[GH-ISSUE #1023] AP Webserver not responding after WiFiManager connected to WiFi #869

New issue

Closed

opened 2026-02-28 01:27:25 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 01:27:25 +03:00

Owner

Originally created by @CoderUni on GitHub (Mar 15, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1023

Basic Infos

Hardware

WiFimanager Branch/Release:

Master
Development

Esp8266/Esp32:

ESP8266
ESP32

ESP Core Version: 2.4.0, staging

2.3.0
2.4.0
staging (master/dev)

###Serial Monitor Log

*WM: THIS MAY CAUSE AP NOT TO START UP PROPERLY. YOU NEED TO COMMENT IT OUT AFTER ERASING THE DATA.
*WM: 
*WM: Configuring access point... 
*WM: ssid
*WM: password
*WM: Custom AP IP/GW/Subnet
*WM: AP IP address: 
*WM: 192.168.4.1
*WM: HTTP server started
*WM: WiFi save
*WM: Sent wifi save page
*WM: Connecting to new AP
*WM: Connecting as wifi client...
*WM: Status:
*WM: 0
*WM: [ERROR] WiFi.begin res:
*WM: 6
*WM: Connection result: 
*WM: 3
connected...yeey :)
192.XXX.XXX.XXX
*WM: freeing allocated params!

Description

I changed your code wherein it makes the esp8266 go STA mode after successfully connecting to a WiFi. I changed it to AP_STA mode instead of just sta mode so I can update a text in the webserver. However, this didn't go as planned because the webserver stopped responding once the esp8266 connected to the wifi. How would this be fixed?

Originally created by @CoderUni on GitHub (Mar 15, 2020). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1023 ### Basic Infos #### Hardware **WiFimanager Branch/Release:** - [x] Master - [ ] Development **Esp8266/Esp32:** - [x] ESP8266 - [ ] ESP32 **ESP Core Version: 2.4.0, staging** - [ ] 2.3.0 - [x] 2.4.0 - [ ] staging (master/dev) ###Serial Monitor Log ``` *WM: THIS MAY CAUSE AP NOT TO START UP PROPERLY. YOU NEED TO COMMENT IT OUT AFTER ERASING THE DATA. *WM: *WM: Configuring access point... *WM: ssid *WM: password *WM: Custom AP IP/GW/Subnet *WM: AP IP address: *WM: 192.168.4.1 *WM: HTTP server started *WM: WiFi save *WM: Sent wifi save page *WM: Connecting to new AP *WM: Connecting as wifi client... *WM: Status: *WM: 0 *WM: [ERROR] WiFi.begin res: *WM: 6 *WM: Connection result: *WM: 3 connected...yeey :) 192.XXX.XXX.XXX *WM: freeing allocated params! ``` ### Description I changed your code wherein it makes the esp8266 go STA mode after successfully connecting to a WiFi. I changed it to AP_STA mode instead of just sta mode so I can update a text in the webserver. However, this didn't go as planned because the webserver stopped responding once the esp8266 connected to the wifi. How would this be fixed?

kerem closed this issue

2026-02-28 01:27:26 +03:00

kerem commented

2026-02-28 01:27:26 +03:00

Author

Owner

@tablatronix commented on GitHub (Mar 15, 2020):

The webserver shutsdown when cp exits use non blocking mode in development branch

@tablatronix commented on GitHub (Mar 15, 2020): The webserver shutsdown when cp exits use non blocking mode in development branch

kerem commented

2026-02-28 01:27:26 +03:00

Author

Owner

@CoderUni commented on GitHub (Mar 16, 2020):

@tablatronix Thanks, will check it out.

@CoderUni commented on GitHub (Mar 16, 2020): @tablatronix Thanks, will check it out.