Cant connect to server after 1.8 upgrade - OctoPrint 4a

Get Help
1

What is the problem?

After Upgrade to 1.8 no longer able to connect via web browser - seems to be permissions related. Realize Octoprint 4a is support by others, but wanted to bring awareness.

Per android device, says "OctoPrint is Running" and does connect to printer, camera server seems to be active - Looks normal from andriod 10 phone

See screenshots from Chrome browser attempt from Win10 pc, same message when attempting from chrome browser on andriod phone running OctoPrint 4a.

image
image1874×654 59.9 KB

What did you already try to solve it?

A few reboots, reload, googling..

Have you tried running in safe mode?

Unable (or unfamilair) with ability to run in safe mode via Octoprint 4a. Glad to try with guidance

Did running in safe mode solve the problem?

N//A

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

Glad to try, need instruction

Additional information about your setup

Octoprint 1.7 was stable on unrooted android 10 phone, update to 1.8, initially looked successful but said unable to restart. using Python 3.9.? - Checked before update.

Seeing similar reports starting today on the OctoPrint 4a Github, reporting same/similar issue.

I am unable to capture the terminal log, but on the OctoPrint 4a GitHub another user has provided an example, that appears to provide same failure mode.

see comment from others troubleshooting same..
Quote from other thread on OctoPrint 4a...

[

koprda](koprda (Ivan Koprda) · GitHub) commented 19 minutes ago •

edited

problem is in new version octoPrint
src/utils/comm.py on line 201 os.scandir("/dev")

quick fix:

  • comment or delete lines 201-204 in comm.py and reinstall
  • I used ssh in okto4a

ssh root@[ip] -p 8022
cd ~/OctoPrint-OctoPrint-f430257
sed -i '201,204d' src/octoprint/util/comm.py
pip install .

... restart server

1 Like
2

It's a known issue, albeit a very annoying one following 5 release candidates across 2 months for people to test. I couldn't reproduce the issue on my own Octo4a test install.

Link to the Octo4a issue for anyone else:

I suspect OctoPrint will need a patch to better handle the permissions error here, it was not anticipated - the old code used to do the same job, but with a higher-level API that must do some error handling for us, now it will have to be done in OctoPrint specifically.

1 Like
3

Thanks, very much - watching on the other thread.

4

I know you may have seen the other thread, but again for anyone else that comes across this issue, it has been fixed with Octo4A version 1.1.0:

1 Like
5

The issue has re-emerged and been reported for further review.

6

The update to 1.1.1 has/appears to have resolved the issue.

2 Likes
7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.