Bug Report

With the latest 2026.2.1.5 RDM for MacOS, I cannot open any of my saved connections when I double click on them. When I double click on them, I receive a message stating "The action needs an open CyberArk dashboard with an account selected." I have never configured CyberArk on my RDM settings and I checked in all the obvious places and CyberArk isn't enabled, both within the RDM settings and also the individual connection settings. [image] I am still able to open connections if I left-click to select the session and press the "Enter" key and also through the search shortcut of the application (Shift + CMD + \). This is why I think it's a bug and not a newly implemented feature change since I can still open it through the other two methods.

The feature to double-click to close tabs is no longer working. I have it enabled in the settings, but the tabs only close when right-click > Close is selected or the X of th tab is pressed. I have the Double-Click action set to Close, but it's no longer working in the current version (2026.2.1.5). [image]

HI, I am experiencing frequent issues with RDP sessions in Remote Desktop Manager, where the application becomes unresponsive when attempting to copy content from an active RDP session. This issue occurs consistently in approximately two out of every three attempts. When it happens, the application remains unresponsive for a couple of minutes before recovering and functioning normally again. I am currently running the latest version (2026.1.10.3) on an M5 MacBook Pro with the latest version of macOS. Please note that this is a new setup on this MacBook, and the .rdm configuration file was imported from my previous MacBook.

Hello after updating RDP latest build on a old macbook with Ventura 13.7.8, it freeze during loadin connection from devolution server. Rollback to previous version work. Try the cfg rename but unsussesfully. Any ideas? Thanks

I am using RDM on an 2017 iMac running MacOS Ventura 13.7.8. Before the upgrade RDM ran fine. After upgrading to 2026.2.1.5, RDM got stuck with the loading connections part. See attachment. I removed it from my computer, reinstalled it, no matter what I am doing it always ends up hanging at the same step. Does anybody have the same problem? If so, has anybody been able to overcome it? Thank you any comments in advance [image]

How solve this bug when loading devolutions cloud in rdm for macOS in latest version 2026.2.1.2 Unable to convert entry to connection. ID: fdc22095. Name: Devolutions account validation. Exception: Devolutions.Cryptography.DevolutionsCryptoException: NativeError : InvalidMac ===Original Message=== Exception_WasThrown, Devolutions.Cryptography.DevolutionsCryptoException ===Original StackTrace=== at Devolutions.Cryptography.Utils.HandleError(Int64 errorCode) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.ConvertEntryToCommonConnection(Guid dataSourceID, Guid repositoryID, Entry entry) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.ConvertEntryToConnection(Guid dataSourceID, Guid repositoryID, Entry entry, Dictionary`2 entries) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.GetConnections(ConnectionEngine engine, Guid dataSourceID, Guid repositoryID, Guid dataSourceVerison, Int64 repositoryVersion)` ——— Unable to convert entry to connection. ID: 3a0a3c29. Name: Authenticator App. Exception: Devolutions.Cryptography.DevolutionsCryptoException: NativeError : InvalidMac ===Original Message=== Exception_WasThrown, Devolutions.Cryptography.DevolutionsCryptoException ===Original StackTrace=== at Devolutions.Cryptography.Utils.HandleError(Int64 errorCode) at Devolutions.Cryptography.Managed.Decrypt(Byte[] data, Byte[] key, Byte[] aad, ILegacyDecryptor legacyDecryptor) at Devolutions.Cryptography.Managed.DecryptWithKeyAsUtf8String(String b64data, Byte[] key, Byte[] aad, ILegacyDecryptor legacyDecryptor) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.ConvertEntryToCommonConnection(Guid dataSourceID, Guid repositoryID, Entry entry) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.ConvertEntryToConnection(Guid dataSourceID, Guid repositoryID, Entry entry, Dictionary`2 entries) at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.GetConnections(ConnectionEngine engine, Guid dataSourceID, Guid repositoryID, Guid dataSourceVerison, Int64 repositoryVersion)`

Environment Remote Desktop Manager 2026.2.1.2 (64-bit), macOS (Apple Silicon) Embedded RDP engine: …/Remote Desktop Manager.app/Contents/MonoBundle/libDevolutionsRdp.dylib Connection type: RDP (Microsoft Remote Desktop) through an RD Gateway (WebSocket-based, open-source rdpgw) Gateway server: stage-rdpgw.oneclick.services:443 (valid Let's Encrypt cert, reachable, /remoteDesktopGateway/ returns HTTP 401 as expected) Connection Host : a per-session hostname (e.g. u3wsva2djj-stage.oneclick.services) that is only resolvable through the gateway , not via local/public DNS (by design — the gateway resolves it internally) Problem Every connection attempt fails within ~3 seconds with: ERROR Could not establish a secure connection to the host (0x00020008) (occasionally Connection failed (0x00020006)). Nothing ever reaches the gateway server (verified server-side: no handshake/auth is logged). Root cause (from RDM debug+verbose log) RemoteDesktopManager.debug shows, in the same second as the error: DEBUG Network monitoring initialized for host: u3wsva2djj-stage.oneclick.services DEBUG Network transition detected for host: u3wsva2djj-stage.oneclick.services - Pausing connections DEBUG Certificate verification skipped: Network transition in progress → ERROR Could not establish a secure connection to the host (0x00020008) The network monitor then loops endlessly , emitting dozens of identical lines per second and never settling: DEBUG Network restored for host: … - Starting stabilization period DEBUG Network transition detected for host: … - Pausing connections It appears the network monitor performs a reachability check tied to the connection's Host , and because that Host is only resolvable via the gateway (not local DNS), the check fails permanently → it perpetually reports a "network transition" and pauses the connection, so the actual connect never proceeds (TLS/cert verification is explicitly skipped). Proof this is RDM-specific (not network/gateway/target) The native Microsoft RDP client (Windows App / mstsc) connects successfully to the same gateway + same Host from the same Mac and network . A FreeRDP 3.x -based client also connects successfully to the same gateway. Gateway endpoint reachable from the Mac (TCP/TLS OK via openssl/nc); macOS Application Firewall is disabled ; no Little Snitch / network-filter extensions. This connection worked previously (January 2026) on an older RDM version (which used the separate FreeRDPSandboxed.app engine and did not have this network-monitoring behavior). On 2026.2.x no SessionLogs/*.log is written for these attempts — the engine aborts before a session starts. Already tried (no effect) Clean reinstall of RDM 2026.2.1.2 Recreating the connection entry from scratch Gateway Transport = Auto and = HTTP Stopping Tailscale/VPN (the monitor kept flapping for 90s+ afterwards) No user-facing toggle for this in RemoteDesktopManager.cfg Questions / request How can the RDP network-monitoring / "network transition" pausing behavior be disabled? This looks like a false-positive when the RDP Host is only resolvable through the RD Gateway (common with gateway-brokered/per-session hostnames). Can the monitor be fixed to not block such connections (e.g. check the gateway reachability instead of the inner Host)?

Hi, Not really a bug report but with the new UI changes in RDM 2026.2 on macOS, the close buttons for tabs are now on the right side of the tab instead of the left side, which is rather counter-intuitive for Mac users. Just saying. [image] Best regards, Jelle Hillen

Hey, I've been trying to establish multiple embedded RDP sessions with the latest Remote Desktop Manager for MacOS (2026.1.8.6), but none of them worked. I tried to establish "plain" RDP sessions (direct connection to the target machine), but it didn't work. I also tried to establish CyberArk's SIA-RDP connections (with RD Gateway), but it didn't work either. The message I keep getting is "unable to connect to host - CONNECT_FAILED (0x00020006)". I also tried to change the hostname to the public IP, but it didn't work as well. The thing is - I tried all of those sessions with an external RDP client (Windows App triggered via Remote Desktop Manager), and all of them worked. I asked a team member to try on their machine and they got the same issue. The way I configured my RDP sessions was by importing RDP files, which, again, worked well on Windows App. My setup: MacOS Tahoe (26.3.1) Latest Remote Desktop Manager version (2026.1.8.6) Palo Alto Networks VPN

Since latest update (2026.1.12.4) terminal tool struggling to start and if it starts it is starting with the error 22 as yo can see in the screenshot. [image] And it started but the first line has percent sign and only after first enter key it fixes it's place. [image] Thanks

Version: RDM macOS 2026.1.12.2, Devolutions.ProtocolsSharp 2026.4.17.1 Server: OpenSSH 8.9p1 Ubuntu 22.04, xterm-256color Behavior: Session establishes successfully, runs for varying duration (seconds to minutes), then unexpectedly terminates with the above exception. Server logs show clean Received disconnect: Logout (client-side disconnect). Log excerpt attached. Stack: DoShellLoopAsync: Arg_IndexOutOfRangeException at Devolutions.Protocols.Core.Terminal.ExecuteCommand(ReadOnlySpan`1 data) at Devolutions.Protocols.Core.Terminal.ParseXtermData(ReadOnlySpan`1 data) at Devolutions.Protocols.Core.SshClient.DoShellLoopAsync(Channel channel, Upper upper)

We do not know what to do anymore... RDM is constantly failing with error "unable to retrieve 1password credentials". we file a new ticket, they tipically wait a month to fix it, and one or two weeks later it stops working again... are we the only ones using 1password with RDM? is there any reccomandation? Many thanks in advance to who can help us.

Hello Devolutions Support Team, I would like to report a bug in Remote Desktop Manager macOS version 2026.1.12.4 affecting the 1Password integration when DUO MFA is enabled. **Environment:** - RDM macOS: 2026.1.12.4 - 1Password for Mac: 8.10.21 - 1Password CLI: installed and up to date - 1Password account type: Business (baselnetgroup.1password.com) - MFA method: DUO - RDM 1Password config: My Account Settings, Host: Default, Region: Global, Login method: Default **Issue:** When attempting to retrieve credentials from 1Password via RDM, the following error is displayed: "Unable to retrieve 1Password credentials" The Application Log reveals the underlying cause: "PasswordManagerAccess.Common.InternalErrorException: Duo: Duo HTML: the main form is not found" RDM appears to be attempting to handle the DUO MFA flow through its own embedded WebView rather than delegating authentication to the 1Password CLI / 1Password App integration. The "Connect with 1Password CLI" option is enabled in the 1Password App under Settings → Developer, but RDM does not appear to honour this and still tries to process DUO authentication internally — which fails because the current DUO HTML no longer contains the form element RDM expects. **Steps to reproduce:** 1. Configure 1Password in RDM via My Account Settings (Region: Global, Login method: Default) 2. Enable "Connect with 1Password CLI" in 1Password App → Settings → Developer 3. Attempt to use a credential entry linked to 1Password in RDM 4. Observe the error **Workaround:** Using a 1Password Service Account token instead of username/password/MFA resolves the issue, but this is not acceptable as a permanent solution for our organisation due to the reduced security level (no MFA on the service account token). **Expected behaviour:** RDM should delegate authentication to the 1Password CLI / App integration and not attempt to handle DUO MFA via an internal WebView. Please advise on a fix or patch timeline. Best regards, Lukas Schweizer

I use multiple RDP connections over SSH tunnels with VPN default pauser time set to 0 seconds . This worked flawlessly up to 2025.2.12.6 . Even if the SSH tunnel needed ~1 second to fully establish, RDP would automatically connect once ready. Since newer versions, RDP connections only succeed if I manually set at least 1 second pause , even for tunnels that establish instantly. With pause=0, the SSH tunnel connects, but RDP never starts. Additionally, when using SSH tunnels with TOTP + private key only (without static password): if I enter the OTP in the One Time Password setting, it is ignored and I am still prompted for an OTP code. Authentication only succeeds if I enter the OTP into the password field . This issue does not occur when starting the SSH tunnel alone — in that case, the TOTP field works correctly and is automatically used.

If I open / edit and close multiple files on a server that have the same name (eg docker-compose.yml) then whenever one of those files is "saved" in a local editor (VS Code and Mac TextEdit), RDM then automatically uploads the single file being "saved" to the destinations of any files that were opened & closed in the session with the same file name effectively overwriting them with the incorrect content. I am on version 26.1.10.3, this behavior is new. Previously i could open and edit multiple files at the same time. I believe the cause is because the local cache directory where the files are temporarily stored does not take into account of the path of the file on the remote server. IE it just stores docker-compose.yml at the base cache directory. Hope that makes sense? [image]

[image] I'am running the lateset RDM for Mac (2026.1.9.5) and startying from previous relese (2026.1.8.7) stop working change directory on SFTP session Now RDM shown only user home dir and not allow change it (event for root user) Direct sftp to remote server works fine Now in UI in the path if i can type any existing directory on remote server after Enter nothing happen And in local side SFTP broser now showing / instead home dir

Hi, I'm currently running RDM 2026.1.14.4 on macOS Sequoia. Ever since the 2026.1 branch, I regularly encounter issues where icons get "replaced", usually after editing an entry: [image] In the screenshot above, the green ones are actually RDP sessions (with their default icon). The two blue with the transparent arrow should be the default SSH icon. If I click on an entry, that specific entry and those next to it get reverted back to their normal state. This was not an issue in versions before 2026.1. In the screenshot below I clicked on an entry, reverting its icon but also the entry right above it: [image] To me it looks like there's some corruption going on in the icon cache or something like that when saving changes to an entry. I did not notice it yet with folders, and it usually doesn't happen with credential entries, more with session entries. If there's anything you need from me (logs, etc.), please let me know. Best regards, Jelle Hillen

Hi, Since the 2026.1 update on macOS, the Default icon selection seems to have disappeared when trying to change a session's icon: [image] It is no longer possible to keep the icon but change it to a different color (on the Windows-version, this still works). Best regards, Jelle Hillen

I am running Remote Desktop manager 2026.1.9.5 on a macbook m5 pro. I have lots of servers configured but only one that I wish to run undocked. I have "Open undocked sessions in the last created undocked window" checked in the settings, however it opens full screen every time after the main program is closed. If I don't close RDM, it will re-open the window where it was last and at the same time and all is well, but closing the program and relaunching causes the undocked to open full screen except for the top menu bar of the mac. This is 100% repeatable on this machine. Not sure if this is by design or I've missed something or if this is a bug. Thanks for your time and a great piece of software.

The new Find Quickly window is no longer working reliably. When I use the shortcut ( Shift + Cmd + \ ) , the window does not consistently open centered on the screen. With the 2026.1.9.5 release, the behavior improved slightly in that the window now opens on some monitor, but its placement and rendering remain inconsistent. Below are the behaviors I’ve observed. I haven’t identified a specific trigger that determines which behavior occurs: Expected behavior - The shortcut menu opens centered on the monitor where the mouse cursor is currently located. Incorrect rendering (vertically squashed) - The window opens on the correct monitor, but the menu is vertically compressed. For example, a menu that should be approximately 500 px tall appears squashed into roughly 100 px. (Pixel values are illustrative to help describe the issue.) (See image below.) Incorrect monitor and position - The window opens on a different monitor, positioned near the bottom-right corner and sometimes partially off-screen. Aside from the incorrect placement and monitor selection, the window remains interactive and functional. (See image below.) Window appears to open but is not visible - An opening animation plays, suggesting the window is opening somewhere, but it does not appear on any monitor. Typing a known search term and pressing Enter does not produce any visible result, suggesting the window may be fully off-screen or not rendered. [image] [image] [image] [image]

I am connecting to multiple SSH targets through HAProxy running in TCP mode with TLS termination. This setup worked perfectly up to version 2025.2.12.6 using an SSH Terminal configuration with Proxy = Custom + Local + Custom and the following command: openssl s_client -connect haproxy.domain.tld:PORT -quiet -servername %h 2>&1 (The 2>&1 is intentionally added to suppress unnecessary SSL output.) Since version 2025.3.6.7 , this no longer works. The connection immediately fails with IO_EOF_ReadBeyondEOF Devolutions. ProtocolsSharp: 2026.1.8.1 OS: macos unknown option '2>&1' Bytes sent: 24, Bytes received: 0 Packets sent: 0, Packets received: 0 Kex completed: 0problem2: This strongly suggests that command parsing or proxy execution behavior changed between these versions.

We've updated from 2026.1.8.7 to 2026.1.9.5 and the default embedded sing in window had to be disabled. We're using a zero trust conditional access policy where only compliant, joined devices can sign in. The embedded browser window does not share any device information when signing in, according to the sign in logs it looks like an unmanaged device. This feature works without any issues on our Windows devices. [image] Best, Janic :-)

1Password integration in the latest release is broken on RDM for MacOS. More than a week our ticket with support is opened, and replies from support state that development team is working with priority on this issue, but neithere a solution is in sight, nor a workaround. We have big impact on daily operations, luckily we have a premium support contract.....

Please forgive me if this is a mistake on my end, but I just updated to the latest version of Remote Desktop Manager for macOS and the "Find Quickly" search doesn't seem to be returning any results. I've tried poking around in the settings to see if there is something new that I need to enable, but thought I'd post here in case this is an actual bug. I am happy to provide more details, but this is the search that I'm referring to: [image] [image] [image]

The setting New SSH Session > General > SSH Terminal > Terminal > Advanced > Show Hidden files. Working on direct SFTP session. but not in dual panel SSH.