A little more background on this:
When you download the instant support client, it adds your organization's relay code to the file name. This relay code can be found on the Organization tab, and it can be used by to query the web API to get branding info.
However, since these are "generic" versions that I've compiled in advance on my build server, they have no way of knowing what server it should contact to get the branding info.
For the scripts, I'm able to inject the server URL right when they're downloaded. I can get the server URL based on the download request, and replacing text in the file is easy. But I can't do that with an EXE. They would need to be recompiled.
I've thought about hosting this as a service, where I'd recompile clients on demand like TeamViewer does. But it would get costly. And I'd need both Windows and Mac servers. And it kind of defeats the purpose of self-hosting.
So if you're fine with using systemd and .NET on the host machine instead of Docker, you can follow this tutorial to have GitHub Actions build a customized server: https://remotely.one/Tutorials
Same issue I am getting. Trying to contact them from their website (https://remotely.one/Contact) and getting an error. Not sure how else to get ahold of someone as I haven’t been able to login for a few days now.
Hi, just do the same steps as you did while install remotely fort the first time. Exactly same steps. Include GitHub repo fork steps and command, you have to create new personal access token in github.
Database and configure file of Remotely stay untouched after installation :)
Readme on GitHub: https://github.com/lucent-sea/Remotely#installation-instructions
Video tutorial: https://remotely.one/tutorials
Agreed, the generic name has made it hard to find info and guides online. I tried searching on YouTube using the project website URL remotely.one and remotely_app and found a video but it's difficult to separate the wheat from the chaff with the name fitting the way many people are now working 'remotely' from home. I like the name, it's just a shame it makes searching online so difficult.
Found the issue guys. It appears that the OS does not see a physical screen attached, thus disables the "console" screen from showing. RDP works fine. One of the workarounds is purchasing an EDID adapter: