Configure VPN access for Devin to connect to your internal network
Devin operates in its own VM workspace and sometimes needs to access resources within your internal network (e.g., internal package registry, staging services, self-hosted services). Like your developers, Devin can use a client VPN to connect to your internal network.
Before setting up VPN access, verify the following:
Public Access Verification
Authentication Method: Using a service account to authenticate is recommended. Credentials can be securely stored via Devin’s Secrets functionality.
OpenVPN comes pre-installed in Devin’s workspace. To configure:
config.ovpn
configuration file to Devin’s workspace by dragging and dropping it into the VSCode instance/etc/systemd/system/openvpn.service
:Then reload systemd, enable and start the service.
This ensures the VPN connection is managed by the system and automatically restarts if it fails.
If your organization uses a different VPN solution:
For clients like Fortinet that can be installed via a package manager:
For clients like Palo Alto GlobalProtect that require a binary installation:
Upload the client binary and certificate to Devin’s workspace by dragging and dropping it into the VSCode instance
Install using: