a year ago
I'm trying to deploy rabbitMQ which has both a TCP port an a HTTP port but you cannot expose both publicly.
The example comes with a proxy but that's not working, can anyone help?
0 Replies
a year ago
at this time you can't expose a single service via tcp and https
a year ago
i will look into why the template doesnt work
a year ago
the project has no services?
a year ago
can you deploy a fresh rabbitmq template so i can look for the issue?
I'm testing around with this project as I don't want to mess with my main project
e269f5dd-f1fb-40f1-9ea5-9b0a20b1c53a
a year ago
in the test env?
a year ago
do i have your permission to also test in this env?
I just want to be able to access both the TCP port (5672) and the HTTP management port (15672) as I need to access the API as well
a year ago
looks like it works now
a year ago
check the activity panel to see what i changed
a year ago
its namespace was wrong
Now, I don't want to sound stupid but I think I've replicated this exactly in my dev environment and it's not working still…
a year ago
looking
a year ago
okay so thats a bit different since this was not deployed from a template
a year ago
do you have a rabbitmq conf file in that monorepo?
Yeah this is my custom version of rabbitMQ with a plugin added on top. Here is my dockerfile
FROM rabbitmq:3-management-alpine as rabbitmq
COPY plugins plugins
RUN rabbitmq-plugins enable rabbitmq_message_deduplication
a year ago
thats all there is to the dockerfile in the rabbitmq folder?
There is a plugins folder also in that rabbitmq folder which has a message deduplication plugin in and it copies it accross
a year ago
do you know what the difference is between 3-management-alpine
and just management-alpine
are?
a year ago
nvm the hash says they are the same
It just specifies the latest version 3 of rabbitMQ since a new v4 is in the RC stage so is coming out soon.
I just spotted the same start command difference as well <:Fingers:1202140286956867644>
a year ago
yeah its working now, so ill explain
a year ago
/bin/sh -c "echo management.tcp.ip = :: >> /etc/rabbitmq/conf.d/10-defaults.conf && docker-entrypoint.sh rabbitmq-server"
this start command dynamically modifies the rabbitmq conf file to have the management interface listen on ipv6, instead of the default ipv4 interface.
this is needed since the private network is ipv6 only.
a year ago
no problem, let me know if you have any more questions!
a year ago
no problem!
I wanted to put a rabbitmq on my railway, but it's not appearing when I click on new, what do I do?
8 months ago
please open your own thread