Replies: 1 comment 7 replies
-
It's an obvious question, but what is different about this "one server"?
How are you running this docker container? On Windows, Linux, etc? I'm assuming it's on a different server than those hosting your client applications. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I wonder if you could give me a hand on solved this issue. First, our env:
RabbitMQ and Erlang version RabbitMQ 3.13.3 Erlang 26.2.5
Operating system for RabbitMQ and your client application. RabbitMQ: Docker Container with tag 3-management; Client: Windows Server 2016 fully patched.
RabbitMQ.Client library version 6.8.1
.NET version 4.7.02053 (.NET Framework)
Application runtime (Windows Server, IIS, etc): Windows Server 2016, IIS
FULL stack traces // Not exactly sure what you mean, but here's a portion of the log from .net app:
RabbitMQ Log;
_rabbitmq_logs.txt
Problem
We have set up RabbitMQ for Prod and Dev environments, as Docker containers. Our app works fine, and is able to connect to the service from everywhere but one server with same OS and client app. We went to the entire troubleshooting connectivity guide, and everything is fine. Ping is fine, telnet to 5672 is fine, even ncap works (you can see that in RabbitMQ log, attached, but is the only thing logged from the server). The only thing that doesn't work from that particular server, is connecting from our app to the RabbitMQ service ("None of the endpoints were reachable"). I believe this must be a combination of IIS config + Windows components, other than that there is no logical explanation I could find. The code is also working in a couple of servers / PCs, no issues there.
There is a similar issue from couple of years back, now closed.
Let me know if you need further details. Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions