Local and remote br...
 
Notifications
Clear all

[Solved] Local and remote browser can no longer open Mycodo UI  


kppc
 kppc
(@kppc)
Eminent Member
Joined: 6 months ago
Posts: 28
Topic starter  

I am able to connect via ssh to the system. However connecting via https no longer works after a system reboot.

Tried stopping and starting nginx service. This works, meaning a browser can open the UI, as long as the terminal session from my remote mac that started the nginx service stays open.

Second test was connecting a keyboard, mouse and monitor directly to the raspberry pi and restarting the system. When opening the browser to local host, an error displayed (sorry I didn't get a copy of it) that said something about conflicting chromium sessions. After allowing chromium to stop the other process, the browser on the raspberry itself opened the mycodo UI. Logged out of Mycodo and shut down the browser. Connected via HTTPS from my mac and everything worked normally again. Problem solved, I thought.

Then today I tested the system by shutting down the mycodo and raspberry pi using the menu option in Mycodo. Then powered the pi off and a minute later back on. After a minute or two the 4 line display on the pi showed the pH, EC and other data. The system was working normally. Tried to login in to the UI from my mac and received the same error "failed to connect".

I'm sure if I connect a monitor, mouse and keyboard it can be fixed again till the system is rebooted. 

Two questions:

1. What would cause this to start happening?

2. What can be done to correct it permanently?


Quote
Kyle Gabriel
(@kylegabriel)
Member Admin
Joined: 6 years ago
Posts: 429
 

This isn't normal behavior, so there's probably a software issue on your system. I'd recommend reinstalling the OS and Mycodo. Without logs or a verbose error message, diagnosing the issue probably isn't possible. Also, nginx shouldn't need a terminal open to stay running; its running state should be changed with "sudo service nginx stop|start|restart".

Mycodo Developer


ReplyQuote
kppc
 kppc
(@kppc)
Eminent Member
Joined: 6 months ago
Posts: 28
Topic starter  

Will do the reinstall of both the OS and Mycodo. Is there an article on saving the mycodo setup through terminal? And one for restoring the backup after the new mycodo install?

I looked at the mycodo backups via terminal yesterday. There is a backup that is dated prior to this problem. 

thanks again for your help!


ReplyQuote
Kyle Gabriel
(@kylegabriel)
Member Admin
Joined: 6 years ago
Posts: 429
 

Backup and restore of Mycodo settings can be performed from the Import/Export page of the UI.

Mycodo Developer


ReplyQuote
Kyle Gabriel
(@kylegabriel)
Member Admin
Joined: 6 years ago
Posts: 429
 

You could save the entire Mycodo directory, then copy it to the new system and run install/setup.sh

Backups are saved to /var/Mycodo-Backups

Mycodo Developer


ReplyQuote
kppc
 kppc
(@kppc)
Eminent Member
Joined: 6 months ago
Posts: 28
Topic starter  

The reinstall using 'sudo /bin/bash /home/pi/Mycodo/install/setup.sh' corrected the problem. The system UI is now remotely accessible again. Thanks for the help!


ReplyQuote