How to access webservice on same VPN server?
Posted: Wed Sep 09, 2020 11:08 pm
How do I visit, through OpenVPN, a remote SVN server as if were visiting a local one?
Target system: VPS with Ubuntu 20.x LTS, 3.2G Single core CPU, 4G Ram, 100G SSD + 400G Mechanical HDD
What I want to accomplish:
Log on to a remote SVN server with Subversion GUI Client using OpenVPN by configuring the address to a LAN address, or better yet, 127.0.0.1. E.g. http://127.0.0.1/myRepo. I want to have all the traffic to never leave my remote VPS host once it arrived at it.
What I have accomplished:
Successful OpenVPN service deployment, established server-client configuration, encryption appears to be working properly based on wireshark sniffing.
Successful Apache2 Subversion service deployment.
Why do I want to do what I want to do:
Security. Which has 2 layers of meaning: a. All the traffic is now UDP & encrypted. b. By being able to replace the remote IP address with a LAN/local one I can effectively rule out the possibility of uploading my code unencrypted to the remote VPS, forgetting that my VPN isn't connected.
My VPS provider blocks http & https traffic. But it made it clear that it does not interfere with any other traffic, even cloaked http traffic. Since to use SVN I need to go http eventually at some point I need to limit the traffic, once it reaches the VPS, to within the VPS.
The crux of the problem
The missing piece here is I don't know what to do since I've finished delopying both VPN and SVN service. I was expecting naively and groundlessly that once I connected I could replace the remote IP address in the SVN Client with 127.0.0.1 or 10.8.0.5 something like that, but clearly it's not that simple.
Please help! Thanks in advance!
Target system: VPS with Ubuntu 20.x LTS, 3.2G Single core CPU, 4G Ram, 100G SSD + 400G Mechanical HDD
What I want to accomplish:
Log on to a remote SVN server with Subversion GUI Client using OpenVPN by configuring the address to a LAN address, or better yet, 127.0.0.1. E.g. http://127.0.0.1/myRepo. I want to have all the traffic to never leave my remote VPS host once it arrived at it.
What I have accomplished:
Successful OpenVPN service deployment, established server-client configuration, encryption appears to be working properly based on wireshark sniffing.
Successful Apache2 Subversion service deployment.
Why do I want to do what I want to do:
Security. Which has 2 layers of meaning: a. All the traffic is now UDP & encrypted. b. By being able to replace the remote IP address with a LAN/local one I can effectively rule out the possibility of uploading my code unencrypted to the remote VPS, forgetting that my VPN isn't connected.
My VPS provider blocks http & https traffic. But it made it clear that it does not interfere with any other traffic, even cloaked http traffic. Since to use SVN I need to go http eventually at some point I need to limit the traffic, once it reaches the VPS, to within the VPS.
The crux of the problem
The missing piece here is I don't know what to do since I've finished delopying both VPN and SVN service. I was expecting naively and groundlessly that once I connected I could replace the remote IP address in the SVN Client with 127.0.0.1 or 10.8.0.5 something like that, but clearly it's not that simple.
Please help! Thanks in advance!