I’m using Chrome, latest version as of 9/23/23. Using client meshtastic org site. Using Meshtastic version 2.1.23.
The web interface works great when I’m connecting my T-beam SX1262 via USB/serial.
I’m able to turn off the bluetooth, and enable the wifi radio. I’ve successfully connected the T-beam to my home network. I can actually connect to the T-beam via my android phone Meshtastic app via it’s assigned intranet IP (192.168.x.x).
But… I can’t get the thing to connect via the client.meshtastic.org site. My Windows 10 PC is on the same network. I’ve entered in the IP correctly. I’ve even tried the meshtastic local hostname.
All it says after I click “Connect” is “Messages: Loading…”. Nothing ever connects.
My T-beam is an ESP32, so it should work, according to the Meshtastic site.
I also read on the Meshtastic site that you need to ensure the certificate is trusted in the browser to allow it to connect with https. I exported the certificate when chrome gives me the warning when I try to connect to https: at the 192.168.x.x IP, and then I’ve imported it into a lot of different places in Chrome’s security settings for managing device certificates, including: Persona, Intermediate Certificate Authorities, Trusted Root Certification Authorities, Trusted Publishers. Nothing changes. I still get the warning in Chrome if I try to connect to https: //192.168.x.x. When I use the Web interface, it still never ever connects, when both trying the 192.168.x.x address, or the meshtastic local hostname…
I know wifi works. I got to my T-beam with my android app with my smartphone on the same network.
What gives with the web client? Am I doing something wrong?
You don’t need to import the certificate anywhere. Once you go to https://yourip it’l have you confirm the certificate by agreeing to continue. Right after that the device should reset. I would also suggest doing the same with https://meshtastic.local
When I try to connect with https to the IP and to the hostname, I get the screen that has the Red triangle with exclamation point that says:
“Your connection is not private
Attackers might be trying to steal you information from meshtastic.local (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
To get Chrome’s highest level of security, turn on enhanced protection”
If i click “Advanced”:
“This server could not prove that it is meshtastic.local; its security certificate is not trusted by your computers operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to meshtastic local (unsafe)”
If I click the proceed, it then says:
This site can’t be reached.
meshtastic local unexpectedly closed the connection.
try
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics.
Unfortunately, on the current version of Chrome, there is no where for me to confirm the certificate.
Crichton is correct, you should be able to hit the proceed button within Chrome and move past the certificate warning. But there is a big list of reasons why the security settings on your PC might not allow you to bypass an untrusted certificate, both within Chrome and the Windows OS. Going through it all is kind of a PITA, and getting your PC to trust the certificate should fix most of those problems without being as much work. If you’re able to get it working by hitting “Proceed Anyway,” then that would be the smart thing. But if that doesn’t work…
You would not be uploading anything. You’d open the MMC management console on your PC, and then install the cert into your machine’s local personal store. Doing so should get your PC to stop throwing a security warning every time you access the device using HTTPS. There is more than one way to accomplish this:
I’ve tried those methods for importing the certificate many many times. Rebooted, restarted Chrome, etc.
Still having the same issues. When trying to load up meshtastic.local or by using the IP on the network, the Web Client still just shows a constant: “Messages: Loading…”
Should I be trying a different firmware? I’m using the most recent beta for the T-beam…
Also, as an aside, Chrome never gives me any option beside “proceed to meshtastic local (unsafe)…” when trying to connect directly to the T-beam with https. Once I click that, I get no where.
All I get is the following webpage error:
“This site can’t be reached
The connection was reset.
Try
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics.”
After all of this, the Web Interface still won’t work. BUT…if I then go to my Meshtastic android app, on my phone on the same network, I can easily connect to the T-beam using the IP using WiFi.
Does anyone know if this is an issue with the firmware or with the current version of the web interface???
Finally, I was just looking around the settings in the T-beam using the serial connection. I saw that TLS was disabled under the MQTT Module Config. I enabled it, thinking this would change things. Unfortunately, nothing changed. Still same behavior. (Should TLS be enabled or disabled?) I changed it back, seeing that this setting was specific for the MQTT module…
I had the same issue. If the wifi signal is not excellent then all the http traffic takes a while and can easily timeout. Does it work via client.meshtastic.org if you bring the node in close range of your wireless router/ap ?
I moved it closer, and got a better RSSI signal strength. But, it still doesn’t connect to any of my Windows devices via Chrome or Edge using client.meshtastic.org.
It still connects perfectly via WiFi via my android Meshtastic app. There must be something I’m not doing right.
Huh. Funny thing… When I connect to the device without https…
That is, http://192.168.x.x, it now lets me connect to the web interface served up on the ESP32 device, and NOW I can finally connect to the device and change settings, send messages, etc.
But, I still can’t get client.meshtastic.org’s site to work, which requires https to be used.
Any more hints? This is the furthest I’ve gotten so far! Thanks!
I’m concluding that the firmware’s http and https interfaces with the web/chrome clients aren’t perfected, yet. The android app seems to work great, though.
Will be waiting for the firmware improvements to the WiFi interface with https and http.
I’m seeing the same behaviour. client.meshtastic works fine over serial but not http. All I see in the network activity is failed requests for hotspot-detect.html
