[GH-ISSUE #116] If client save connect fails , no timeout #90

New issue

Closed

opened 2026-02-28 01:23:21 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @tablatronix on GitHub (Feb 29, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/116

If you save settings , and the client connect fails, wrong password etc, the connection never fails, you have to reboot the board to get configportal back.

Would be nice to auto handle this. Running STA+AP would be neato since you get real time status, but I think that has too many issues currently ( channel switching disconnects etc.), so a timeout and restart config portal might be good enough.

not a major issue, but if you device was hard to reset...

Originally created by @tablatronix on GitHub (Feb 29, 2016). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/116 If you save settings , and the client connect fails, wrong password etc, the connection never fails, you have to reboot the board to get configportal back. Would be nice to auto handle this. Running STA+AP would be neato since you get real time status, but I think that has too many issues currently ( channel switching disconnects etc.), so a timeout and restart config portal might be good enough. not a major issue, but if you device was hard to reset...

kerem closed this issue

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

kerem commented

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

Author

Owner

@tzapu commented on GitHub (Mar 1, 2016):

this is a weird one, while the config portal is running, before connect, it is actually kind in STA + AP
(probably the issue of random issues people have)
the behaviour i get sometimes is that it fails connecting and i can click back on the config portal browser window to rescan, other times, portal config goes away, but only when wifi gets disconnected as well, and in this case i just tap the AP name, to reconnect, and re get the config portal..

this is on a ios device, and on os x, not sure how it works on others, what device are you using ? can you not just reconnect to wifi?

i am thinking of making a "safe mode" switch, that would change the current behaviour to connect to disable softAP, kill web and dns server, try to connect, if fails, start everything up again, for people that have issues currently with how it works at times...

@tzapu commented on GitHub (Mar 1, 2016): this is a weird one, while the config portal is running, before connect, it is actually kind in STA + AP (probably the issue of random issues people have) the behaviour i get sometimes is that it fails connecting and i can click back on the config portal browser window to rescan, other times, portal config goes away, but only when wifi gets disconnected as well, and in this case i just tap the AP name, to reconnect, and re get the config portal.. this is on a ios device, and on os x, not sure how it works on others, what device are you using ? can you not just reconnect to wifi? i am thinking of making a "safe mode" switch, that would change the current behaviour to connect to disable softAP, kill web and dns server, try to connect, if fails, start everything up again, for people that have issues currently with how it works at times...

kerem commented

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

Author

Owner

@kentaylor commented on GitHub (May 2, 2016):

The version at https://github.com/kentaylor/WiFiManager/ keeps the configuration portal open until it is shut down by a button press in the portal interface. This caters for the @tablatronix scenario.

When the configuration portal automatically closed and the device WiFi network automatically disappeared, as occurred previously, browsing devices usually change automatically to another WiFi network. User testing showed that most people thought they were still on the device WiFi network and interpreted the inability to access the configuration portal as the device having failed. Restarting the device didn't fix it for them as being now on another WiFi network they could still not access the configuration portal. At that point they gave up.

@kentaylor commented on GitHub (May 2, 2016): The version at https://github.com/kentaylor/WiFiManager/ keeps the configuration portal open until it is shut down by a button press in the portal interface. This caters for the @tablatronix scenario. When the configuration portal automatically closed and the device WiFi network automatically disappeared, as occurred previously, browsing devices usually change automatically to another WiFi network. User testing showed that most people thought they were still on the device WiFi network and interpreted the inability to access the configuration portal as the device having failed. Restarting the device didn't fix it for them as being now on another WiFi network they could still not access the configuration portal. At that point they gave up.