My printer has a web app being served at 192.168.1.101:80, and is redirecting the OctoPrint page to 192.168.1.101:1080. This works perfectly, with one issue. When a user isn't logged in, the OctoPrint redirects to the login page at:
dropping the port number and trying to access 80, which leads to a "
Cannot GET /login/" error. When the port number is manually added, like so:
I am able to access the login page without issue. From that point forward, reloading the OctoPrint page will work perfectly. The problem is that if a user logs out, restarts the printer, or accesses the printer from a new device, they have to go back through the process of adding the port number manually.
I've looked through the code for the web app for the printer, and it's handling all requests to the API correctly and the port number is properly attached in all instances. The printer is fully functional, once the Login screen port number issue is manually resolved.
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
octoprint-systeminfo-20220105213351.zip (15.3 KB)
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
OctoPrint version: 1.7.2
OctoPi version: 0.18.0
Firmware: Marlin 1.x
Browser: I've reproduced this issue in current versions of Chrome, Firefox, Safari