I used for 2 years the ocotpi server to print. The last time I had some connection problems to reach the server via browser. But if the connection was established than it kept it. Today I updated 1.3.8 to 1.3.10. I printed an all was good. But after a reboot I cannot connect to the server.
I rebooted a few times.
I checked the points that are recommended on the browser page:
Verify that the process is running: ps -ef | grep -i octoprint | grep -i python
-> I don't get any information
Take a look into ~/.octoprint/logs/octoprint.log:
-> there are lot of information but I cannot see the key problem, I attached the log file, in this file you can also see the successful update process... OctoPiServer_noConnection_putty.log (54.2 KB)
pi@octopi:~ $ dh -h
-bash: dh: command not found
pi@octopi:~ $ sudo dh -h
sudo: unable to open /var/lib/sudo/ts/pi: Read-only file system
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for pi:
sudo: dh: command not found
pi@octopi:~ $ ls -l ~/.octoprint
total 52
-rw-r--r-- 1 pi pi 1269 Mar 1 10:20 config.yaml
drwxr-xr-x 7 pi pi 4096 Mar 1 10:22 data
drwxr-xr-x 4 pi pi 4096 Mar 1 10:15 generated
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 logs
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 plugins
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 printerProfiles
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 scripts
drwxr-xr-x 3 pi pi 4096 Mar 1 10:15 slicingProfiles
drwxr-xr-x 3 pi pi 4096 Mar 1 10:15 timelapse
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 translations
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 uploads
-rw------- 1 pi pi 218 Aug 12 2018 users.yaml
drwxr-xr-x 2 pi pi 60 Mar 1 10:15 virtualSd
drwxr-xr-x 2 pi pi 4096 Mar 1 10:15 watched
My bad, that was a typo on my part (I meant to put df there).
pi@octopi:~ $ ls -l ~/.octoprint
total 52
-rw-r--r-- 1 pi pi 1269 Mar 1 10:20 config.yaml
drwxr-xr-x 7 pi pi 4096 Mar 1 10:22 data
That's probably correct for users.yaml since you don't want others reading it (only the owner who is pi in this case). And your config.yaml has its rights set correctly as well. About the only thing left, then, would be who you are.
whoami
# mine responds with "pi"
So if yours also responds with pi then again, try simply nano ~/.octoprint/config.yaml and attempt to make the edits.