#MQTT Broker + TCP Proxy

15 messages · Page 1 of 1 (latest)

snow crystal
#

Trying to get a docker container of a MQTT broker to run

I am running one on AWS and looking to move it to Railway. Do I understand correctly that if the container exposes 1883 or 8883:

Then I can use a TCP proxy <generated_domain>:<generated_port> -> 1883 || 8883.

Does not seem to be working for me

sleek skiffBOT
#

Project ID: 670ec5a8-83d2-45f3-abf6-4e43eed89b36

west anchorBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

snow crystal
snow crystal
#

Additional question, if I were to use a custom domain, cold i use reverse proxy also? or is it eaither or, in that case can i use nginx in the docker container to do the proxy there?

golden quartz
snow crystal
#

What is project in your context? if i only can expose i tcp port per project how am i running 1 project with 2 TimescaleDB containers both using tcp proxy,

If you mean per "service" or "container" then i follow.

I got the TCP proxy for the MQTT broker working, but it is now on one of the generated domain names, with a random port, is there any way to use a custom domain with TCP proxy of is it not interchangable?

golden quartz
#

im sorry, i misspoke, i did mean per service

#

there is no way to provide your own domain or port for the tcp proxy, but for an mqtt broker does it matter?

snow crystal
golden quartz
#

they are dynamic, please do not use an ip

snow crystal
#

the MQTT broker i am replacing is used to IoT devices scattered on various Offshore vessels, and most of these have no DNS service so are bound by refering to the brokers IP instead of DNS record.

golden quartz
#

railway isnt gonna be ideal for that usecase

snow crystal
#

aaalright thanks for clearing that up! saved me some frustration

golden quartz
#

no problem 🙂