mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 17:15:53 +03:00
[GH-ISSUE #604] Unable to start webserver after "Exit". - softAPdisconnect FAILED #504
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#504
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MichMich on GitHub (May 1, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/604
Basic Infos
Hardware
WiFimanager Branch/Release: Development
Esp8266/Esp32: ESP32 Wemos Lolin32 OLED
Hardware: ESP32 Wemos Lolin32 OLED
Core Version: Latest.
Description
Id like to start a webserver after the "Exit" button in the config screen is pressed. In this case I want to run, or keep running the ESP32 in AP mode, and use the softAP mode to allow the user to continue with a direct connection to the ESP.
After I press the Exit button, I can connect to the ESP, but the webserver (WebServer_tng) is unable to start on port 80. When I use port 8080 it works without any issues.
When I check the serial log of WiFi manager, the following is interesting:
As you can see, it gives an error.
Settings in IDE
Module: lolin32
@tablatronix commented on GitHub (May 1, 2018):
#545
@tablatronix commented on GitHub (May 1, 2018):
can you reproduce with this gist?
https://gist.github.com/tablatronix/e57dc3096ea311dd0e59aa512b8fe6e7
@tablatronix commented on GitHub (May 1, 2018):
*WM: [ERROR] disconnect configportal - softAPdisconnect FAILEDwas fixed in the esp32 lib, you must not be running the latest core
@MichMich commented on GitHub (May 2, 2018):
Ah, I'll update to the latest core, and check again. Thanks!