[GH-ISSUE #2311] Nats error, what could it be? #3375

Closed
opened 2026-03-14 07:13:47 +03:00 by kerem · 0 comments
Owner

Originally created by @desenvolvimento-stateraTI on GitHub (Oct 10, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2311

This error is appearing in the logs, I only modified the identification information in this log. There are several lines with different IPs.

2025/10/10 13:38:26 [error] 2439194#2439194: *5035166 recv() failed (104: Connection reset by peer) while proxying upgraded connection, client: ip_client, server: api.domain.com.br, request: "GET /natsws HTTP/1.1", upstream: "http://127.0.0.1:9235/natsws", host: "api.domain.com.br:443" ........

My nginx is like this in natsws:

location ~ ^/natsws {
    proxy_pass http://127.0.0.1:9235;
    proxy_http_version 1.1;

    proxy_set_header Host $host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header X-Forwarded-Host $host:$server_port;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

What solution should I take or processes to follow?

Originally created by @desenvolvimento-stateraTI on GitHub (Oct 10, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2311 This error is appearing in the logs, I only modified the identification information in this log. There are several lines with different IPs. 2025/10/10 13:38:26 [error] 2439194#2439194: *5035166 recv() failed (104: Connection reset by peer) while proxying upgraded connection, client: ip_client, server: api.domain.com.br, request: "GET /natsws HTTP/1.1", upstream: "http://127.0.0.1:9235/natsws", host: "api.domain.com.br:443" ........ My nginx is like this in natsws: location ~ ^/natsws { proxy_pass http://127.0.0.1:9235; proxy_http_version 1.1; proxy_set_header Host $host; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Forwarded-Host $host:$server_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } What solution should I take or processes to follow?
kerem closed this issue 2026-03-14 07:13:53 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#3375
No description provided.