What is the problem?
I think my Chrome browser is preventing me from logging into Octoprint's UI.
I can access the UI from the expected address by using Edge instead of Chrome. I can also reach the "OctoPrint Login" page in Chrome. However, when I enter the same login credentials I used to reach the UI in Edge, it seems to revert back to the "OctoPrint Login" page before I entered my credentials (without giving a "wrong username or password" warning).
Additionally, the octoprint.log file consistently shows the following at the time stamp where I attempted to log in via Chrome:
2022-08-15 20:57:22,550 - octoprint.access.users - INFO - Logged in user: Afish321
2022-08-15 20:57:22,553 - octoprint.server.api - INFO - Actively logging in user Afish321 from 10.0.0.7
2022-08-15 20:57:22,690 - octoprint.server.util.sockjs - INFO - Client connection closed: 10.0.0.7
2022-08-15 20:57:22,857 - octoprint.server.util.sockjs - INFO - New connection from client: 10.0.0.7
This is what octoprint.log reports when I re-log into the UI from Edge:
2022-08-15 21:11:42,456 - octoprint.access.users - INFO - Logged in user: Afish321
2022-08-15 21:11:42,459 - octoprint.server.api - INFO - Actively logging in user Afish321 from 10.0.0.7
2022-08-15 21:11:42,643 - octoprint.server.util.flask - INFO - Passively logging in user Afish321 from 10.0.0.7
2022-08-15 21:11:42,644 - octoprint.access.users - INFO - Logged in user: Afish321
2022-08-15 21:11:42,788 - octoprint.server.util.sockjs - INFO - Client connection closed: 10.0.0.7
2022-08-15 21:11:43,187 - octoprint.plugins.octoeverywhere - INFO - SetFrontendLocalPort API called. Port:5000 IsHttps:False URL:http://10.0.0.18:5000/?
2022-08-15 21:11:43,216 - octoprint.server.util.sockjs - INFO - New connection from client: 10.0.0.7
2022-08-15 21:11:43,234 - octoprint.server.util.flask - INFO - Passively logging in user Afish321 from 10.0.0.7
2022-08-15 21:11:43,235 - octoprint.access.users - INFO - Logged in user: Afish321
2022-08-15 21:11:45,445 - octoprint.server.util.sockjs - INFO - User Afish321 logged in on the socket from client 10.0.0.7
2022-08-15 21:11:46,255 - octoprint.plugins.tracking - INFO - Sent tracking event webui_load, payload: {'browser_name': 'Edge', 'browser_version': '104.0.1293.54', 'os_name': 'Windows', 'os_version': '10'}
What did you already try to solve it?
Tried the following with no effect:
- Hard reloading the webpage
- Deleting the cache and cookies of the webpage
- Changed site settings in Chrome to allow everything I could, including "insecure content" (which to my knowledge deals with the https issue) (this fix allowed me to reach the login page - I previously was prevented from accessing the webpage entirely due to Chrome's ridiculous way of handling anything that's not an https link)
Logs (syslog, dmesg, ... no logs, no support)
octoprint.log (3.5 MB)
Additional information about your network (Hardware you are trying to connect to, hardware you are trying to connect from, router, access point, used operating systems, ...)
I'm operating on a home network. My Windows 10 PC is hard-wired to the router, while the Pi is connected via WiFi. Since I'm not having any issues logging in with Edge, I'm assuming that the Chrome browser itself is mucking with it somehow.
