-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't retrieve layer progress #1304
Comments
Im wracking my brain to figure this out too. Tried looking through other reports and nothing ive seen solves my problem, ive tried reinstalling too. |
same issue on my side |
Are you sure you have the DisplayLayerProgress plugin installed? Without additional info such as version numbers (octoprint, octopi, octodash), slicer used, and what settings you have setup in the DisplayLayerProgress plugin then it'll be hard for anyone to help you. |
In my case, I update to 2.1.2 and had an issue with the sleepfunction, so i downgraded back to 2.0. |
I tried switching my port in OctoDash from 80 to 500 like someone said they did to get working. Now it wont connect just hangs. How can i switch the port now? I uninstalled and reinstalled but i think it is still keeping the port 500 from before. |
I also see this occasionally when the printer is connected but not printing. I definitely have the DisplayLayerProgress plugin installed. If I can help by providing more info or testing anything let me know. |
I have the DisplayLayerProgress plugin installed and it works great now! |
How did you get it working? I still get the error and I have the plugin installed already (I installed it during the OctoDash install propmts) |
Reopening since the error does seem to pop up again. The workaround for now is to use @jneilliii's custom fork with DisplayLayerProgress disabled: https://github.com/jneilliii/OctoDash. If anyone who has the problem could please reply with the following information:
|
What doesn't work? What did you already try? General Information: |
Changed from octopi.local to localhost in config. May have solved the issue. |
As of right now I would say that's it in my case: Use "localhost" and the problem seems to be gone! |
There seems to be something really fishy with octoprints mdns atm. Lots of people reporting problems which go away once localhost is used. |
It might have something to do with IPv6. I do know that there were some changes to mdns in one of the recent releases. |
I'm persistently having the same error: "Can't retrieve layer progress - Http failure response for http://localhost/plugin/DisplayLayerProgress/value - 404 NOT FOUND" I've tried changing url in ~/.config/octodash/config.json. Either I get no connection or the above error. I have tried network alias, url and localhost. Three weeks getting this far...really frustrated! (and I still don't have touchscreen working) General Information: |
i an getting the same error but on the octoprint screen rather than on octodash, i also am unable to update octoprint now that octodash is installed for some reason, has anyone had this same iisue? |
Ok I still really don't know whats going on here, but here are a few things to try so we can narrow this down:
After this change OctoDash will only ask OctoPrint for new data every 5 seconds, if this error is somehow load related this should get rid of the error. |
It came again when I cahnged to octopi.local and went when I cahnged back. So this it was for me. |
Latest everything, Pi 3B+. I had the same, on Octodash screen only, and only when idle. Yes, I did print some files before installing Octodash and DLP. When printing, everything works as expected. Seems to have gone away after switching to localhost. (Fingers crossed, but I haven't seen it after I made the change about 30 mins ago). Thank you @Cyberbastler ! |
Hi,
I have installed octoDash on my raspberry but now I get a Warnig
Http failure response for http://octopi.local/plugin/DisplayLayerProgress/values: 404 not found
I have looked at the internet but i can not find a solution.
Can you help me?
The text was updated successfully, but these errors were encountered: