doppelt.digital Application Platform Documentation
English Deutsch

Preparation

Workspace VM Troubleshooting

Quick checks when connection, tools, or local services do not work as expected.

On this page

RDP or desktop does not respond

Check hostname, RDP port, and user on the workspace start page. Restart your RDP client and connect again. If the VM was provisioned recently, wait a moment until all services are ready.

The RDP/SSH hostname must be workspace-<slug>.workspaces.application-platform.com and resolve via Tailscale. If SSH to *.workspaces-dev.application-platform.com lands you on root@proxmox, you are hitting the public gateway DNS – that is not the workspace VM.

Windows App (macOS): password prompt, then nothing

The password dialog often appears locally before any network connection. If there is no visible error, check Tailscale first:

  1. Tailscale is connected and MagicDNS is active (tailscale status shows the workspace host as online).
  2. The hostname resolves: dscacheutil -q host -a name workspace-<slug>.workspaces.application-platform.com → an IP in 100.64.x.x.
  3. The port is reachable: nc -vz workspace-<slug>.workspaces.application-platform.com 3389.

If steps 2/3 work locally but Windows App still fails silently, try connecting with the Tailscale IP (100.64.x.x) instead of the MagicDNS name – the app sometimes fails to resolve MagicDNS. Alternatively use FreeRDP (sdl-freerdp) with /cert:ignore for a clear error message.

Windows App logs: ~/Library/Containers/com.microsoft.rdc.macos/Data/Library/Logs/Windows App/. Typical entries: Name resolution failed / Connection refused (DNS/route) vs. a later successful RDP handshake.

Error 0x207 (“expired password”)

After the password dialog you may see Error code: 0x207. The “expired password” wording is misleading – usually the RDP password does not match gnome-remote-desktop, or the CredSSP/NLA handshake fails. Use the password from the Platform connect dialog (copy it), not another account password. If FreeRDP with /cert:ignore reports AUTHENTICATION_FAILED, reset credentials on the VM (grdctl --system rdp set-credentials …).

macOS Windows App + GNOME Remote Login: If FreeRDP works but Windows App shows 0x207 / SSL_ERR_HANDSHAKE_FAILED, the .rdp file must contain:

use redirection server name:i:1

(not i:0). The Platform-downloaded RDP file already sets this. Delete old PC entries in Windows App and reopen the file. Alternative: FreeRDP (sdl-freerdp … /cert:ignore /gfx).

Tool is unavailable

Open a new terminal and verify that asdf knows the expected version:

asdf current

If a project contains a .tool-versions file, switch into the project folder first and then start the dev script again.

Local service blocks the port

If a dev script fails because a port is already in use, stop the old process or old Docker containers. Backend projects start Docker services with docker compose; frontends and homepages use fixed, incremented local ports.

Project folder is missing

Check whether the repository was cloned and whether you are working in the shared group folder. If a repository is missing, clone it from the project group.