Skip to content

v2023.01.06.1648 Release

Choose a tag to compare

@bitbound bitbound released this 07 Jan 01:34
56ee561

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.