Since version 9.10 I have had issues accessing the NodeLink Web page. ip_addr:8090 comes back with a err_connection_refused error. 

When this happened I followed the thread on Mono and NodeLink access issues, but it went no where and the problem persists. I have gone so far as to reinstall Sketch from scratch and then NodeLink again. This allowed me to configure NodeLink and access the web page, but now I find a few days later NodeLink's web interface is again not available. 

 

NodeLink is running as verified by both the AC and systemctl status nodelink on the Pi3 itself. I just can't access the web interface. I have tried Chrome, FireFox and Edge and none of them work. I'm open to suggestions. Thank you.

Log?

io_guy,

First i'd like to thank you for all your work on NodeLink. It's a wonderful application and it just works. I don't like to bug you unless it's something I just can't figure out and I admit I should have done more investigation before I posted. I have NodeLink installed in /opt/nodelink and didn't change the permissions. This was causing all kinds of weirdness, but mostly what was happening was that config.xml was being cleared on a reboot of the Pi or a restart of NodeLink. 

 

Since the porfile existed on the ISY, but the config.xml was blank the web page wouldn't load and the only error was err_connection_refused. Simply changing the permission on the /opt/nodelink directory allowed the config.xml file to be written to and everything is now working again.

 

In 9.10 I didn't have this problem, it is only an issue in versions greater then 9.10. shrug. That's what I found and I thought I'd share it and again thank you for your responsiveness and NodeLink.

1 hour ago, kzboray said:

io_guy,

First i'd like to thank you for all your work on NodeLink. It's a wonderful application and it just works. I don't like to bug you unless it's something I just can't figure out and I admit I should have done more investigation before I posted. I have NodeLink installed in /opt/nodelink and didn't change the permissions. This was causing all kinds of weirdness, but mostly what was happening was that config.xml was being cleared on a reboot of the Pi or a restart of NodeLink. 

 

Since the porfile existed on the ISY, but the config.xml was blank the web page wouldn't load and the only error was err_connection_refused. Simply changing the permission on the /opt/nodelink directory allowed the config.xml file to be written to and everything is now working again.

 

In 9.10 I didn't have this problem, it is only an issue in versions greater then 9.10. shrug. That's what I found and I thought I'd share it and again thank you for your responsiveness and NodeLink.

I didn't extract whether you got fixed up or not from your last post.

I had a few times where NodeLink wiped out the config.xml file.in earlier versions .io_guys has created a backup file for it so it is there if you need to recover the file, you can  copy the backup  back into the original name, also. 

 IMHO it had  something to do with NodeLink not getting a correct response from ISY and thinks it is a virgin run creating the config.xml file from scratch again. If I read it right there has been a lot of protocol  fixes on both ends of the comm link between ISY and Node Servers, lately.  I assume I will not likely  see this again with v9.12 and ISY v5.0.12.

Running NodeLink v9.12 now and haven't seen a problem with this for quite some time. It was rare anyway.

Larryllix,

I found two problems both with my Pi configuration and a shout out to io_guy for his help and fast response. The first problem was that I had installed NodeLink in /opt/nodelink and I didn't have the permissions set properly so the config.xml and backup couldn't be written to. The second issue was that during startup of the Pi3 NodeLink was trying to load before the network had started. I first tried changing raspi-config startup to wait on the network which didn't help, and then io_guy suggested I add a delay into my services script which solved my remaining issues problems.

I think you're right about the config.xml being cleared when NodeLink can't connect to the ISY and that's probably exactly what was happening with the network not being loaded during startup. Here's the final version of the services script I'm using to start NodeLink including the delay. "ExecStartPre=/bin/sleep 10"

 

[Unit]
Description=NodeLink Server
Documentation=http://automationshack.com/nodelink.html
After=network-online.target

[Service]
Type=simple
ExecStartPre=/bin/sleep 10
ExecStart=/usr/bin/mono /opt/nodelink/NodeLink.exe
Restart=always

[Install]
WantedBy=multi-user.target