You must have a weird ISP. Port forwarding is usually done on one's own home router, not by the ISP. Though it's possible they use NAT for your outgoing IP and as such it's in a private space so forwarding is impossible for the end user or they lock down the router and don't allow you to add your own (unlikely).
In any case, MQTT is NOT for allowing public access! Never do that without proper authentication and encryption. It's for internal communication on your own LAN for IOT, weather devices, etc. BTW, accessing JSON on your own server at home when you're outside of your LAN also requires port forwarding. That can be properly secured but I guess it's equally impossible for you then because of ISP restrictions. But let's not deter the thread with that - in a new thread or privately I can help, though. On Friday, March 29, 2019 at 10:43:31 AM UTC+1, [email protected] wrote: > > Thanks kobuki for this info. > I started with mqtt a while ago until I discovered that some ports must be > forwarded to your application. > Our ISP will do that for us... for a monthly fee. No thanks! > Luc
