Load Octoprint https page on Windows 10 WLAN stuck

#1

What is the problem?
When i connect my Win 10 PC to Octoprint by WLAN and using https the side is not loading and gets stuck after the Browser message that the self signet certificate is not valid. I'm accepting the warning and then its loading without end.
When i connect the same Win 10 PC by LAN everthing is loading smooth. What could be the issue ?

What did you already try to solve it?
I tested with all browsers IE,Edge,Firefox,Chrom.

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
Octoprint 1.4.12

#2

What's the future like? Just kidding. I don't see any logs? May need to see what's in the browser's developer console as well...

#4

octoprint.log (13.5 KB)

Here is the log, i randomized some informations.

Basically the IP 10.10.10.10 is the one with windows. I tried to log in with lan (success) and wlan (no success). Also with a linux machine with IP 11.11.11.11 and this one has no such problem, this should proof that the Network config should be ok and the error only accours on the windows machine.
Octoprint has the ip 11.11.11.12. So there are 2 different ip ranges for lan and wlan.

#5

Well that seems to show the connection establishing, what about inside the developer console of your browser?

#6

no major issue shown there, its loading endless.
when i try to connnect with http its working but the image symbols are not shown properly.
i thing maybe its a timeout related issue any hints ?

#7

Your router is responsible for moving traffic to/from both segments (10.10.10.0/24 and 11.11.11.0/24). It sounds like it's forwarding the port 80 traffic but not the 443 but that's a guess.

In order for the https to work you'd need a self-signed certificate. Make sure to follow the instructions for haproxy.

It may be worthwhile to check your Windows' firewall settings to make sure that it's not blocking local 443 traffic for some reason.

You might try locally on the Pi doing: curl -v https://localhost/ to see what's going on. The -v indicates that you're interested in the verbose mode. Interpreting the header information could tell you if haproxy and the certificate are happy.

#8

i already tried to disable the windows firewall, but did not change anything.

curl -v https://localhost/ gives back :

Expire in 0 ms for 6 (transfer 0x937880)

  • Expire in 1 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 1 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 1 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 1 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 1 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 2 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Expire in 0 ms for 1 (transfer 0x937880)
  • Trying ::1...
  • TCP_NODELAY set
  • Expire in 149999 ms for 3 (transfer 0x937880)
  • Expire in 200 ms for 4 (transfer 0x937880)
  • Connected to localhost (::1) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • successfully set certificate verify locations:
  • CAfile: none
    CApath: /etc/ssl/certs
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (OUT), TLS alert, unknown CA (560):
  • SSL certificate problem: self signed certificate
  • Closing connection 0
    curl: (60) SSL certificate problem: self signed certificate
    More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

#9

Did you actually generate the client certficate?

Backing up here for a moment, the biggest reason why you'd want to use HTTPS is to prevent anyone from eavesdropping on your client-to-server conversation. For a local install of OctoPrint this seems like it's unnecessary to me. Perhaps I might suggest using http and not worrying about this.

#10

I dont use it localy on the PI, always remote over wlan. (ssh or https)

The output above is when run from the PI locally.

When i run the curl -v ... on the windows machine connected to the wlan i get the same.

#11

Try just using http://octopi.local or http://ipaddress

#12

No Luck mate, but i suppose it is a issue to my LAN/WLAN configuration. i will work around by simple using my phone when needed. Thanks anyway.