Since some months I have the issue that I have to re-login into octoprint UI very often. I did not have that when I startet to use octoprint (around 2 years ago).
I can't tell what causes me to have to login again.
On my phone I have to login nearly everytime. On my ipad "nearly never". On my Laptop sometimes.
I already deleted the cache but that did not help.
It's entirely possible that this is a cookie-based problem. I would guess that OctoPrint saves the session's ID in a cookie so that it knows you're the same person who logged in earlier.
If you have something that automatically deletes or blocks cookies then this might explain things.
I don’t have something that automatically deletes cookies. Or at least I think I don’t have that.
However I do have Pihole in my network. Could this cause this issue?
I dunno. It doesn't sound probable but then again, it's something different. Feel free to turn it off, use a different DNS server temporarily and see if that works better.
I turned it off, but the issue persists. I changed the local IP of my octoprint some months ago. Could this be the issue? An old cookie or something like that?
Now you're getting somewhere. Could be arp caching but seems unlikely. If you have Windows then install the Bonjour client.
If you had an iPhone (unlikely), it would probably just work fine. So I'll guess that you have an Android-based phone. Android calls this Network Service Discovery, for what it's worth. The only documentation I found was how to add the broadcasting side of this to an app rather than to verify whether or not the phone has the service toggled on or not.
That said, your phone can't discover network services unless you're connected to your local wi-fi network, right? And further, your phone needs to be connected to the same 2.4GHz network that your Raspi is connected to (rather than trying to route through your router which may not forward broadcasts like this).
It doesn't sound like @h4nc is having issues connecting but rather staying loggedin. Service discovery and bonjour has nothing to do with that.
@h4nc please provide some more info about your setup and logs. Where does OctoPrint run. What phone, what browser on your phone. How's your network setup. And so on. The more info the better.
Sry for my very late reply, I missed your answers somehow.
I came back because I remembered this issue and I have a new issue that seems very similar.
Lately I don't face the reload issues any more (very very rare, probaly fine). Two things that I can think of that I changed in the last months:
This is interesting:
I have an iPhone and I use Safari. I use the same said for 2,4GHz and 5Ghz. So could this be the issue? It only works if the device chooses the 2,4Ghz network?
Now to my new issue:
Sometimes I cannot connect to octoprint from my iphone or my mac.
Some minutes ago I experienced this:
What could cause this? Seems like the iPad stuck it somehow and I needed to connect with it, to make it work again.
I couldn't find a way to reproduce this, to this happens totally fortuitously.
And this is my logfile (changed the username).
192.168.0.100 is my iPhone
192.168.0.106 is my iPad
192.168.0.102 is my Mac
192.168.0.2 is my home assistant raspi
2019-12-16 16:34:16,373 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:34:40,195 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 16.19ms
2019-12-16 16:34:40,369 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 17.89ms
2019-12-16 16:34:44,449 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.22ms
2019-12-16 16:34:44,597 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.14ms
2019-12-16 16:34:44,711 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.27ms
2019-12-16 16:34:46,427 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:34:46,521 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.100) 17.76ms
2019-12-16 16:34:48,657 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2019-12-16 16:34:48,667 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
2019-12-16 16:34:48,671 - octoprint.plugins.nautilus - INFO - >>>> Sending notification type [error] to 1 device(s)
2019-12-16 16:34:48,673 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2019-12-16 16:35:10,105 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.11ms
2019-12-16 16:35:10,144 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.05ms
2019-12-16 16:35:15,210 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.14ms
2019-12-16 16:35:15,234 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.60ms
2019-12-16 16:35:15,259 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.36ms
2019-12-16 16:35:16,530 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:35:16,694 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2019-12-16 16:35:16,711 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
2019-12-16 16:35:16,716 - octoprint.plugins.nautilus - INFO - >>>> Sending notification type [error] to 1 device(s)
2019-12-16 16:35:16,717 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2019-12-16 16:35:23,363 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.100) 8.20ms
2019-12-16 16:35:26,878 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2019-12-16 16:35:26,895 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Error: Failed to autodetect serial port, please set it manually."
2019-12-16 16:35:26,900 - octoprint.plugins.nautilus - INFO - >>>> Sending notification type [error] to 1 device(s)
2019-12-16 16:35:26,901 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2019-12-16 16:35:33,556 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:35:40,352 - tornado.access - WARNING - 404 GET /apple-touch-icon-precomposed.png (192.168.0.100) 7.34ms
2019-12-16 16:35:40,362 - tornado.access - WARNING - 404 GET /apple-touch-icon.png (192.168.0.100) 6.44ms
2019-12-16 16:35:40,373 - tornado.access - WARNING - 404 GET /favicon.ico (192.168.0.100) 6.41ms
2019-12-16 16:35:40,411 - tornado.access - WARNING - 404 GET /apple-touch-icon-precomposed.png (192.168.0.100) 6.74ms
2019-12-16 16:35:40,422 - tornado.access - WARNING - 404 GET /apple-touch-icon.png (192.168.0.100) 6.67ms
2019-12-16 16:35:40,432 - tornado.access - WARNING - 404 GET /favicon.ico (192.168.0.100) 6.37ms
2019-12-16 16:35:41,060 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 9.65ms
2019-12-16 16:35:41,091 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.19ms
2019-12-16 16:35:45,439 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.100
2019-12-16 16:35:45,609 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.100
2019-12-16 16:35:46,074 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:35:46,096 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.10ms
2019-12-16 16:35:46,122 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.22ms
2019-12-16 16:35:46,212 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 9.74ms
2019-12-16 16:35:46,561 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:35:50,696 - octoprint.server.util.sockjs - INFO - User myusername logged in on the socket from client 192.168.0.100
2019-12-16 16:35:54,057 - tornado.access - WARNING - 409 POST /api/printer/command (192.168.0.100) 19.70ms
2019-12-16 16:35:54,072 - tornado.access - WARNING - 409 POST /api/printer/command (192.168.0.100) 30.68ms
2019-12-16 16:35:59,891 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:36:00,167 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.100
2019-12-16 16:36:12,136 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.74ms
2019-12-16 16:36:12,334 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.32ms
2019-12-16 16:36:16,618 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:36:16,685 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.100
2019-12-16 16:36:17,352 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 19.03ms
2019-12-16 16:36:17,591 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 16.62ms
2019-12-16 16:36:17,742 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.24ms
2019-12-16 16:36:43,156 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.22ms
2019-12-16 16:36:43,296 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 17.19ms
2019-12-16 16:36:46,690 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:36:48,214 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 18.74ms
2019-12-16 16:36:48,507 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.68ms
2019-12-16 16:36:48,672 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 16.49ms
2019-12-16 16:37:14,242 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 18.32ms
2019-12-16 16:37:14,371 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.51ms
2019-12-16 16:37:16,745 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:37:19,374 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.42ms
2019-12-16 16:37:19,523 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 8.22ms
2019-12-16 16:37:19,635 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 9.88ms
2019-12-16 16:37:45,089 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 16.39ms
2019-12-16 16:37:45,222 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.73ms
2019-12-16 16:37:46,799 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:37:50,199 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 16.28ms
2019-12-16 16:37:50,257 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 18.43ms
2019-12-16 16:37:50,301 - tornado.access - WARNING - 409 GET /api/printer (192.168.0.2) 15.66ms
2019-12-16 16:38:05,010 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.106
2019-12-16 16:38:05,240 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.106
2019-12-16 16:38:05,266 - octoprint.server.util.sockjs - INFO - User myusername logged in on the socket from client 192.168.0.106
2019-12-16 16:38:07,351 - octoprint.server.api.system - INFO - Performing command for custom:pon
2019-12-16 16:38:08,255 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial port"
2019-12-16 16:38:08,287 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial port" to "Opening serial port"
2019-12-16 16:38:08,291 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2019-12-16 16:38:08,302 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-12-16 16:38:08,305 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-12-16 16:38:09,214 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-12-16 16:38:13,839 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2019-12-16 16:38:13,852 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-12-16 16:38:13,871 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2019-12-16 16:38:16,852 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:38:21,988 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:38:28,625 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.100
2019-12-16 16:38:28,790 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:38:30,482 - octoprint.server.util.sockjs - INFO - User myusername logged in on the socket from client 192.168.0.100
2019-12-16 16:38:46,884 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:39:16,944 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:39:24,761 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.100
2019-12-16 16:39:47,005 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:40:17,064 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:40:47,123 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:41:17,183 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:41:47,240 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:42:02,795 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2019-12-16 16:42:17,300 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:42:47,357 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:42:49,823 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: Test/cube.gcode, owner: myusername, user: myusername
2019-12-16 16:42:49,833 - octoprint.plugins.DisplayLayerProgress - INFO - File selected. Determining number of layers.
2019-12-16 16:42:49,921 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2019-12-16 16:42:49,982 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Test/cube.gcode, owner: myusername, user: myusername
2019-12-16 16:42:49,998 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2019-12-16 16:42:50,037 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2019-12-16 16:42:50,883 - octoprint.plugins.DisplayLayerProgress - INFO - Printing started. Detailed progress started.{'origin': 'local', 'name': u'cube.gcode', 'file': u'/home/pi/.octoprint/uploads/Test/cube.gcode', 'owner': 'myusername', 'path': u'Test/cube.gcode', 'user': 'myusername', 'size': 1106065L, 'filename': u'cube.gcode'}
2019-12-16 16:42:50,897 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2019-12-16 16:42:53,504 - octoprint.util.comm - INFO - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly
2019-12-16 16:43:06,466 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:43:07,418 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.100
2019-12-16 16:43:07,617 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:43:09,148 - octoprint.server.util.sockjs - INFO - User myusername logged in on the socket from client 192.168.0.100
2019-12-16 16:43:13,791 - octoprint.util.comm - INFO - Telling the printer to set the busy interval to our "communicationBusy" timeout - 1s = 2s
2019-12-16 16:43:17,416 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:43:47,479 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:44:15,249 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.100
2019-12-16 16:44:17,537 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:44:47,594 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:44:55,797 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.106
2019-12-16 16:45:17,651 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:45:47,706 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:46:17,762 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:46:47,816 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:47:17,871 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:47:47,927 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:48:17,959 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:48:47,991 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:49:18,022 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:49:48,068 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:50:18,100 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:50:48,132 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:51:18,164 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:51:48,222 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:52:18,278 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:52:48,333 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:53:18,378 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:53:48,439 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:54:18,495 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:54:43,863 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.100
2019-12-16 16:54:44,013 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.100
2019-12-16 16:54:44,098 - octoprint.server.util.sockjs - INFO - User myusername logged in on the socket from client 192.168.0.100
2019-12-16 16:54:48,551 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:55:18,582 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:55:20,914 - octoprint.server.util.sockjs - INFO - Client connection closed: 192.168.0.100
2019-12-16 16:55:48,615 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:56:18,646 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:56:48,678 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:57:02,798 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2019-12-16 16:57:18,733 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:57:48,766 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:58:18,825 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:58:48,875 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:59:18,910 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 16:59:48,965 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 17:00:19,036 - octoprint.plugins.navbartemp - INFO - Checking SoC internal temperature
2019-12-16 17:00:20,440 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.102
2019-12-16 17:00:20,987 - octoprint.server.util.sockjs - INFO - New connection from client: 192.168.0.102
2019-12-16 17:00:21,144 - octoprint.server.util.flask - INFO - Passively logging in user myusername from 192.168.0.102
2019-12-16 17:00:23,539 - octoprint.server.util.sockjs - INFO - User myusername logged in on the socket from client 192.168.0.102
BTW I run Unifi controller as an addon in home assistant. And I sometimes also can't connect to the Unifi controller. Could be the same issue.
In many default network router setups, it won't forward broadcast traffic from one network to another. So the Avahi/Bonjour "hey, my name is octopi...!" broadcast packet wouldn't arrive on the other wifi network, necessarily. But this only affects lookups. And it depends upon your router.
To this, I'll add that my own router/Avahi will increment a new broadcast like this if I've just taken a microSD out of a Raspberry Pi 3B, for instance, and put it into a Pi 4B. Immediately, Avahi and the router will then negotiate that it gets to be "octopi_1" or something like that. If I wait a bit, the router will retire the earlier saved information and it will become "octopi" again.
In many cases, simply (successfully) pinging "octopi.local" in this case will put that into the device's local arp cache. As long as it's in the cache then it will work happily. Oh, and you need to try "octopi.local" rather than just "octopi".
Thank you. I use a Unifi USG router.
I just had this issue again on my iPhone.
I wasn’t able to connect to the octopi (btw I don’t use octopi.local, I use the DHCP reserved IP address in the Browser). I also tried restarting the phone and closing safari, but it still did not work.
Tried connecting with my mac, which worked at the first try.
Closed Safari again on my phone and octoprint loaded fine again.
Now it seems like (have to repeat it again to verify) I found a procedure to make it work, maybe someone explain what is wrong.
For what it's worth, my iPhone is connected to my local wifi and I've just jumped into the DuckDuckGo browser and entered http://octopi.local and it's happily resolving and going to the page. Likewise, the Safari browser also works doing this.
I updated Octopi to the lastest version 0.17 because it wasn't possible any more autoupdate my plugins. I was running 0.12.
Did not habe any issues in the last few days, so it looks like this solved my issue.
Also I noticed a few other positive things, but I'm not sure whether it's a placebo or not:
So are these benefits due to the update, the new install (restored a backup) or only a placebo?