Remotely VS rathole

Following the comments in this thread, I should see an input for Server URL when building the client application with GitHub actions, however it's not there. Yes I forked the official GitHub repo.

Are you sure? It seems to be thriving under new management.

Site to site VPN if you have access to your locations' firewalls, otherwise some raspberry pis and https://github.com/immense/Remotely or any RMM.

I have another suggestion, have a look at Remotely. I only just looked into this and spun up a container to play around with. It's very similar to TeamViewer in that:

The closets open source alternative to Tactical RMM, I would say it's Immense Networks Remotely. It offers unattended remote access, as well as quicksupport feature like Teamviewer. It also has limited support for running scripts on one or many hosts which in effect allows doing some functions like that of Tactical RMM, however it doesn't give your same detailed device inventory as Tactical RMM, it doesn't monitor performance and you can't setup alarms as you can in TRMM. https://github.com/immense/Remotely

if you feel comfortable self hosting: https://github.com/immense/Remotely

Edit: For anyone who wants to follow: https://github.com/immense/Remotely/issues/553

rathole - Similar to frp, including the config format, but with improved performance. Low resource consumption. Hot reload. Written in Rust.

rathole?

There is also this: https://github.com/rapiz1/rathole

I always struggle with the iptables rules that are needed for that. I recently stumbled on Rathole, which seems to take care of that for this specific usecase, but haven't tried yet. https://github.com/rapiz1/rathole

Rathole is also a simple lightweight solution if you're open to alternatives to haproxy.

Very minimalist, but rathole would work if you have a public facing VPS as well => https://github.com/rapiz1/rathole