Skip to content
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

409 conflict error #890

Closed
megatech1966 opened this issue Aug 8, 2020 · 27 comments
Closed

409 conflict error #890

megatech1966 opened this issue Aug 8, 2020 · 27 comments
Assignees
Labels
bug Something isn't working

Comments

@megatech1966
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduceimage
Steps to reproduce the behavior:

  1. Go to files
  2. Click on local
  3. Select file to print
  4. See error 409 conflict. Still prints ok.

Expected behavior
No error message

Screenshots
If applicable, add screenshots to help explain your problem.

General Information:

  • Hardware pi 4. CR10S3
  • OS Info Raspbian Buster Lite
  • OctoDash Version [v2]
  • OctoPrint Version [v1.4.2]

Additional context

@UnchartedBull
Copy link
Owner

Has this started with 1.4.2, so doesn't occur with 1.4.0? I've been away a couple of days, so I'm just catching up.

@UnchartedBull UnchartedBull added the bug Something isn't working label Aug 10, 2020
@megatech1966
Copy link
Author

megatech1966 commented Aug 10, 2020 via email

@megatech1966
Copy link
Author

Does not do it with OctoPrint 1.4.0

@UnchartedBull
Copy link
Owner

Haven't had any time to upgrade my printer to 1.4.2 yet. I'll try to find some time this week.

@UnchartedBull
Copy link
Owner

Could you maybe send over that GCode file? I can't reproduce this issue on 1.4.2 on my machine :/.

@megatech1966
Copy link
Author

megatech1966 commented Sep 2, 2020 via email

@megatech1966
Copy link
Author

megatech1966 commented Sep 2, 2020 via email

@UnchartedBull
Copy link
Owner

Thanks. I'll try that and report back :)

@UnchartedBull UnchartedBull self-assigned this Sep 15, 2020
@UnchartedBull
Copy link
Owner

I've tried multiple things and I'm just not able to replicate this on my end. With one of the next releases the API calls will be replaced by the OctoPrint JS Client, which should hopefully fix this issue. Until then I probably won't be able to provide a fix for this. Sorry for the inconvenience. Will most likely be fixed together with #595

@titis14
Copy link

titis14 commented Sep 18, 2020

Hello, I have the same error I thought it came from a usb problem between my screen, the printer and the cam but apparently it's something else.
Image of ocotdash

@UnchartedBull
Copy link
Owner

@titis14 the error you're getting is something different. The weird thing is that the values for your printer are all available (temperature / status / ...). What happens if you close the card, does it come back again? Mabye OctoPrint just had a small hickup.

@megatech1966
Copy link
Author

megatech1966 commented Sep 21, 2020 via email

@titis14
Copy link

titis14 commented Sep 21, 2020

@UnchartedBull If I type on the notification it goes away and no problem afterwards. I have to do a test without the cam because at the beginning of the installation of octodash I did not have this error.

@megatech1966
Copy link
Author

I did a fresh install of OctoPrint and octodash. Still get errors when picking gcode files. This I didn't install samba. Thought that might fix it. It didn't 🥺

@UnchartedBull
Copy link
Owner

Great! Closing this for now. If the issue reappears please reopen :)

@titis14
Copy link

titis14 commented Sep 28, 2020

Switching on the printer and octodash today I had no error.

@megatech1966
Copy link
Author

I thought I had fix the 409 error when I used the global API key, but no it still happens😢. Also tried port 80 instead of 5000. No change🥺 Tried uninstalling octopod. No change😭 Is there any else that I can try?

@megatech1966
Copy link
Author

Switching on the printer and octodash today I had no error.

Sometimes it works. Sometimes it doesn't 🥺

@megatech1966
Copy link
Author

It's been solved by James Mackay. For some reason my touchscreen is recording 2 taps when I tap on the print icon too slowly.

@titis14
Copy link

titis14 commented Oct 2, 2020

Switching on the printer and octodash today I had no error.

Sometimes it works. Sometimes it doesn't 🥺

The same for me during my last 2 ignition 409 error tap on it and it works anyway.

@megatech1966
Copy link
Author

megatech1966 commented Oct 2, 2020 via email

@titis14
Copy link

titis14 commented Oct 4, 2020

Did you see me post? I found what was causing it. A dev on Facebook suggested it and he was right.

Sent from my iPhone X 256Gb
On 3 Oct 2020, at 5:01 am, titis14 @.***> wrote:  Switching on the printer and octodash today I had no error. Sometimes it works. Sometimes it doesn't 🥺 The same for me during my last 2 ignition 409 error tap on it and it works anyway. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

I have the error already starting without touching the screen and even without turning on the printer.

@megatech1966
Copy link
Author

megatech1966 commented Oct 4, 2020 via email

@UnchartedBull
Copy link
Owner

@titis14 could you maybe elaborate on the errors you're getting? Maybe attaching a screenshot. Do they also occur if the printer is turned on?

@titis14
Copy link

titis14 commented Oct 5, 2020

@titis14 could you maybe elaborate on the errors you're getting? Maybe attaching a screenshot. Do they also occur if the printer is turned on?

Hello, I put a screenshot above with the orange screen. I also have the error if the printer and turn on. I don't know what it came from because if I type on the message it goes away and everything works normally.

@UnchartedBull
Copy link
Owner

Oh didn't saw that you're the same guy. As stated above please wait for release 2.2 or 2.3, which will replace the API with OctoPrint websocket. This should get rid of the error. Sorry that you need to close this each time until then :/

@titis14
Copy link

titis14 commented Oct 10, 2020

Oh didn't saw that you're the same guy. As stated above please wait for release 2.2 or 2.3, which will replace the API with OctoPrint websocket. This should get rid of the error. Sorry that you need to close this each time until then :/

No problem ;) you do a great job is for free.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants