Report this

What is the reason for this report?

Accessing Droplets in VPC via Private Network After Connecting to Outline VPN

Posted on January 16, 2022

I used the digital ocean guide to setup an Outline VPN droplet and I’m able to connect to it with my external IP correctly showing the droplets IP once connected.

However I’d like to be able to, but can’t connect to any of my other droplets in the same VPC via there private network IPS.

Curious if there’s additional configuration I need to do to accomplish this?

I am able to access the droplets via there external IPs.

I’d prefer though to use their private ips so as to not have the network traffic between the droplets and VPN droplet count against our quota.

Any help would be appreciated.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Base on my experience. If you are setting OpenVPN and you would like to access other droplet resources in the same vpc, you must configure the following in /etc/ufw/before.rules

# START OPENVPN RULES
# NAT table rules
*nat
:POSTROUTING ACCEPT [0:0]
# Allow traffic from OpenVPN client to eth0 (change to the interface you discovered!)
-A POSTROUTING -s 10.8.0.0/8 -o <eth0 OR eth1> -j MASQUERADE
COMMIT
# END OPENVPN RULES

Had the same issue when I followed digital ocean’s instruction. I had to change eth0 to eth1 then I was able ping and ssh to other droplets in the same vpc network.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.