Doesn't seem to work when 8266 is running a server application about esp_wifimanager

[khoih-prog]

Some more thoughts about the issue

The real reason behind that issue is that the ESP_WiFiManager has to run its own WebServer on port 80 to handle the Config Portal.
If you create another WebServer instance on port 80, you must be careful

1. Either to delete the previous ESP_WiFiManager's WebServer instance, when Config Portal done, before creating another one (your instance) to avoid conflict and/or memory issue because the ESP8266 WebServer library possibly permits only one instance on one port 80.

Ken Taylor's version provides a workaround by issuing a reset() to restart the board and clear the created instance after exiting the Config Portal. If you'd like, you can use this workaround (Per Ken Taylor: This is a bit crude. For some unknown reason webserver can only be started once per boot up, so resetting the device allows to go back into config mode again when it reboots.)

2. The example is just an example only for that narrow / intended use case. If you modify the example, you have to consider all the unintended possibilities.

[Wakewatcher]

Yeah I ended up just using the double reset case slightly modified so I could use double flash which was even a bit more crude. Anyway thanks for your stuff.

[khoih-prog]

Hi @Wakewatcher

Thanks for using the library and this bug report.
Could you post your code or minimized version of it along with the instructions how to duplicate the issue.