Remote Access Tools

Based on Opensource is Awesome https://www.youtube.com/watch?v=DZ0Ocwga43w

Decided on Remotely - installed as nc.brusch.co.uk.

I had issues that links and installers did not work:

  • Instant desktop sharing failed to get session id,
  • Installer download, the installer fails with an error about empty ETag.

The root cause turned out to be that links were embedded as http (not https). Which broke things.

The fix was to tick Force Client HTTPS in Server Config

Issues on Upgrade

After upgrading the docker image of remotely the service would not even run; when I did get it working the original devices had all dissappeared.

  1. The fix is to move the docker environment settings into the docker compose file. i.e.
    environment:
      - ASPNETCORE_HTTP_PORTS=5000
      - ASPNETCORE_ENVIRONMENT=Production

I also had to share a volume as /root and update the docker-compose.yml file to include the network definition.

  1. On updating the image, docker will create a new container, which seems to get a new OrganizationID. This breaks everything. The fix is to update the OrganizationID inthe sqlite database before logging in.
docker exec -it remotely bash
apt update
apt install sqlite3
sqlite3 Remotely.db
$ update Organizations set OrganizationID="baxxxxxx";

Last outstanding question if why is sqlite3 dB and appsettings.json in /app, then the saved volume is /app/AppData??!

Fixed after re-configure.