[Bug]: No webserver files on (at least) T3 and T3S3 boards.

[waltje]

Category

WiFi

Hardware

T-Lora v2 1.6

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.15.567b8ea and up

Description

I wanted to manage my T3-based nodes over WiFi, and that does not seem to work. I get "connection reset", meaning, the actual TCP connection works, but is then closed without any further action.

Logging on these nodes show the problem... yes, we have a client, but no, we don't have anything to serve 'em.

Tested this with the stable version 2.7.15, but also the newer alpha's - all the same issue.

Was this "feature" left out for these boards for space or other reasons, or is this a bug?

Relevant log output

[HTTPS:I] New connection. Socket FID=53
[HTTPS:I] Request: GET / (FID=53)
[211543][E][vfs_api.cpp:105] open(): /littlefs/static/index.html does not exist, no permits for creation
[211557][E][vfs_api.cpp:105] open(): /littlefs/static/index.html.gz does not exist, no permits for creation
[211571][E][vfs_api.cpp:105] open(): /littlefs/static/index.html.gz does not exist, no permits for creation
WARN | 21:07:39 211 [WebServer] File not available - /static/index.html.gz
E (317302) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (317302) task_wdt: - loopTask (CPU 1)
E (317302) task_wdt: Tasks currently running:
E (317302) task_wdt: CPU 0: IDLE0
E (317302) task_wdt: CPU 1: IDLE1
E (317302) task_wdt: Aborting.

[github-actions[bot]]

@waltje, Welcome to Meshtastic! 👋

Thanks for opening your first issue. If it's helpful, an easy way
to get logs is the "Open Serial Monitor" button on the Web Flasher.

If you have ideas for features, note that we often debate big ideas
in the discussions tab
first. This tracker tends to be for ideas that have community
consensus and a clear implementation.

We're very active on discord,
especially the #firmware and #alphanauts-testing channels. If you'll
be around for a while, we'd love to see you there!

Welcome to the community! ❤️

[fifieldt]

Was this "feature" left out for these boards for space or other reasons, or is this a bug?

Yes, that's correct - the baked-in client had to be removed due to space :( Around 2.7.0 or so.

You should be able to point Client.meshtastic.org to your node and connect that way :)

[waltje]

How would client.mesh.org connect to a device over TCP if nothing is 'present' in that device to support that?

[waltje]

I have meanwhile learned that the "connect through network" mode of the apps does not use http(s), but a standard TCP connection, which DOES work on these devices. Possible actions:

1. Remove http(s) support entirely from the fw code for these devices; and
2. Add the TCP connection code from the client apps to the Web Client and remove the https stuff from the web client.