Let's Control It

Hello. I have a strange problem. There were 4 devices on ESP Easy, all worked. ESP-01, ESP-01S, 2xWemos D1 mini. At some point Web interface WMOS stopped working - addr_unreachable. Then the rest stopped. In the terminal, with no errors - the device works and transmits data. I tried to reflash, use other devices - everything is still. Thought the problem in the router - no. I changed the router, I tried on another network - there is no web interface. I tried Tasmota - the same nonsense. Where to look for a problem? Please tell me.

Is your webbrowser in the same network IP-range as your ESP's ?
Did you configure the "Client IP-Filtering" setting on the Config tab to "Allow IP range" ?
Have you tried a different browser ? Background: The latest Firefox and Chrome make it harder on every update to connect to plain http sites, even in the local network.
Do you have a browser plugin like https-everywhere active ?
What version of ESPEasy are you using on your devices ? (Filename is in the Info page "Binary Filename")

Ath wrote: ↑02 Mar 2022, 10:50 Did you configure the "Client IP-Filtering" setting on the Config tab to "Allow IP range" ?

Perhaps this should be default to "Allow All" to avoid issues of this nature ?

Yes, all devices in one network.
No, after the first start and setting up the ssid/pass, the device reboot, connecting to the network and i can not go to it.
Yes, i tried more browser: chrome/ff old and new, mypal, kode, opera. All browser without any plugins and with disabled compression\proxy\vpn\etc.
Firmware INIT : Booting version: mega-20211224_f162ebf (ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support)

iron wrote: ↑02 Mar 2022, 11:02 Perhaps this should be default to "Allow All" to avoid issues of this nature ?

The disadvantage of that is that probably nobody will ever change it to the somewhat more secure "Allow Local Subnet" or most secure available "Allow IP range" setting. Will discuss this with TD-er, but I suspect we'll keep current default.

xorkrus wrote: ↑02 Mar 2022, 11:39 Firmware INIT : Booting version: mega-20211224_f162ebf (ESP82xx Core 2843a5ac, NONOS SDK 2.2.2-dev(38a443e), LWIP: 2.1.2 PUYA support)

Well, that's the most recent Release available, so should be quite OK.

You could download the latest "mega" build that has the Arduino 3.0 update merged now, but not yet released as a new Nightly, where many, many, framework bugs have been solved. Get that from here: https://github.com/letscontrolit/ESPEas ... 1872632694
Download the Binaries.zip file, and get the .bin from the .zip file using the same build name you used before

Ath wrote: ↑02 Mar 2022, 11:49
... to the somewhat more secure "Allow Local Subnet" or most secure available "Allow IP range" setting...

A "more secure" http huh ?

iron wrote: ↑02 Mar 2022, 13:40

Ath wrote: ↑02 Mar 2022, 11:49
... to the somewhat more secure "Allow Local Subnet" or most secure available "Allow IP range" setting...

A "more secure" http huh ?

I should probably have written "... to the somewhat more secure "Allow Local Subnet" or..."
At least access is prohibited when trying to access the node from another LAN segment

Can you do a simple PING from your computer to the ESP devices and get a response?