-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstream connection issue #3
Comments
Error from rabbitmq log 2022-02-18 17:36:46.329907+00:00 [info] <0.31586.0> accepting AMQP connection <0.31586.0> (127.0.0.1:43634 -> 127.0.0.1:5672) |
That's 0.2ms between the connection and the timeout. Have you configred the handshake timeout manually? Because the default is more like 10 seconds. |
No I am using default setup Also when I test message submission directly to rabbitmq it is working fine. |
Which client library/version were you connecting with? |
I am facing the same issue 2024-03-12T17:14:50.914146378Z 152.58.208.213:0 disconnected: #<IO::Error:Closed stream> and with this we noticed there's been increase in the memory usage with time. Created an issue for this : #16 |
Hi Team,
I am getting following error in default setup
websocket-tcp-relay[31604]: 3.7.237.29:56904 connected
3.7.237.29:56904 connected to upstream
3.7.237.29:56904 disconnected: #<IO::Error:Error reading socket: Connection reset by peer>
[main]
upstream = tcp://127.0.0.1:5672
bind = 0.0.0.0
port = 443
proxy-protocol = false
webroot = /var/www/html
tls-cert = /etc/letsencrypt/live/polkadex.trade/fullchain.pem
tls-key = /etc/letsencrypt/live/polkadex.trade/privkey.pem
The text was updated successfully, but these errors were encountered: