Skip to content

Releases: immense/Remotely

v2023.04.17.1215 Release

17 Apr 22:41
Compare
Choose a tag to compare

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

  • b1cc1d1 Merge pull request #619 from immense/jaredg-617-fix-linux-desktop-client
  • 5add343 Update submodule.
  • 4cba297 Fix unattended session in Linux.
  • 903eafc Update submodule.
  • 8893f19 Don't use app manifest when running in debug.
  • d2dd852 Fix desktop reconnection. Fix crash in Wayland (though still not supported).
  • e97eda0 Update submodule.
  • 16477e7 Register missing IMessageBoxViewModel in DI, organize MessageBox-related classes, add FakeMessageBoxViewModel, fix resolution of current Application in AvaloniaDispatcher, and remove unused dependency on libdgiplus.

This list of changes was auto generated.

v2023.02.14.2047 Release

15 Feb 14:38
Compare
Choose a tag to compare

This release enables account lockout by default for new accounts. Accounts will be locked out for 5 minutes after 5 failed attempts (Identity framework's defaults).

Existing accounts will need to be manually updated in the database by changing LockoutEnabled to true on the RemotelyUsers table.

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

  • 57e3d52 Enable lockout when user is created from the registration page.
  • 564668f Enable lockout on new accounts created on the organization page.
  • 0e62543 Enable account lockout.

This list of changes was auto generated.

v2023.02.01.2115 Release

03 Feb 01:12
Compare
Choose a tag to compare

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

  • cef26f5 Add form label color in darkly theme for Identity input labels.
  • d5bb45a Restrict standard users from accessing device groups that don't have any users.
  • eff1b63 Add "ForceClientHttps" application option.

This list of changes was auto generated.

v2023.01.20.0732 Release

20 Jan 16:33
97e31b4
Compare
Choose a tag to compare

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

  • 97e31b4 Fix NRE in ViewerPageDataProvider. (#571)
  • c5a1a56 Move HTTP logging above forwarded headers, so the unmodified headers are logged. (#566)

This list of changes was auto generated.

v2023.01.18.0228 Release

18 Jan 03:39
fbb83e3
Compare
Choose a tag to compare

This release moves HTTP logging before processing of forwarded headers in the pipeline. This means that requests will be logged before their headers are altered by the forwarded headers middleware.

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

This list of changes was auto generated.

v2023.01.14.1558 Release

15 Jan 00:56
11a99c6
Compare
Choose a tag to compare

This release adds the UseHttpLogging in appsettings.json and the Server Config page. This will enable ASP.NET Core's built-in HTTP logging middleware, which will log all requests and responses. In addition, it will add some log entries during client downloads that show the effective scheme, host, and remote IP (as resulted from processing forwarded headers).

The app will need to be restarted after changing this, as it's only read once during startup.

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

This list of changes was auto generated.

v2023.01.06.1648 Release

07 Jan 01:34
56ee561
Compare
Choose a tag to compare

Important Notes: With this release, the server no longer relies on the RedirectToHttps setting to determine whether to use "http" or "https" when embedding the server URL into the downloaded clients and installers.

The scheme (http/https) is now being correctly identified from forwarded headers received from the reverse proxy. By default, forwarded headers will be accepted from loopback addresses (e.g. localhost or 127.0.0.1), or from the default Docker host IP (172.17.0.1).

If you're using a non-default Docker configuration, or you're hosting bare-metal with a reverse proxy on a different machine, you will need to add the IP address to the KnownProxies array in appsettings.json.

The RedirectToHttps property will now only be used as originally intended, which redirect http requests that the dotnet process receives (not the reverse proxy) to https. In most scenarios, this isn't needed, because the reverse proxy is accepting connections over https and forwarding them to the dotnet service over http.

Changes:

  • Added Docker default host IP (172.17.0.1) to known proxies so it will accept all forwarded headers.
  • Fixed AudioCapturerWin so NAudio exceptions wouldn't cause Remotely to crash.
  • Set permissions on log file so non-elevated process can write to it.
  • Replaced some static Logger calls with ILogger.

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

  • 56ee561 Bug - Proto forwarded header not being seen by ASP.NET Core. (#554)

This list of changes was auto generated.

v2023.01.04.0634 Release

04 Jan 21:56
Compare
Choose a tag to compare

This release fixes a regression bug in the agent reconnection code. I refactored it to use the "correct" method of reconnection, which is by implementing IRetryPolicy. I forgot to send device details back up to the server on reconnect, though. So reconnected devices would appear offline until the next heartbeat.

Docker Image

See Docker Hub for instructions on pulling and running the image.

Changes:

  • 9cc964f Update Release Build.yml for Azure Pipelines
  • 95b9a45 Fix regression bug related to agent reconnection. (#552)
  • 553c512 Update README.md

This list of changes was auto generated.

v2023.01.02.1403 Release

02 Jan 22:34
080aed5
Compare
Choose a tag to compare

Changes:

  • Add EffectiveScheme in client downloads controller
    • When hosted in Docker behind a reverse proxy, the forwarded headers feature doesn't appear to be working for scheme (i.e. http/https). So Remotely will only see the URL of the request as HTTP, even if HTTPS is being used.
    • Set RedirectToHttps to true in appsettings.json to force it to use HTTPS.
  • Check for empty ETag result before installation and upgrade
  • Update Linux installers to use new log location (/var/log/remotely)

Docker Image

See Docker Hub for instructions on pulling and running the image.

v2023.01.01.1855 Release

02 Jan 04:47
Compare
Choose a tag to compare

This is a follow-up to yesterday's release that fixes the following:

  • When using Docker, changes on the Server Config page (which saves to appsettings.json) weren't reflecting in the web app unless the container was restarted
  • The installer wasn't able to extract the embedded server data
  • Logs are now being saved to C:\ProgramData\Remotely\Logs on Windows and /var/log/remotely on Linux

Docker Image

See Docker Hub for instructions on pulling and running the image.