[GH-ISSUE #174] Web server connection refused, after configuration via Wi Fi Manager #137

Closed
opened 2026-02-28 01:23:38 +03:00 by kerem · 1 comment
Owner

Originally created by @DarkBeardRUS on GitHub (May 19, 2016).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/174

Hello,
Sorry for my bad english.
Maybe then he raised the topic.
But I could not find a solution to the problem.

If the device configuration via WiFiManager, then I pick up on port 80 another web server. New web server must rise to the new IP, but also on port 80, I get a connection refused.

If you restart the device, the Web server will accept connections. or if I'm going to use a port other than 80, then the same web server will accept connections.

Where can I see the solution to my problem?

Originally created by @DarkBeardRUS on GitHub (May 19, 2016). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/174 Hello, Sorry for my bad english. Maybe then he raised the topic. But I could not find a solution to the problem. **If the device configuration via WiFiManager, then I pick up on port 80 another web server. New web server must rise to the new IP, but also on port 80, I get a connection refused.** **If you restart the device, the Web server will accept connections. or if I'm going to use a port other than 80, then the same web server will accept connections.** Where can I see the solution to my problem?
kerem closed this issue 2026-02-28 01:23:38 +03:00
Author
Owner

@tzapu commented on GitHub (May 20, 2016):

hi

check example AutoConnectWithHTTPServer

cheers

<!-- gh-comment-id:220574947 --> @tzapu commented on GitHub (May 20, 2016): hi check example AutoConnectWithHTTPServer cheers
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/WiFiManager#137
No description provided.