Report Bugs Here

Moderator: Mmiscool

User avatar
By Oldbod
#56356 I'm not at all sure about this, and esp8266basic is continuously evolving anyway, but I think the websockets connection was hardcoded to port 81.

If you can make it work on ports 80 and 81, then that localises the problem to the port handling.

Or put some serialprints in to show how far it gets...
User avatar
By rodrigocirilo
#56358 Yes, I agree that the esp8266basic is evolving !!

The problem is that these ports 80 and 81 here in my country are blocked by internet service provider, and it's very complicated to ask release them. So it could be other doors would be better.

I got the unlock here to test, and it worked, but not doors that I want to release ever.
User avatar
By rodrigocirilo
#56438
Mmiscool wrote:You need to port forward port 80 qnd 81 on your router in order to access the web interface from an external ip address. You can then send from your external ip address.


Please help me.

As I said, here in my country the ports 80 and 81 are permanently locked and releases them you need to contact your internet provider and it is very difficult to release them. For IoT applications would be very difficult to use.

It would be possible to change the configuration of espbasic (interpreter) to use other ports other than 80 and 81, and it was possible to change them.