Back up before updating. The database changes automatically at startup and cannot be changed back. Update signal and web together to the same release.
Packages (Debian · Ubuntu): Check for and install a new release in Admin › Updates. This works only on servers installed from the packages.tastedev.net repository; other servers show "This server does not use automatic updates".
journalctl -u tasteremote-update.Windows and RPM servers: Download the new packages and install them yourself.
Docker: Pull the new release of the repository, then bring it up again.
git pull && docker compose up -d --buildA host updates only up to the release of the server it is registered to. After updating the server, also fetch the new release of the host installers on the server with sudo tasteremote-fetch-hosts. Hosts installed with MSI or deb are prompted to install the new package; hosts installed with zip, setup.exe, AppImage, rpm or dmg have no automatic update, and users must install the new release themselves.
A host whose first two version numbers differ from the server's cannot be connected to, so after a server upgrade connections may be blocked until the hosts catch up. If a host cannot be updated right away, RD_HOST_VERSION_CHECK=off turns this check off.
Allow updates from the server: When on, this device's owner and the server administrator can update this computer from the signaling server. Only the server's version with a verified signature is installed. --allow-server-update
journalctl -u tasteremote-signal, journalctl -u tasteremote-webdocker compose logs --tail=200 signal%ProgramData%\tasteremote\logsLogs contain no secret values. Use LOG_LEVEL=debug for more detail.
| Symptom | What to do |
|---|---|
| The server does not start | Look at the first line of the log. It shows a settings error such as a missing RD_SETUP_TOKEN, a TURN_SECRET shorter than 16 characters, a missing or http RD_WEB_ORIGIN, or TRUST_PROXY=true. |
| No certificate is issued | Check that DNS points to the server and that 80 and 443 are open. |
| Sent back to the login page, or "The request was refused" | Check that the browser address is exactly the same as RD_WEB_ORIGIN. |
| The screen does not connect (TURN) | Check ports 3478 and 49160–49200, and TURN_EXTERNAL_IP. |
| All users get "Too many requests" at once | Set TRUST_PROXY to the number of proxies. |
| No installers on the download page | Run sudo tasteremote-fetch-hosts. |
| The server setup wizard's WebSocket check gives 400 or 426 | The proxy dropped the WebSocket Upgrade header. Check the configuration the wizard made again. |
Send bug reports and suggestions to Product support.