That’s right.
Also try WAN.
No it didn’t work
Did you also try https?
Yes I did and it does not work either
Do I need to put a port number after the external IP
Use an online port checker to see which ports you have open.
I don’t think you need one because https defaults to 443 and you have the iptable set to forward to 9443.
Try just http too.
Yeah okay which port numbers should I check
80, 443, 8080, 9443, 8441, 8442 and 8443.
So 443 Is not open
Just 443 Is not open out of all of the above ports
I’m pretty sure that the API calls, which ultimately what IFTTT does, uses just http not https so 443 will not be needed.
It will be required if you want remote admin access though.
Should I put forward 443 in my Rueter
See my last post,
Please confirm the LAN API call that worked just used http not https.
Works with http
Https Takes me to your connection is not private webpage and does not light the button in the blynk app
Sorry a further update to my previous message when I click advanced and continue it lights the button up in the app
OK so you can use http or https. Unless you have a domain to tie a WAN IP to then you will always get the warning stuff because Let’s Encrypt doesn’t provide certs for IP addresses.
If you have the required ports open and the WAN API call doesn’t work then its:
- Some Firewall issue
- Some port block issue by your ISP
- You didn’t port forward correctly
That’s why the docs state local servers are for the “pros”.
Well I think we can count out option three because I did the port checker and everything came back okay except for 443
Just thinking out loud considering I was using my Naz box on port 8080 without any issue I think it’s safe to say that there is no firewall issue regarding that port