-
Notifications
You must be signed in to change notification settings - Fork 271
[Bug]: Connect via HTTP(S) is not working for me #1031
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't working
Description
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
Firmware Version
2.7.15
Operating System
Windows 11
Browser
Chrome - latest
Expected Behavior
- Load client.meshtastic.org
- Attempt to connect to device's IP
- Connect to and manage device via web client
Actual Behavior
- Load client.meshtastic.org
- Attempt to connect to device's IP
- 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
- Load client.meshtastic.org
- Attempt to connect to device's IP
- Fails to connect
Relevant console output
Screenshots
No response
Additional Context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working