a year ago
Good afternoon all, i'm working on EMQX mqtt broker but it seem unreachable from public network.
This service is listening on mqtt ports 1883 TCP connection, and 8883 for SSL connections of MQTT clients.
In case of TCP proxy selection i'm able to reach the broker succesfully for TCP, but seem to have ssl issues in case of 8883.
In case of standard pubblic domain selection (generated one i mean), i'm not able to reach nor 1883 or 8883.
Performing some tests seem i can reach from internal network this ports but not from public network.
Is there any procedure or recommandation to perform so?
I think MQTT is very popular protocol and providing a running one is a great feature.
Thanks a lot, Railway is a real grate product!
2 Replies
a year ago
To access a service publicly over HTTPS the service itself needs to listen on HTTP (not HTTPS) and host 0.0.0.0 (not just ::).
a year ago
What about MQTTS ? To can expose my broker over a custom domain name i have to configure a specific port listening on, and i can see right ports. But looks to be unreachable. The binding is both in variables and internal settings to 0.0.0.0:1883 and 0.0.0.0:8883. I can reach effortless Caddy but the MQTT Broker can be reached only in proxy setting.