[GH-ISSUE #1579] Web Server doesn't starts after Wifi connected through WiFiManager

kerem commented

2026-02-28 01:29:42 +03:00

Owner

Originally created by @patelabhi23 on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1579

I am using ESP32 Wroom DA module. When I connect to the WiFi Manager AP & then save new WiFi credentials then the Web Server doesn't starts. It gets the IP & Internet Connection but when I open WebServer HTTTP404 error. I am using AsyncWebServer instead of the WebServer.

Currently, if I do hard reset of the ESP then the WebServer starts working, but instead of Hard Reset on ESP I would like to do with the code itself.

Originally created by @patelabhi23 on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1579 I am using ESP32 Wroom DA module. When I connect to the WiFi Manager AP & then save new WiFi credentials then the Web Server doesn't starts. It gets the IP & Internet Connection but when I open WebServer HTTTP404 error. I am using AsyncWebServer instead of the WebServer. Currently, if I do hard reset of the ESP then the WebServer starts working, but instead of Hard Reset on ESP I would like to do with the code itself.

kerem

2026-02-28 01:29:42 +03:00

closed this issue
added the
Upstream/Dependancy
label

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@Bighoneypot commented on GitHub (Mar 29, 2023):

@patelabhi23 can you paste your full code and write your the result you expected?

@Bighoneypot commented on GitHub (Mar 29, 2023): @patelabhi23 can you paste your full code and write your the result you expected?

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (Mar 29, 2023):

@Bighoneypot yes here is the code:

#include <WiFiManager.h>
WiFiManager wm;
#include "ESPAsyncWebServer.h"

AsyncWebServer server ( 80 );

void setup() {
  Serial.begin(9600);

  wm.resetSettings();

  bool res;
  res = wm.autoConnect("Abc", "123"); 

  if (!res) {
    Serial.println("Failed to connect");
  }
  else {
    Serial.println("connected...yeey :)");
    ESP.restart();
  }

}

void beginServer()
{
  server.reset();

  server.on("/", HTTP_GET, [](AsyncWebServerRequest * request) {
    request->send(200, "text/html", webPage());
    delay(1000);
    ESP.restart();
  });
  server.begin();
  Serial.println ( "HTTP server started" );
}

void loop() {
  Serial.println(WiFi.localIP());
  beginServer();
  delay(5000);
}

String webPage() {
  String ptr = "<!DOCTYPE html> <html>\n";
  ptr += "<body>\n";
  ptr += "<p>Hello World</p>";
  ptr += "</body>\n";
  ptr += "</html>\n";
  return ptr;
}

Once the Wifi is configured then it prints the IP address but when I open the webpage using that IP it shows that "This site can't be reached"

@patelabhi23 commented on GitHub (Mar 29, 2023): @Bighoneypot yes here is the code: ``` #include <WiFiManager.h> WiFiManager wm; #include "ESPAsyncWebServer.h" AsyncWebServer server ( 80 ); void setup() { Serial.begin(9600); wm.resetSettings(); bool res; res = wm.autoConnect("Abc", "123"); if (!res) { Serial.println("Failed to connect"); } else { Serial.println("connected...yeey :)"); ESP.restart(); } } void beginServer() { server.reset(); server.on("/", HTTP_GET, [](AsyncWebServerRequest * request) { request->send(200, "text/html", webPage()); delay(1000); ESP.restart(); }); server.begin(); Serial.println ( "HTTP server started" ); } void loop() { Serial.println(WiFi.localIP()); beginServer(); delay(5000); } String webPage() { String ptr = "<!DOCTYPE html> <html>\n"; ptr += "<body>\n"; ptr += "<p>Hello World</p>"; ptr += "</body>\n"; ptr += "</html>\n"; return ptr; } ``` Once the Wifi is configured then it prints the IP address but when I open the webpage using that IP it shows that "This site can't be reached" ![image](https://user-images.githubusercontent.com/65539389/228534166-b06a6138-060a-4dce-8a9a-f1eb9bde4c05.png)

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (Mar 29, 2023):

There is a problem in esp with reopening a port for example opening another webserver even after one is closed. There is an issue we never figured it out

@tablatronix commented on GitHub (Mar 29, 2023): There is a problem in esp with reopening a port for example opening another webserver even after one is closed. There is an issue we never figured it out

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (Mar 29, 2023):

@tablatronix
I am using the below attached ESP32 Board

Also I have tried doing the same in other ESP boards as if this ESP board might be damaged but it wasn't the case. In multiple ESP boards I have faced the same issue.

I have also gone through the #545 where you have resolved for the simple WebServer and not the AsyncWebServer.

@patelabhi23 commented on GitHub (Mar 29, 2023): @tablatronix I am using the below attached ESP32 Board ![image](https://user-images.githubusercontent.com/65539389/228541803-171962e7-0ec3-4568-8c8c-78acacd487ec.png) Also I have tried doing the same in other ESP boards as if this ESP board might be damaged but it wasn't the case. In multiple ESP boards I have faced the same issue. I have also gone through the #545 where you have resolved for the simple WebServer and not the AsyncWebServer.

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (Mar 29, 2023):

Yeah you cannot run 2 webservers even if you close one the port is not free have to reatart

@tablatronix commented on GitHub (Mar 29, 2023): Yeah you cannot run 2 webservers even if you close one the port is not free have to reatart

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (Mar 29, 2023):

So you mean to say that wifimanager library doesn't supports two webservers?

@patelabhi23 commented on GitHub (Mar 29, 2023): So you mean to say that wifimanager library doesn't supports two webservers?

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@Bighoneypot commented on GitHub (Mar 29, 2023):

Yeah you cannot run 2 webservers even if you close one the port is not free have to reatart

This is the problem, you can't run 2 webservers @patelabhi23

@Bighoneypot commented on GitHub (Mar 29, 2023): > Yeah you cannot run 2 webservers even if you close one the port is not free have to reatart This is the problem, you can't run 2 webservers @patelabhi23

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (Mar 29, 2023):

@Bighoneypot I am closing the same port & again reopening it then too why it isn't working. Also you have the option of multiple ports in ESP32 & I am running multiple ports by saving the Wifi credentials in the code, but once I integrate wifimanager everything stops out

@patelabhi23 commented on GitHub (Mar 29, 2023): @Bighoneypot I am closing the same port & again reopening it then too why it isn't working. Also you have the option of multiple ports in ESP32 & I am running multiple ports by saving the Wifi credentials in the code, but once I integrate wifimanager everything stops out

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (Mar 29, 2023):

Its an ESP BUG! ports are not released, run it on a different port I bet it works, or restart if the portal was started

@tablatronix commented on GitHub (Mar 29, 2023): Its an ESP BUG! ports are not released, run it on a different port I bet it works, or restart if the portal was started

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (Mar 29, 2023):

@tablatronix

could you suggest any solution on how to solve that esp bug or even how to debug that?
I have already added the esp restart in the snippet above but then too it isn't working, so any alternatives for that?

@patelabhi23 commented on GitHub (Mar 29, 2023): @tablatronix 1. could you suggest any solution on how to solve that esp bug or even how to debug that? 2. I have already added the esp restart in the snippet above but then too it isn't working, so any alternatives for that?

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (Mar 31, 2023):

Its deep inside the wifiserver library, I am not very familiar with it but I never figured out or even got anywhere.

There might be a conflict between async and regular webserver libraries also , have you tried running both without wm?
I am working on the async branch to get it switchable

@tablatronix commented on GitHub (Mar 31, 2023): Its deep inside the wifiserver library, I am not very familiar with it but I never figured out or even got anywhere. There might be a conflict between async and regular webserver libraries also , have you tried running both without wm? I am working on the async branch to get it switchable

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (Mar 31, 2023):

Yes when I run without wm both of them works well but on integrating with wm it causes issue.

Also the esp.restart isn't working in that case so any alternatives for that?

@patelabhi23 commented on GitHub (Mar 31, 2023): Yes when I run without wm both of them works well but on integrating with wm it causes issue. Also the esp.restart isn't working in that case so any alternatives for that?

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (May 1, 2023):

@tablatronix as per this were you able to make the async branch switchable?

Its deep inside the wifiserver library, I am not very familiar with it but I never figured out or even got anywhere.

There might be a conflict between async and regular webserver libraries also , have you tried running both without wm? I am working on the async branch to get it switchable

@patelabhi23 commented on GitHub (May 1, 2023): @tablatronix as per this were you able to make the async branch switchable? > Its deep inside the wifiserver library, I am not very familiar with it but I never figured out or even got anywhere. > > There might be a conflict between async and regular webserver libraries also , have you tried running both without wm? I am working on the async branch to get it switchable

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (May 1, 2023):

No but I will try to get some traction on it this week and try to get some releases out

@tablatronix commented on GitHub (May 1, 2023): No but I will try to get some traction on it this week and try to get some releases out

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@SVLoneStar commented on GitHub (May 8, 2023):

Any news on this?
Alternatively...is there a way to start WifiManager listening on a port other than 80? Thx!

@SVLoneStar commented on GitHub (May 8, 2023): Any news on this? Alternatively...is there a way to start WifiManager listening on a port other than 80? Thx!

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (May 10, 2023):

No not any yet as the asyncwebserver trys to reopen the same port but it isn't being able to do so.

Any news on this? Alternatively...is there a way to start WifiManager listening on a port other than 80? Thx!

@patelabhi23 commented on GitHub (May 10, 2023): No not any yet as the asyncwebserver trys to reopen the same port but it isn't being able to do so. > Any news on this? Alternatively...is there a way to start WifiManager listening on a port other than 80? Thx!

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@patelabhi23 commented on GitHub (May 10, 2023):

@tablatronix any updates?

No but I will try to get some traction on it this week and try to get some releases out

@patelabhi23 commented on GitHub (May 10, 2023): @tablatronix any updates? > No but I will try to get some traction on it this week and try to get some releases out

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (May 11, 2023):

#1121

@tablatronix commented on GitHub (May 11, 2023): #1121

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@kjyv commented on GitHub (May 29, 2023):

Why was this closed? The bug is still there and the linked ticket seems related, but is not a duplicate or superset of this one

@kjyv commented on GitHub (May 29, 2023): Why was this closed? The bug is still there and the linked ticket seems related, but is not a duplicate or superset of this one

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@tablatronix commented on GitHub (May 29, 2023):

Because its a bug In ESP not wm, and i have no workaround for it

@tablatronix commented on GitHub (May 29, 2023): Because its a bug In ESP not wm, and i have no workaround for it

kerem commented

2026-02-28 01:29:43 +03:00

Author

Owner

@khoint2101 commented on GitHub (Jun 12, 2023):

Bất kỳ tin tức về điều này? Ngoài ra... có cách nào để bắt đầu nghe WifiManager trên cổng khác 80 không? Thx!

Any news on this? Alternatively...is there a way to start WifiManager listening on a port other than 80? Thx!

You can open custom port for WM lib. You can use to
WiFiManager wm; wm.setHttpPort(8080);
This is open port 8080 for wifimanager web config, but when you login to wifi, you must type: 192.168.4.1:8080 to open web.
When using the other port, webserver will start after success config wifi. DON'T NEED Hard Reset :>

@khoint2101 commented on GitHub (Jun 12, 2023): > Bất kỳ tin tức về điều này? Ngoài ra... có cách nào để bắt đầu nghe WifiManager trên cổng khác 80 không? Thx! > Any news on this? Alternatively...is there a way to start WifiManager listening on a port other than 80? Thx! You can open custom port for WM lib. You can use to `WiFiManager wm; wm.setHttpPort(8080); ` This is open port 8080 for wifimanager web config, but when you login to wifi, you must type: 192.168.4.1:8080 to open web. When using the other port, webserver will start after success config wifi. DON'T NEED Hard Reset :>

Rows
Columns

[GH-ISSUE #1579] Web Server doesn't starts after Wifi connected through WiFiManager #1348