Samuel Oliveira Martel

Hi,

Thank you for following up on this feature request.

We understand your interest in this feature. Unfortunately, we do not have an estimated timeline to share at the moment. We'll be sure to communicate any updates as soon as they become available.

Best regards,

Thank you for the report.

We've reproduced the issue and opened an internal ticket.

We'll keep you updated once it's fixed.

Best regards,

Hi,

Thank you for the detailed report, the debug logs and version bisect were very helpful in tracking this down.

I was able to reproduce the issue and have applied a fix. This will be included in the 2026.2.2.0 release.

Best regards,

@Samuel Oliveira Martel

Thanks for the additional infos about the "Unified VPN" and "Additional Parameters" settings, very helpful.

I understand how Tailscale works and I made sure that everything is working as it should when I do things manually.

For the description you sent:

"This is where the RDM integration helps. In your case, since Tailscale is already running, tailscale up does nothing and RDM connects directly. If Tailscale were disconnected but still authenticated, RDM would automatically bring the tunnel up before establishing the connection." -> I can tell you that it doesn't work like this.

When the tunnel is down and I click on a SSH terminal item with Tailscale VPN configured, it just does nothing. The "tailscale up" is apparently not run, the tailscale VPN stays down and the connection I clicked on in RDM opens a tab, stays down and ultimately just closes itself without any information what happened.

Maybe the tailscale binary is not found at all?

Hi @thomassteiner,

With your feedback, I was able to reproduce the issue on our end. When the Tailscale app is down and an SSH entry with Tailscale VPN configured is launched, the tailscale up command does not appear to be executed. The reason is that on macOS, the tailscale up command requires the Tailscale app to be running first. If the app is not started, the command simply fails silently.

I have opened an internal ticket to address this. The fix will ensure that the Tailscale app is launched automatically before executing tailscale up.

Could you let us know which Tailscale installation method you are using? Is it the desktop app or the standalone command-line tool? This will help us make sure the fix covers your setup as there might be another issue on the standalone command-line implementation.

We'll follow up once a fix is available.

Best regards,

Hi,

Here is a clearer breakdown of how the Tailscale VPN integration works in RDM for Mac:

What RDM does automatically

When you configure Tailscale under the "VPN / Tunnel / Gateway" tab, RDM manages the VPN lifecycle for you:

• Before opening your SSH session, it runs tailscale up to ensure the tunnel is active

• After closing the session, it runs tailscale down to disconnect cleanly if set to On session close

If Tailscale is already connected, tailscale up does nothing and RDM proceeds directly to your SSH session, which is the expected behavior.

What RDM does not handle

RDM cannot perform the initial Tailscale authentication.

• If you have never logged in on that machine, or your session has expired:

  • RDM will show an error asking you to authenticate

  • You must open the Tailscale app and log in manually

• It cannot prompt you to choose between accounts such as work or personal

Once authentication is done, RDM handles the rest.

Why the VPN step matters

The Tailscale IP you are using (100.65.xx.xx) exists only within the Tailscale virtual network. It is not reachable over the regular internet. Without the tunnel active, your Mac has no route to that address, and the SSH connection will time out.

This is where the RDM integration helps. In your case, since Tailscale is already running, tailscale up does nothing and RDM connects directly. If Tailscale were disconnected but still authenticated, RDM would automatically bring the tunnel up before establishing the connection.

Use unified VPN

This setting controls whether VPN configurations are shared across platforms:

• Checked (default) means the same VPN configuration is used on Windows, Mac, and Linux

• Unchecked means Mac uses its own independent VPN configuration

For Tailscale, you can usually leave this enabled since behavior is consistent across platforms.

Additional Parameters

This field lets you pass extra command-line flags to the tailscale up command.

Examples:

• --exit-node=<hostname> routes traffic through a specific exit node

• --accept-routes accepts subnet routes advertised by other nodes

• --hostname=<name> sets a custom hostname

You can run tailscale up --help in your terminal to see all available options.

Hope this clarifies everything.

Best regards,

Hi,

I tried to reproduce the issue you’re experiencing but wasn’t able to replicate it on my side.

Just to confirm, for the username field of the SSH terminal, are you using thomas.s... or tagged-d... as shown in your screenshots? And for the password field, can you confirm that you’re entering the password of the remote machine?

Could you also confirm that the IP address returned by the tailscale ip -4 command matches the one you’re trying to use?

In my tests, I used the “Always ask for password” option and it worked as expected, so you might want to try that as well to see if it changes the behavior on your end.

Also, please make sure that the VPN has been launched recently on the remote machine, as it needs to be active for the connection to work properly.

Best regards,

Hi,

Did you happen to launch Tailscale at least once before launching your entry? The application usually needs to be opened at least once so it can initialize properly before any integration can use it.

From your description, it sounds like the integration may not be able to detect or communicate with the Tailscale client. I’d recommend confirming that Tailscale is installed in the Application folder, running, and that you’re logged in with an active device.

Unfortunately, there isn’t official documentation available for this feature yet, so ensuring Tailscale itself is fully operational is an important first step.

Also, could you share a bit more about your setup? For example, how you configured your entry, and what environment you’re running this on. That would help narrow things down.

Best regards

Hello,

Thank you for reaching out.

Unfortunately, we only support Safari as the embedded browser. Since you are using macOS 12.5.1 and cannot upgrade, this is likely the cause of the issue with the grey panel.

As a workaround, you will need to continue using web sessions in external mode with another browser.

Best regards,

Hello,

Thank you for reporting this.

A fix has been implemented and will be given to QA soon. It should be available in an upcoming release.

We’ll keep you updated once it’s released.

Best regards,

Hi,

Please note that for the keyboard layout change to take effect on the VM, you will need to either restart the virtual machine or log off and log back in to your user session.

If you continue to experience any issues after these steps, please feel free to reply and we will be happy to investigate further.

Best regards,

Hi,

We have managed to reproduce the issue and a ticket has been opened.

Best regards,

Hi,

Thank you for your feature request.

We have opened a ticket for this request. If we need any additional details or clarification, we will contact you. If you have more information to provide, feel free to reply in this post.

Best regards,

Hi,

Thank you for reporting this,

We've identified the issue and have opened a ticket for it.

Best regards,

Hi,

Thank you for reporting this.

We've identified the issue and have opened a ticket for it.

The fix will be available in the next release of RDM Mac.

Best regards,