Linux VPS Operations

Proton VPN Server Guide

Current setup notes and safe commands for the Proton VPN staging work across vps1, vps2, and vps3.

vps3 staged not live vps1/vps2 need SSH recheck

What Is Done

  • Proton Linux release package was staged on all three VPSes.
  • The staged package SHA-256 was verified when downloaded.
  • Proton manual OpenVPN/IKEv2 username was captured.
  • vps3 has OpenVPN installed and Proton configs present.

What Is Not Live

  • No Proton tunnel was started by Codex.
  • No Proton tunnel is enabled on boot.
  • WireGuard configs were not generated yet.
  • vps1 and vps2 timed out during later SSH verification.

vps3 Start / Stop

Use this only when you intentionally want vps3 to route through Proton. Keep a second SSH session open the first time.

Connect sudo systemctl start openvpn-client@proton-us
Check status sudo systemctl status openvpn-client@proton-us --no-pager
Check public IP curl ifconfig.me
Stop sudo systemctl stop openvpn-client@proton-us

Config Locations

  • /etc/openvpn/client/proton-us.conf
  • /etc/openvpn/proton/us-free-1.ovpn
  • /etc/openvpn/proton/us-free-tcp443.ovpn
  • /etc/openvpn/proton/us-tcp443.ovpn
  • /etc/openvpn/proton/us-udp.ovpn

Staged Packages

  • vps1: /home/mike/downloads/protonvpn/
  • vps2: /home/mike/downloads/protonvpn/
  • vps3: /root/downloads/protonvpn/

Recommended Next Steps

  1. Restore or confirm SSH access to vps1 and vps2.
  2. Verify package/config state on those two servers before doing anything live.
  3. Use WireGuard long term after generating one Proton config per server.
  4. Only enable boot startup after manual activation is confirmed stable.