[GH-ISSUE #788] Can't open "Configure WiFi" page with my phone #658

Open
opened 2026-02-28 01:26:26 +03:00 by kerem · 5 comments
Owner

Originally created by @AlcorDust on GitHub (Dec 18, 2018).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/788

Hello, i'm using wifiManager on my NodeMCU. Here's the details:

Board: nodeMCU 1.0
4M (3M SPIFFS)
Upload speed 115300
Frequency 80 MHz

I uploaded the example "AutoConnect", and i'm able to connect and see the main page on my smartphone. The problem is that i can't open the page "Configure wifi" when i press the button. I tried to connect to the AP with my laptop and It works correctly. Is it a smartphone problem? I have a Huawei P9 Lite.

Originally created by @AlcorDust on GitHub (Dec 18, 2018). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/788 Hello, i'm using wifiManager on my NodeMCU. Here's the details: Board: nodeMCU 1.0 4M (3M SPIFFS) Upload speed 115300 Frequency 80 MHz I uploaded the example "AutoConnect", and i'm able to connect and see the main page on my smartphone. The problem is that i can't open the page "Configure wifi" when i press the button. I tried to connect to the AP with my laptop and It works correctly. Is it a smartphone problem? I have a Huawei P9 Lite.
Author
Owner

@tablatronix commented on GitHub (Dec 18, 2018):

sounds like maybe there is an html problem, try development branch ?

<!-- gh-comment-id:448303937 --> @tablatronix commented on GitHub (Dec 18, 2018): sounds like maybe there is an html problem, try development branch ?
Author
Owner

@AlcorDust commented on GitHub (Dec 19, 2018):

Hi, i tried development branch. Using the "Basic" example sketch i can't even open the main page. I'm going to try older versions of the library!

<!-- gh-comment-id:448744443 --> @AlcorDust commented on GitHub (Dec 19, 2018): Hi, i tried development branch. Using the "Basic" example sketch i can't even open the main page. I'm going to try older versions of the library!
Author
Owner

@AlcorDust commented on GitHub (Dec 19, 2018):

Here's what i did:

  • I tried with older versions but nothing changed.
  • I used 2 ESP8266, with the same result.
  • If i open the serial monitor i read this:
    *WM: 192.168.4.1
    *WM: HTTP server started
    *WM: Handle root
    *WM: Request redirected to captive portal
    *WM: Request redirected to captive portal
    *WM: Handle root
    *WM: Request redirected to captive portal
    *WM: Request redirected to captive portal
    *WM: Handle root
    *WM: Handle root
    *WM: Request redirected to captive portal
    *WM: Handle root
    *WM: Request redirected to captive portal
    *WM: Handle root
    *WM: Request redirected to captive portal
    *WM: Handle root
    *WM: Handle root
    *WM: Handle root
    *WM: Scan done
    *WM: DUP AP: WOW FI - FASTWEB
    *WM: DUP AP: Vodafone-Guest
    *WM: FASTWEB-1-55D705
    *WM: -58
    *WM: WOW FI - FASTWEB
    *WM: -58
    *WM: InfostradaWiFi-012943
    *WM: -61
    *WM: TIM-21030679
    *WM: -72
    *WM: Vodafone-A45210187
    *WM: -72
    *WM: Vodafone-WiFi
    *WM: -73
    *WM: Vodafone-Guest
    *WM: -75
    *WM: FASTWEB-B836B7
    *WM: -87
    *WM: Vodafone-33898704
    *WM: -88
    *WM: Vodafone-A74575006
    *WM: -92
    *WM: DIRECT-22-HP OfficeJet 4650
    *WM: -92
    *WM: Sent config page
    *WM: Request redirected to captive portal
    *WM: Handle root
<!-- gh-comment-id:448751026 --> @AlcorDust commented on GitHub (Dec 19, 2018): Here's what i did: - I tried with older versions but nothing changed. - I used 2 ESP8266, with the same result. - If i open the serial monitor i read this: *WM: 192.168.4.1 *WM: HTTP server started *WM: Handle root *WM: Request redirected to captive portal *WM: Request redirected to captive portal *WM: Handle root *WM: Request redirected to captive portal *WM: Request redirected to captive portal *WM: Handle root *WM: Handle root *WM: Request redirected to captive portal *WM: Handle root *WM: Request redirected to captive portal *WM: Handle root *WM: Request redirected to captive portal *WM: Handle root *WM: Handle root *WM: Handle root *WM: Scan done *WM: DUP AP: WOW FI - FASTWEB *WM: DUP AP: Vodafone-Guest *WM: FASTWEB-1-55D705 *WM: -58 *WM: WOW FI - FASTWEB *WM: -58 *WM: InfostradaWiFi-012943 *WM: -61 *WM: TIM-21030679 *WM: -72 *WM: Vodafone-A45210187 *WM: -72 *WM: Vodafone-WiFi *WM: -73 *WM: Vodafone-Guest *WM: -75 *WM: FASTWEB-B836B7 *WM: -87 *WM: Vodafone-33898704 *WM: -88 *WM: Vodafone-A74575006 *WM: -92 *WM: DIRECT-22-HP OfficeJet 4650 *WM: -92 *WM: Sent config page *WM: Request redirected to captive portal *WM: Handle root
Author
Owner

@tablatronix commented on GitHub (Dec 19, 2018):

Yeah sounds like a problem with captive portal, can you connect to ap fine and goto the ip address?

Could be a security setting, some android has locked down captive portals for some ips

<!-- gh-comment-id:448767056 --> @tablatronix commented on GitHub (Dec 19, 2018): Yeah sounds like a problem with captive portal, can you connect to ap fine and goto the ip address? Could be a security setting, some android has locked down captive portals for some ips
Author
Owner

@tablatronix commented on GitHub (Dec 19, 2018):

Develoment has the most debugging, you should test without captiveportal first

<!-- gh-comment-id:448767747 --> @tablatronix commented on GitHub (Dec 19, 2018): Develoment has the most debugging, you should test without captiveportal first
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#658
No description provided.