[GH-ISSUE #179] Unable to access html config page after few AP mode cycles #142

New issue

Closed

opened 2026-02-28 01:23:39 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 01:23:39 +03:00

Owner

Originally created by @Zyxmn on GitHub (May 31, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/179

Hi, I am unable to access the config html page after a couple AP cycles. Here is what I did to test this:

I set the config portal timeout to 3 minutes and the device enters into a permanent loop of AP cycles . I use the autoconnect() function. I enter the wrong password for the chosen ssid after scan.
The device tries to connect with the wrong password and fails and goes back to AP mode. After timeout it starts another fresh AP mode by calling the autoconnect() function again. This is where I am unable to access the html page to configure the device. Even though the last message I get on the serial monitor is the " *WM: HTTP server started".

I did notice that during AP modes where I am unable to load the html page, there are no
" *WM: 204 No Response ",
" *WM: Request redirected to captive portal " and
" *WM: Handle root "

messages on the serial monitor.

Originally created by @Zyxmn on GitHub (May 31, 2016). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/179 Hi, I am unable to access the config html page after a couple AP cycles. Here is what I did to test this: 1) I set the config portal timeout to 3 minutes and the device enters into a permanent loop of AP cycles . I use the autoconnect() function. I enter the wrong password for the chosen ssid after scan. 2) The device tries to connect with the wrong password and fails and goes back to AP mode. After timeout it starts another fresh AP mode by calling the autoconnect() function again. This is where I am unable to access the html page to configure the device. Even though the last message I get on the serial monitor is the " *WM: HTTP server started". I did notice that during AP modes where I am unable to load the html page, there are no " *WM: 204 No Response ", " *WM: Request redirected to captive portal " and " *WM: Handle root " messages on the serial monitor.

kerem closed this issue

2026-02-28 01:23:40 +03:00

kerem commented

2026-02-28 01:23:40 +03:00

Author

Owner

@tzapu commented on GitHub (Jun 2, 2016):

hi, i ve seen some issues similar to this when the module flash size was not set properly in the arduino ide

can you check that that is ok?

@tzapu commented on GitHub (Jun 2, 2016): hi, i ve seen some issues similar to this when the module flash size was not set properly in the arduino ide can you check that that is ok?

kerem commented

2026-02-28 01:23:40 +03:00

Author

Owner

@Zyxmn commented on GitHub (Jun 3, 2016):

Hi @tzapu , the flash size setting is 4M(1M SPIFFS)

Edit: I have the same issue even on 4M(3M SPIFFS) flash size.

2nd Edit: I am currently using button reset or switching off the regulator via the LDO pin and restarting the device as a work around. The board is Adafruit Huzzah.

@Zyxmn commented on GitHub (Jun 3, 2016): Hi @tzapu , the flash size setting is 4M(1M SPIFFS) Edit: I have the same issue even on 4M(3M SPIFFS) flash size. 2nd Edit: I am currently using button reset or switching off the regulator via the LDO pin and restarting the device as a work around. The board is Adafruit Huzzah.

kerem commented

2026-02-28 01:23:40 +03:00

Author

Owner

@lkeehon commented on GitHub (Aug 1, 2016):

Hi @tzapu , I'm facing similar problem based on the scenario below:
wifiManager.setAPCallback(configModeCallback);

I'm running my program and wifi was turn off thus automatically went to AP mode
Able to connect to the AP but can't go into the setting page http://192.168.4.1

However, I can go into the setting page if i reset my board. I have tried numerous time but same result. Appreciate your kind advice and thanks in advance for your kind help

Note: I did access to the AP before 3 minutes timeout.
Code
WiFiManager wifiManager;

wifiManager.setAPCallback(configModeCallback);
wifiManager.setConfigPortalTimeout(180);

if (!wifiManager.autoConnect(hostString)) {
Serial.println("failed to connect and hit timeout");

ESP.reset();
delay(1000);

}

@lkeehon commented on GitHub (Aug 1, 2016): Hi @tzapu , I'm facing similar problem based on the scenario below: wifiManager.setAPCallback(configModeCallback); 1) I'm running my program and wifi was turn off thus automatically went to AP mode 2) Able to connect to the AP but can't go into the setting page http://192.168.4.1 However, I can go into the setting page if i reset my board. I have tried numerous time but same result. Appreciate your kind advice and thanks in advance for your kind help Note: I did access to the AP before 3 minutes timeout. **Code** WiFiManager wifiManager; ``` wifiManager.setAPCallback(configModeCallback); wifiManager.setConfigPortalTimeout(180); ``` if (!wifiManager.autoConnect(hostString)) { Serial.println("failed to connect and hit timeout"); ``` ESP.reset(); delay(1000); ``` }