Skip to main content
VPN profiles require the Internal network scanning add-on.

Common issues

Applies to VPN Agent (VM, Docker, Cloud) only.
  • Verify outbound internet access from the agent
  • Check firewall rules allow TCP port 22 to vpn2.pentest-tools.com
  • Confirm the VPN UUID is correct
  • Restart the agent
  • Run a connection test and check the connection logs
  • Verify the agent can reach the target (ping or telnet from the agent)
  • Check internal firewall rules between the agent and the target
  • Verify routing is configured correctly
  • Confirm the target is responding on the expected ports
  • Check network stability on the agent’s host
  • Verify the agent has sufficient CPU and memory
  • Review agent logs for errors
  • Check for IP or port conflicts
  • Check network latency between the agent and targets
  • Verify agent resource utilization (CPU, memory)
  • Consider placing the agent closer to the targets
  • Check for bandwidth limitations

Connection logs

Both VPN Agent and Custom OpenVPN profiles provide connection logs for diagnosing issues. To view them:
  1. Go to Settings > VPN Profiles
  2. Click on the profile name to open the details panel
  3. Scroll to Connection logs
If the logs are empty, click Test connection to generate them.

Connection test statuses

StatusMeaning
SuccessConnection established
RefusedFirewall blocking or wrong server address
TimeoutNetwork unreachable or DNS issues
Auth FailedWrong username or password
TLS ErrorMismatched certificates or outdated TLS
Options ErrorIncompatible options in config file
UnsupportedUnsupported VPN features in config

Checking agent status

# Check container status
docker ps -a | grep pentest-agent

# View logs
docker logs pentest-agent --tail 100

Restarting the agent

docker restart pentest-agent

Contacting support

If you can’t resolve the issue, collect this information before contacting support:
  1. Connection logs from the VPN profile details panel
  2. Agent logs (Docker: docker logs pentest-agent, VM: cat /root/entrypoint.log)
  3. Agent deployment type (Docker, VM, or Cloud)
  4. Steps you’ve already tried