Remotely VS frp

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

If you want to self-host, there are many options. For something production ready frp is probably what you want. If you're a developer, I'd recommend starting with my own SirTunnel project and modifying it for your needs. For non-developers and those wanting more of a GUI experience, I created boringproxy. It's my take on a comprehensive tunnel proxy solution. It's in beta but currently solves almost everything I want. Once the server is running this is a very easy tool to use and has some nice features.

Seems to be the exact opposite of https://github.com/fatedier/frp which is a reverse tunnel over a variety of protocols (including HTTP).

I've been self-hosting https://github.com/fatedier/frp on my little box, and it feels insane to think of the times where I didn't have it set up. There are many choices in the space as others pointed out, but frp's capabilities and lightweight packaging blows all other setups out of the water. I placed mine behind nginx with Let's Encrypt for SSL support. Hella fresh!

My setup to do the same:

- small Hetzner instance

- my domain's dns pointing to that instance

- frps[1] running on that instance

- frpc running on my local machine and connected to the cloud frps

[1] https://github.com/fatedier/frp

An easy service to use is FRP, recently found it and it basically handles making the connection out of the network and is really easy to setup. https://github.com/fatedier/frp I personally having it running on a VPS and the client then running on my local network pointing at a reverse proxy which then handles sending it to the diffrent clients.

No, FRP - https://github.com/fatedier/frp

Another way around is to use reverse proxy like frp but since you need SSH anyway, all you need is already comes with SSH (reverse SSH)

Take a look also onto popular, similar to yours project: frp