[Bug]: Connect via HTTP(S) is not working for me

[scarolan]

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

T-Beam

Connection Type

HTTP

Local or Hosted

https://client.meshtastic.org

Firmware Version

2.7.15

Operating System

Windows 11

Browser

Chrome - latest

Expected Behavior

1. Load client.meshtastic.org
2. Attempt to connect to device's IP
3. Connect to and manage device via web client

Actual Behavior

1. Load client.meshtastic.org
2. Attempt to connect to device's IP
3. Fails to connect

The device is confirmed up by both ping and nmap.

❯ sudo nmap -p 80,443 192.168.1.139 -Pn
Starting Nmap 7.94SVN ( https://nmap.org ) at 2026-03-15 15:01 EDT
Nmap scan report for 192.168.1.139
Host is up (0.011s latency).

PORT    STATE SERVICE
80/tcp  open  http
443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds

Steps to Reproduce

1. Load client.meshtastic.org
2. Attempt to connect to device's IP
3. Fails to connect

Relevant console output

Screenshots

No response

Additional Context

No response

[roberthadow]

My experience with client.meshtastic.org using http or https is this:
(1) Add new connection. Select an IP address known to be active on the local network. The "Use HTTPS" toggle is deactivated.
(2) Test the connection. After three tries it fails. The popup recmmends opening a browser session with the iP address and accepting security risks.
(3) The IP address opens a session with the device, with the device stub server appearing "Web server is running."
(4) At a second test of connection, client.meshtastic.org says the connections is not reachable. The Save button doesn't work.

I confirm @scarolan 's observation. Connect via HTTP(S) is not working for me