[Bug]: HTTPS connection does not work. 2 operating systems 3 browsers. Does not work.

[rekcodocker]

Before submitting

• I have searched existing issues to make sure this bug hasn't already been reported
• I have updated to the latest version of the software to verify the issue still exists
• I have cleared cache/cookies/storage or tried in a private/incognito window (if applicable)

Hardware

Heltec V3

Connection Type

HTTP

Local or Hosted

https://client.meshtastic.org

Firmware Version

2.7.15.567b8ea

Operating System

Linux Mint 21 and Windows 11

Browser

Firefox, Google Chrome and Microsoft Edge

Expected Behavior

I follow the instructions.
open https://client.meshtastic.org/
open a new tab.
browse to https://my-node-IP
accept all risks.
re-browse to https://my-node-ip.
confirm there IS a certificate

go to https://client.meshtastic.org/
add the IP (or meshtastic.local, does not make a difference).
Click 'test connection'

Expected: That I get a connection.

Error 'not reachable´. Every time. On three browsers on two operating systems.
HTTPS does not work.

I also can not disable the 'HTTPS' even though there is a button on the screen. That button is disabled.

Actual Behavior

I follow the instructions.
open https://client.meshtastic.org/
open a new tab.
browse to https://my-node-IP
accept all risks.
re-browse to https://my-node-ip.
confirm there IS a certificate

go to https://client.meshtastic.org/
add the IP (or meshtastic.local, does not make a difference).
Click 'test connection'

Error 'not reachable´. Every time. On three browsers on two operating systems.
HTTPS does not work.

I also can not disable the 'HTTPS' even though there is a button on the screen. That button is disabled.

Steps to Reproduce

open https://client.meshtastic.org/
open a new tab.
browse to https://my-node-IP
accept all risks.
re-browse to https://my-node-ip.
confirm there IS a certificate

go to https://client.meshtastic.org/
add the IP (or meshtastic.local, does not make a difference).
Click 'test connection'

Expected: That I get a connection.

Error 'not reachable´. Every time. On three browsers on two operating systems.
HTTPS does not work.

I also can not disable the 'HTTPS' even though there is a button on the screen. That button is disabled.

Relevant console output

Screenshots

Error:

web server is running under https:

Additional Context

1. My phone can make a connection via the wifi using the app. My laptop/browser can not.
2. There is a 'HTTPS / HTTP' switch on the screen but it is disabled. It can not be clicked.
3. My suggestion: First make it work, then make it safe. Now it simply does not work via the web/wifi
4. serial and bluetooth work.

[potassium-chloride]

Absolutely same issue.

[alexherington]

The default timeout for this reachability check is 2500ms. I've noticed in the web dev tools it always hits that timeout trying to connect to my Heltec V3. I did some benchmarking and over decent wifi (approx 6ms ping time) it takes that device ~7s to respond to the check.

We should extend the reachability timeout to maybe 10000ms, or make it configurable from the web UI. A 7 second response time is unusually long though.

The write timeout is already on the cusp of that:
READ_TIMEOUT_MS = 7000 (7 seconds)
WRITE_TIMEOUT_MS = 4000 (4 seconds)

[AlanLane]

I’ve tried connecting multiple times, and it seems to be an HTTPS permission issue that the browser cannot handle due to security policies.
I managed to connect only once by lowering all the security policies through advanced settings, but that was a one-time occurrence, as it hasn’t worked since.

We could try connecting without HTTPS, because the self-signed certificate on the device isn’t properly recognized even if we accept all the risks.

[linuxslate]

Same issue/vote for this bug.

I often have to attempt to connect multiple times, each with a long time-out delay before I can connect.

I nearly always have to browse to https://(notes local IP address)/ in a separate browser tab, and then go back to https://client.meshtastic.org/, and attempt to connect again. If I do this, I can usually connect within about 3 tries.

Note that this may be a firmware issue since browsing to the node's IP seems to be "waking up" the nodes network connection.

Note also that in all cases, the node is steadily pingable throughout the connection attempts.

Linux Ubuntu 22.04 Tried with Firefox and Chrome.

EDIT: Additional information:
Android Client App usually connects within one or tries without connecting to the IP first.