Configure persistant .onion address for remote SSH over Tor

Hello, I have setup a remote StartOS server that I am responsible to manage. I had followed the guide for SSH over Tor and had it working initially, including connecting from my Windows machine using Putty via Tor’s Socks 5 proxy. However I’ve since run into the issue stated on the guide page, that “after each server reboot, a new .onion address will be generated, rendering the old one inactive.” Is there a way to configure the SSH .onion address to persist after reboot?

Unfortunately not. Until you’re able to avoid this step entirely with StartOS v040, if you need remote SSH access badly, I’d set up a wireguard tunnel to somewhere on the LAN with the server, then SSH locally from that.

1 Like

Thank you for the reply. I will say the StartOS platform has generally been a joy to work with compared to some of my other adventures on Linux-based systems with advanced-beginner skills.

Is there a container I can install that would work as a Wireguard endpoint, or do you mean placing a separate physical device on the network? The family member to whom this node belongs uses a stock “ISP” modem/router so there’s no VPN functionality exposed to the end user aside from basic port forwarding and static IPs.

On a related note, is there an estimate of when v0.4.0 will be released? Thanks again.

No one has created a Wireguard service for v0.3.5.1 - I assume because of the way the vlan works making it somewhat tricky, or just because of the proximity of v0.4.0, which is almost in public beta, so soon.

1 Like