Does the CaptivePortal example work for you on either Android or IOS?
And do you have
#define DEBUG
Explore... Chat... Share...
Moderator: igrr
#define DEBUG
burkmurray wrote:Glad to hear it works in IOS!
Does the CaptivePortal example work for you on either Android or IOS?
And do you haveCode: Select alluncommented in ESP8266WebServer.cpp? It's not especially verbose, but it'll show responses from the ESP in your serial console.#define DEBUG
DNS responds: 192.168.1.1 for connectivitycheck.android.com
DNS responds: 192.168.1.1 for settings.crashlytics.com
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for mtalk.google.com
DNS responds: 192.168.1.1 for googleadservices.com
DNS responds: 192.168.1.1 for connectivitycheck.android.com
DNS responds: 192.168.1.1 for settings.crashlytics.com
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for mtalk.google.com
DNS responds: 192.168.1.1 for googleadservices.com
DNS responds: 192.168.1.1 for connectivitycheck.android.com
DNS responds: 192.168.1.1 for settings.crashlytics.com
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for mtalk.google.com
DNS responds: 192.168.1.1 for googleadservices.com
DNS responds: 192.168.1.1 for connectivitycheck.android.com
DNS responds: 192.168.1.1 for settings.crashlytics.com
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for mtalk.google.com
DNS responds: 192.168.1.1 for graph.facebook.com
DNS responds: 192.168.1.1 for googleadservices.com
DNS responds: 192.168.1.1 for connectivitycheck.android.com
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for time-a.nist.gov
DNS responds: 192.168.1.1 for android.clients.google.com
DNS responds: 192.168.1.1 for graph.facebook.com
DNS responds: 192.168.1.1 for connectivitycheck.android.com
DNS responds: 192.168.1.1 for teredo.ipv6.microsoft.com
DNS responds: 192.168.1.1 for teredo.ipv6.microsoft.com
DNS responds: 192.168.1.1 for teredo.ipv6.microsoft.com
DNS responds: 192.168.1.1 for teredo.ipv6.microsoft.com
DNS responds: 192.168.1.1 for teredo.ipv6.microsoft.com
DNS responds: 192.168.1.1 for google.com
DNS responds: 192.168.1.1 for google.com
DNS responds: 192.168.1.1 for google.com
DNS responds: 192.168.1.1 for google.com
DNS responds: 192.168.1.1 for google.com
DNS responds: 192.168.1.1 for blah.com
For fun, I added some debugging in DNSServer.ccp to see what Android was doing as soon as it connects. This is what it spits out.
...
DNS responds: 192.168.1.1 for connectivitycheck.android.com
server.on("connectivitycheck.android.com", handle_root);
"<!DOCTYPE html><html><head><title>Success</title></head><body>"
It takes about 20-25 seconds for home assistant c[…]
I tried to upgrade tof my sonoff basic R2 with the[…]
a problem Perhaps you want to define "Probl[…]
Rebooting your router will not give you a faster I[…]
There are no other notifications from esptool.py i[…]
Using the Arduino IDE, you'll learn how to set up […]
In this project, you will post to Twitter using an[…]
In this project, we will build a water level contr[…]
I guess I'm late, but I had the same problem and f[…]
Last night I received my first D1 Minis for a lear[…]
Although I am aware that this is an old post, I fe[…]