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

Unable to upload gcode to Octoprint from 2.4.0-beta2-win64 #7389

Closed
ochm opened this issue Nov 30, 2021 · 9 comments
Closed

Unable to upload gcode to Octoprint from 2.4.0-beta2-win64 #7389

ochm opened this issue Nov 30, 2021 · 9 comments

Comments

@ochm
Copy link

ochm commented Nov 30, 2021

Version

2.4.0-beta2-win64

Operating system type + version

Windows10

Behavior

When i try to upload gcode, i see error message window:
Error uploading to print host:
HTTP 503: 503 Service Unavailable
No server is available to handle this request.

When i use beta1 or any previous version of slicer, upload is well.

I'm using Octoprint for two printers, the url in physical printer definition is
for printer1 http://ip.add.re.ss/P1/
for printer2 http://ip.add.re.ss/P2/

Project: zasobnik.zip

@neophyl
Copy link

neophyl commented Nov 30, 2021

Could it be the same as this #7361 ?

@ochm
Copy link
Author

ochm commented Dec 1, 2021

Could it be the same as this #7361 ?

I don't know, I'm not using hostname in definition, I'm using IP, and i don't know nothing about port 5000,
HAproxy in Octoprint is listening on 80 and 443
$ netstat -nap|grep hap
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 638/haproxy
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 638/haproxy

The definition of connection in physical printer setting does not contain any port,
it is written as standard HTTP: http://ip.add.re.ss/P1/ so it means port 80.

@bubnikv
Copy link
Collaborator

bubnikv commented Dec 1, 2021

Could it be the same as this #7361 ?

It surely is.

@ochm
Copy link
Author

ochm commented Dec 1, 2021

Could it be the same as this #7361 ?

It surely is.

I'm not so sure, because I'm not using nonstandard port in physical printer definition (using http), and my error message is number 56 (who knows what does it mean).
err

But if you are sure, my issue can be closed.

kocikdav added a commit that referenced this issue Dec 1, 2021
Instead of just adding port, take original address and replace just host with resolved host.
fix of #7389
@lukasmatena
Copy link
Collaborator

lukasmatena commented Dec 1, 2021

@ochm Can you please try slicing exactly the same 3MF in beta1 and see if it works there? If it does not work, it is likely on your end. If it does, we may provide you with a dev build where #7361 is fixed, so we can make sure it was indeed the problem. Thanks.

Edit: Sorry, others are looking into it already.

@kocikdav
Copy link
Collaborator

kocikdav commented Dec 1, 2021

It is a different manifestation of same bug I introduced a week ago. But thanks to this issue I understood better how to fix it. I will paste a dev build here shortly.

@ochm
Copy link
Author

ochm commented Dec 1, 2021

It is a different manifestation of same bug I introduced a week ago. But thanks to this issue I understood better how to fix it. I will paste a dev build here shortly.

Great, thank you!

@kocikdav
Copy link
Collaborator

kocikdav commented Dec 1, 2021

Please try this build. (if prompted before download use login prusaslicer : slicer). Also please note that this build is experimental and other features could be broken or in middle of development.

When you run PrusaSlicer with command line, there should be output (marked as error but its not an error) to log real address for upload.

@ochm
Copy link
Author

ochm commented Dec 1, 2021

Yes! Works OK, like in beta1

kocikdav added a commit that referenced this issue Dec 2, 2021
Instead of just adding port, take original address and replace just host with resolved host.
fix of #7389
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants