Github Actions have updated network interfaces. Ping timeout. VPN

Question

Posting this as a heads-up, the issue is resolved

One of our long-running GitHub Actions has always done the following:

Connect to our VPN with OpenVPN.

Ping a private IP inside that network as a quick health check.

We hadn’t touched the workflow in months, yet yesterday the ping step started failing. To troubleshoot, we added a debugging step:

- name: Show routes for debugging
  run: |
    ip addr show
    echo '--------------------'
    ip route show table main

The output showed that the runner now sits on the same subnet as our VPN—10.1.0.0/20. Because of that overlap, packets meant for the VPN IP were being routed locally inside the container instead of through the tunnel.

Mike · Accepted Answer · 2025-07-04 10:37:12Z

0

We reassigned the VPN host to an address outside that range, and the workflow is green again.

answered Jul 4 at 10:37

Mike

4474 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Github Actions have updated network interfaces. Ping timeout. VPN

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related