mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #641] connected to esp8266 network but could not open config portal?? #538
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#538
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 @a-c-sreedhar-reddy on GitHub (Jul 4, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/641
I am using Nodemcu.
Autoconnect("appp").
It creates a network. But when I connect to it sometimes I am not able to open config portal. Then I need to restart Nodemcu.
I am using the latest version of WifiManager.
@a-c-sreedhar-reddy commented on GitHub (Jul 4, 2018):
I commented captive portal stuff in the library and I feel it is working fine then.
@tablatronix commented on GitHub (Jul 4, 2018):
captive portal was breaking your connection?
@a-c-sreedhar-reddy commented on GitHub (Jul 5, 2018):
Don't know.
Even after disabling captive portal I could not open 192.168.4.1
When I open 192.168.4.1 "Handle root " is printed on serial monitor, but the page is not loaded.
Then I need to restart my board ( NODEMCU , esp01)
@a-c-sreedhar-reddy commented on GitHub (Jul 5, 2018):
[ SOLVED ]
In the startConfigPortal function I changed the Wifi mode from AP_STA to AP.
It worked..
I think the problem is when more networks are present in our location and WIFI is in AP_STA mode then it would take long time to handle requests.
@tablatronix commented on GitHub (Jul 5, 2018):
Yeah this is fixed in hotfixes branch