-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
Explain ports and host in Troubleshooting guide #560
Comments
Port 5000 is the port that the API uses |
Weird. It would not work for me. Only port 80 worked. |
5000 worked fine for me |
Does 80 work for you? |
The haproxy config in octopi just redirects port 80 to 127.0.0.1:5000, so in theory (assuming octodash and octoprint are running on the same pi) octodash should always work when pointed at 127.0.0.1:5000 (or localhost:5000) even if port 80 is also accessible. Using port 80 would require haproxy set up to forward the port. Octopi may have this enabled by default (it looks like), but for example I just installed octoprint on raspbian so I don't have haproxy running. |
Ah, so my problem is that I used the same IP as when I log in from my browser instead of localhost. Can we add this information to the Wiki Troubleshooting section? |
5000 is the default port. I‘ll add this info to the troubleshooting guide later. Thanks for the info! |
Has been added to the troubleshooting guide alongside with a brief documentation about each setting. |
Unless I am mistaken the default OctoPrint port number will be 80 for 99% of installations. So that is what it should be during setup instead of 5000.
Edit: This is to avoid confusion during setup. Most users like I did assume the provided port is what a standard installation of OctoPrint would be set to.
The text was updated successfully, but these errors were encountered: