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
Enhance proxy handling and add IP name caching (#44)
* Enhance proxy handling and add IP name caching
- Added support for proxy name usage in connection requests to work around strict proxies.
- Enhanced test coverage for proxy functionality and integration tests.
* Remove output comments from example CA tests
@@ -44,18 +44,18 @@ means: *all ports from 1024 to 2048, inclusive*.
44
44
Notes:
45
45
46
46
1.`<agent-ip>` is the internal IP of the machine on your network where Probely's Farcaster Agent is running. The agent uses it to communicate with the Probely server.
47
-
2.`<target-ip>` is the internal IP of your web application.
47
+
2.`<target-ip>` is the internal IP of your web application.
48
48
If your target is configured to use internal extra-hosts, include their IPs here.
49
49
The same goes for the target login URL if a different internal web application serves it.
50
50
3.`<target-port>` is the service port of the server of your web application.
51
51
Typical values are 80 and 443.
52
-
4. The IP addresses of these hosts are subject to change. We recommend allowing
52
+
4. The IP addresses of these hosts are subject to change. We recommend allowing
53
53
web access for the agent VM (HTTP and HTTPS ports). If this is not possible, the agent
54
54
will use an HTTP proxy if you set the `HTTP_PROXY` variable.
55
55
5. At this time, the hosts are: `registry.docker.io` and `registry-1.docker.io`
56
56
6. This server receives connections from potentially vulnerable systems on your infrastructure.
57
57
It is used, for example, to detect "Log4Shell"-type vulnerabilities.
58
-
58
+
59
59
# Installation
60
60
61
61
The agent runs on a Docker container. It should work on any system with a Docker installation.
@@ -117,32 +117,32 @@ Probely's support team.
117
117
Connecting to Probely (via UDP) ... done
118
118
Setting local gateway rules ... done
119
119
Starting WireGuard gateway ... done
120
-
120
+
121
121
Running...
122
122
```
123
123
124
-
Once up and running, the Agent in the Docker container knows the URL or IP of the target to scan from the target configuration in Probely. The Agent communicates with Probely to get this information before starting a scan.
124
+
Once up and running, the Agent in the Docker container knows the URL or IP of the target to scan from the target configuration in Probely. The Agent communicates with Probely to get this information before starting a scan.
125
125
Learn more about [how to scan internal applications with a Scanning Agent](https://help.probely.com/en/articles/4615595-how-to-scan-internal-applications-with-a-scanning-agent).
126
126
127
127
### Connection issues
128
128
If the Agent is not connecting to Probely, please ensure that your [firewall](#network-requirements) is properly configured.
129
-
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.
129
+
130
+
Alternatively, the agent can use a proxy to connect to Probely using standard environment variables. The agent honors `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY`for outbound connections. HTTPS proxies are supported. `ALL_PROXY` is honored for WebSocket connections (ws://, wss://) via the standard library HTTP transport, but not for raw TCP connections.
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
133
### Unsuccessful UDP connection issues
134
-
If the Agent is not connecting through UDP, and you are getting the log:
135
-
134
+
If the Agent is not connecting through UDP, and you are getting the log:
135
+
136
136
```
137
137
...
138
138
Connecting to Probely (via UDP) ... unsuccessful
139
139
Configuring fallback TCP tunnel ... done
140
140
Connecting to Probely (via TCP) ... done
141
141
...
142
142
```
143
-
144
-
It's because the UDP connection is being blocked.
145
-
143
+
144
+
It's because the UDP connection is being blocked.
145
+
146
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