-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webserver unreachable with static IP set. #1291
Comments
I had the exact same problem. |
Yesterday I added a commit that should solve this. |
I try latest release, bat not working. thx |
No issue here with static IP. 😁 |
@stafil What do you mean with "bat not working" ? |
Hello, I have also encountered an issue after upgrade from mega 2.0.0 dev 11 to mega-20180421 test on NodeMCU Amica. There's a rule which beeps on a boot and use IR receiver plugin to control relay. No other plugin is used. Also the Fixed IP Octet is configured. After the successfull OTA firmware upgrade the device rebooted itself, then I heard 3 beeps (so three times rebooted), then I could access it on configured fixed IP address by PING but the web interface is not accessible anymore. When unplugged from power and plug again, several beeps heard (first almost immediately, next after about 10 sec) until device get connected to AP. The IR plugin and rule looks working but the web interface is dead. |
Hi am facing the same problem: no access to the web interface. |
Tried 20180421 version with DHCP but could not access webinterface either. |
I don't know what you guys are doing, but I flashed the firmware from tonight, just to reproduce your issues, but it works!
TD-er made all right. So, you are making something wrong! |
Like I said in another thread, there are a lot of issues which are hard to reproduce. |
This was a test under real conditions. I installed it on a fresh and clean flash chip. Only so you can be sure, that there is no crap left from a previous installation or config. No task, no rule, yet. And that works! ;-) |
I have check both settings. For me DHCP and Static IP work. I do a reset (factoryreset) between the two settings. My version is mega-20180421 build in platformIo. Hardware is NodeMCU 1.0 amica ESP8266. |
Feuerreiter, |
Just tried to reset settings through serial console, configured only wifissid and wifikey, saved settings and rebooted. After reboot ESP connected to AP, reported Settings CRC FAIL, it's accessible via PING but the web console is still dead... So it looks there's an issue with saving config and even reset does not help. Any hint what could be tested except total ESP clear?
ets Jan 8 2013,rst cause:4, boot mode:(3,6) wdt reset ... INIT : Booting version: mega-20180421 (ESP82xx Core 2_4_0) |
You're not running the latest code. |
Yes that's the latest release with settings CRC, I did not update to today's code yet just for the case if there's anything to be debugged. .... I was able to connect and see the WiFi select webpage 8035506 : WD : Uptime 122 ConnectFailures 0 FreeMem 13728 .....
|
Hi, |
Can you add a log via serial output, with the log level set to "Debug More" ? Is it a binary built in the daily build, or one you built yourself? |
with new version work fine, thx
---------- Původní e-mail ----------
Od: Gijs Noorlander <notifications@github.com>
Komu: letscontrolit/ESPEasy <ESPEasy@noreply.github.com>
Datum: 1. 5. 2018 18:24:59
Předmět: Re: [letscontrolit/ESPEasy] Webserver unreachable with static IP
set. (#1291)
"
Can you add a log via serial output, with the log level set to "Debug More"
?
That level does include the internal log of the Arduino library, which
states enable/disable of DHCPclient.
Is it a binary built in the daily build, or one you built yourself?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
(#1291 (comment))
, or mute the thread
(https://github.com/notifications/unsubscribe-auth/AD4UE0UVeALexUBTGxzZ4-sP79rISiahks5tuIxVgaJpZM4TeOzE)
.
"
|
with new version work fine, thx
---------- Původní e-mail ----------
Od: IlluminatMartin <notifications@github.com>
Komu: letscontrolit/ESPEasy <ESPEasy@noreply.github.com>
Datum: 1. 5. 2018 14:03:36
Předmět: Re: [letscontrolit/ESPEasy] Webserver unreachable with static IP
set. (#1291)
"
Hi,
I has also instaled today the last version (ESP_Easy_mega-20180501_test_ESP
8266_4096) and my static IP is also not working. the modules use the IP from
DHCP what they get from the initial phase.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
(#1291 (comment))
, or mute the thread
(https://github.com/notifications/unsubscribe-auth/AD4UE0NsCvzU0I6GgCPJPtUIecLnuHe0ks5tuE8UgaJpZM4TeOzE)
.
"
|
Hi, thanks |
OK, that's an interesting point you make. |
Was a left-over remark in letscontrolit#1291
The last remark is now implemented in PR #1901 |
Summarize of the problem/feature request
WEmos D1 Mini.
When I set static ip, webserver unreachable, serial debug output as follows. Always shows NTP server unreachable.
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v4ceabea9
~ld
⸮⸮⸮U60 :
INIT : Booting version: mega-20180420 (core 2_4_0)
60 : INIT : Warm boot #7
61 : FS : Mounting...
86 : FS : Mount successful, used 75802 bytes of 957314
405 : CRC : program checksum ...OK
409 : CRC : Settings CRC ...FAIL
411 : CRC : SecuritySettings CRC ...OK
517 : INIT : Free RAM:18432
518 : INIT : I2C
518 : INIT : SPI not enabled
534 : INFO : Plugins: 72 [Normal] [Testing] [Development] (core 2_4_0)
534 : WIFI : Switch on WiFi
535 : WIFI : Set WiFi to STA
536 : WIFI : Connecting NSA attempt #0
555 : WD : Uptime 0 ConnectFailures 0 FreeMem 17696
3614 : WIFI : Connected! AP: NSA (2C:30:33:F6:EA:27) Ch: 6 Duration: 3076 ms
3614 : IP : Static IP : 192.168.10.60 GW: 192.168.10.1 SN: 255.255.255.0 DNS: 192.168.10.1
3618 : WIFI : Static IP: 192.168.10.60 (ESP-Easy-0) GW: 192.168.10.1 SN: 255.255.255.0 duration: 5 ms
3640 : Webserver: start
14219 : Host unreachable: 0.0.0.0
14219 : NTP : NTP host 0.us.pool.ntp.org (0.0.0.0) unreachable
Expected behavior
YOUR TEXT GOES HERE
Actual behavior
YOUR TEXT GOES HERE
Steps to reproduce
System configuration
Hardware:
ESP Easy version: mega-20180420 (core 2_4_0) also occurred on 2018417 build
ESP Easy settings/screenshots:
Rules or log data
The text was updated successfully, but these errors were encountered: