Can I use a VPN to "give" my home-based, dedicated server my Digital Ocean IP?

Is it possible to connect my physical, dedicated server to a Digital Ocean Droplet over VPN so that I can be “running” on a clean IP? I have a fast Comcast residential line, which causes problems with outbound, transactional emails when I try to run a dedicated web server. I switched to Bluehost a year ago, but I am sick of them and can’t afford to pay more than the $30 / mo. I am already paying. I run about a dozen, low-traffic WordPress websites and REALLY like the speed that a dedicated server affords.

This morning I successfully set up a Dropbox running Ubuntu 12 64-bit and quickly installed OpenVPN, which I was able to tunnel into from my main Windows machine, so I know at least that much works. I just don’t know where to go from here…

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

You could let your home server dial-in as a HTTP(S) client, and include a Authentication token in a HTTP(S) reguest header (Auth token: Think fx. JWT with AES encryption), so the the server knows that it is your home server that is knocking on the door; maybe also use IP address range filtering. If you main reverse proxy server at Digitalocean needs to do some expensive processing it could ask your home server to do the heavy lifting, and send the response back. This of cource requires that you have good upload and download bitrate, fx 60Mbit/s / 60 Mbit/s.

You could fx. use first Varnish and after that nginx for static files like HTML, js, css, and pictures. Nginx should be configured as a reverse proxy server for dynamic content, which goes to the home server. If the connection to the home server goes down for some reason, nginx should respond with a 500 Internal Server Error, and in your server logs something like “Backend server connection is down.” should be added together with date and time.

JWT (JSON Web Tokens): ,