yes, it is in a same network, but only for testing, when i finish i move my board in different location, and my local server is a same place and i now.
port 8080 it`s open, and i have two router and i forwarded correctly i guess.! image|690x468
My DNS is up to date, but it receives my IP from the ISP router, but I will change the DNS from the ISP and it will automatically take my external ip, now I put my external ip in DDNS alone , but the blynk application automatically connects via DDNS (X.ddns.net) and works, but ESP32 does not work when I connect to DDNS
Having the port open, and having it correctly forwarded to your local server are two very different things. I’d suggest that you share some screenshots of your port forwarding setup.
In that case your port forwarding for port 9443 is correct.
Not quite sure what you’re saying here, you need to explain your current setup in more detail.
so my setup is like this: The provider router is connected to the router I bought, and the local server (blynk) is connected via WIFI to the router I bought
Your last image doesn’t show anything for port 8080
I use a similar setup to you, with a Huawei router provided by my ISP and a Netgear router which handles my internal traffic. I use this to get around my ISP locking down some of the features in their router, such as DNS settings.
I do things differently though. ALL data on all ports is forwarded from the ISP router to my own, and my port-forwarding is done in my own router.
Do you mean that the last picture is not visible? or is it visible but I didn’t do the right thing with port 8080?
And in the end, what can I do to make ESP-32 work with DDNS? Did I write something in the wrong code? or why it doesn’t connect when I try to connect with DDNS.
When I try to connect to the local server ip, it goes and tells me this:
I solved the problem, it was from port forwarding and for ESP 32 I used port 9443 and it worked, but the application didn’t work, but I put port 8080 for blynk app and it worked, now they both go through DDNS
I’m still not sure you have it right, but it works in a roundabout way.
In your own router you should be forwarding:
WAN 9443 to LAN 9443
WAN 8080 to LAN 8080
Yes, that’s correct. But your other router screenshots seem to switch traffic from 8080 to 9443 and vice versa.
You want an incoming packet on port 8080 to travel through your first (ISP) router into your second router then on to your local server - still on port 8080.
That’s not happening, it’s being changed to port 9443 as far as I can tell from your screenshots.
The same applies to port 9443.
Outgoing traffic doesn’t need any re-direction. It knows where it’s destination is, it just needs to be able to access the Internet unchanged.