If the values are not appearing as expected, it is because the headers were missing, didn't contain the correct values, were not the correct format, or didn't come through a chain of known proxies (see below). It is done internally by ASP.NET Core's built-in middleware. The Remotely code does not parse or handle these values. The client IP address is used in the device info. The resulting scheme and host are injected into the installers and desktop clients, so they know where to send requests. These correlate to the scheme (http/https), the URL of the original request, and the client's IP address, respectively. With that said, Remotely requires the following headers to be set: X-Forwarded-Proto, X-Forwarded-Host, and X-Forwarded-For. The Remotely maintainers simply can't provide guidance and support for all the possible environment setups. If you are having networking issues with any other setup, such as with an additional firewall or with Nginx, please seek out community support in the Discussions tab, on Reddit, or another social site. The default configuration for Caddy provides everything that ASP.NET Core and SignalR need to function correctly.

The only supported reverse proxy is Caddy, and only when it is directly facing the internet. Project Linksĭocker run -d -name remotely -restart unless-stopped -p 5000:5000 -v /var/www/remotely:/remotely-data immybot/remotely:latest When we resume this initiate later this year, you will likely abstraction of the Remotely.Desktop code into a shared library that can be consumed by Remotely as well as other agents like ImmyBot.

We want to keep Remotely fully operable as a standalone project.

We did a big push earlier this year to build an integration between Remotely and ImmyBot but ran into some technical challenges trying to keep only one agent on machines, but we don't want to cannibalize Remotely for the gain of ImmyBot. ImmyBot experienced explosive growth this year and we only have 4 developers which is why there hasn't been much activity here. Jared and I had similar goals and he felt that we would be good custodians of the project. While Jared was writing Remotely, we were writing our own tool for MSPs called ImmyBot, primarily focused on automation and software deployment. I (Darren Kattan) had followed this project since the moment Jared shared it on r/msp years ago. We intend to keep Remotely fully open-source. Immense Networks is the proud new owner of Remotely. A remote control and remote scripting solution, built with.

Remote control ubuntu desktop windows