You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+46Lines changed: 46 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,6 +130,52 @@ Probely's support team.
130
130
Alternatively, the agent can use an HTTP proxy to connect to Probely if the `HTTP_PROXY` environment variable is set on the `docker-compose.yml` file.
131
131
While the agent can use an HTTP proxy or a direct TCP connection to Probely, this can cause poor network performance. For more information, see this article about the [TCP Meltdown](https://web.archive.org/web/20220103191127/http://sites.inka.de/bigred/devel/tcp-tcp.html) problem. We **strongly recommend** that you allow the agent to connect to `54.247.135.113`, `44.212.186.140`, and `54.253.10.194` on `UDP` port `443`.
132
132
133
+
### Unsuccessful UDP connection issues
134
+
If the Agent is not connecting through UDP, and you are getting the log:
135
+
136
+
```
137
+
...
138
+
Connecting to Probely (via UDP) ... unsuccessful
139
+
Configuring fallback TCP tunnel ... done
140
+
Connecting to Probely (via TCP) ... done
141
+
...
142
+
```
143
+
144
+
It's because the UDP connection is being blocked.
145
+
146
+
To confirm if nothing is blocking the UDP connections, you can set up a UDP server using the following script **outside your network** to "echo" the received messages:
0 commit comments