Support

@everyone, The Integrated Security authentication method on SQL Server data source is broken in RDM Mac 5.5.0.0, because of a change made by Microsoft inside the framework Xamarin.Mac. We are waiting for a fix from their end. For more details on the issue, please consult https://github.com/mono/mono/issues/9028 As of now, the workaround would be to use database User to authenticate on the data source or rollback to RDM 5.4.0.0. This version can be downloaded here https://cdn.devolutions.net/download/Mac/Devolutions.RemoteDesktopManager.Mac.5.4.0.0.dmg I will update this post later when we will get more information's about the situation. Best regards,

Hi Devolutions Team, I noticed that the option for ManageEngine Password Manager Pro is missing under 'My Account Settings' in the Remote Desktop Manager for Mac client (version 2026.3). Key details: - It was working as expected up until 3 days ago. - The same setting/integration remains visible and accessible on the Windows client for the same setup. - I have performed a complete clean re-install on macOS (including clearing preferences, Application Support folders, and cache at ~/Library/Application Support/com.Devolutions.RemoteDesktopManager), but the integration entry is still missing under My Account Settings. [image] Could you please confirm if this is a known UI regression in the latest macOS build, or if there is a specific configuration step required to restore it? Thank you!

I have a situation where I connect to customer sites using AnyDesk making use of its TCP tunnelling feature (it is tons more stable than their big name VPN). The TCP tunnelling allows mapping a local port to a remote host port, then locally I connect to localhost and a custom port number. The custom port number isn't a requirement, but I have created a register of customer servers I connect to and assigned a unique local port number so that I can connect to multiple sites at the same time, i.e., instead of mapping 3389 on the remote host to 3389 locally I map local ports in the range of 10000-11000 to 3389 for the different servers. This has all been working great until either of Mac OS 27 or the new RDM Mac version (2026.3.0.5) where now RDM is stating Unable to connect to host localhost , however a test connection to the same is working fine and the backup RDP tool (Windows app for just in case) is connecting just fine. [image] [image]

As the title states, is this even a supported scenario on macOS? I've tried every combination and format of the domain and username, e.g. ".\AzureAD\user@domain.com" but with no luck. Local admin user or other proper domain joined hosts work just fine. Couldn't find a documentation article which addresses this functionality. [image] Thanks Janic

I tried to find the setting that controls when and why an RDP entry in the console is marked as expired and can no longer be used. It seems to be hidden somewhere in a rather unintuitive location :O

Hi, I am experiencing an issue with RDP authentication using Kerberos. The error presented by RDM is: Unable to connect to host dc.conteclab.local ERRCONNECT_CONNECT_TRANSPORT_FAILED (0x0000000D) The domain in question has been configured to disable NTLM and enforce Kerberos as the only possible method of authentication. Actions Taken: • A configuration file /etc/krb5.conf was created with all the necessary domain data for Kerberos, including the resolution of SRV records. • FQDNs are being used instead of IP addresses. • A successful test was performed using the kinit command. • Microsoft’s Remote Desktop Manager application was downloaded and used successfully to access the Windows server via RDP. The version of RDM is 2024.2.9.2 (August 8, 2024). A detailed log of the login attempt is attached. Thanks in advance

[image] Hello I don't know whether I should look for the error on the server or on the client.?

for SSH cert-based auth, I got my public key signed by private CA on SSH server and install it to the ssh key credential (snap1.png) [image] in ssh session, there is no option to read the signed cert from the ssh key credential. The options File (local) and Embedded data works fine if I provide the signed public key. (snap2.png) [image] Please help to check if this request is fesible or not. Regards, Eric

Since the upgrade to macOS 27, RDM is crashing over and over - I cannot keep it open for long stretches. Is there any known issues w/this setup? Attached the crash log in case it helps. Seems to be directed to audio.

Hello, we are currently evaluating the SSH functionality of Remote Desktop Manager for macOS and are experiencing an issue with a setup based on OpenSSH User Certificates , Openbao Vault , and a YubiKey PIV smart card . Environment Remote Desktop Manager: 2026.3.1.2 Operating System: macOS 27.0.1 SSH Server: OpenSSH_8.9p1 Ubuntu Authentication: User certificates issued by Openbao Vault SSH CA Certificate validity: 24 hours Private key stored on a YubiKey PIV PKCS#11 provider: /usr/local/lib/libykcs11.dylib Working OpenSSH Configuration The following OpenSSH configuration works correctly from the macOS terminal: PKCS11Provider /usr/local/lib/libykcs11.dylib Host * IdentityFile ~/.ssh/vault-ssh-cert.pub The user certificate is regularly renewed via Vault and stored as: ~/.ssh/vault-ssh-cert.pub When connecting with the native OpenSSH client, the authentication succeeds. OpenSSH debug output shows: Offering public key: /Users/user/.ssh/vault-ssh-cert.pub RSA-CERT Server accepts key: /Users/user/.ssh/vault-ssh-cert.pub RSA-CERT using private key "Public key for PIV Authentication" for certificate Enter PIN for 'YubiKey PIV': Authentication is then successful. RDM Configuration In RDM we configured: Global Settings Smart card PKCS library: /usr/local/lib/libykcs11.dylib SSH Session Host: server.interhyp-intern.de Username: user Use smart card: Enabled Use SSH authentication agent: Enabled Certificate type: File (local) Certificate: ~/.ssh/vault-ssh-cert.pub Private key type: No private key RDM Log Output The RDM log shows that the YubiKey and PKCS#11 provider are successfully detected: Trying smartcard authentication Opening PKCS11 provider: /usr/local/lib/libykcs11.dylib Available smartcard keys: 5 However, the authentication fails before any PIN prompt appears: Validating public key: rsa-sha2-512 Key is not accepted by server Validating public key: rsa-sha2-512 Key is not accepted by server Validating public key: ssh-ed25519 Key is not accepted by server No keys accepted by server: 6 tried The session then falls back to password authentication. Question Does the SSH engine used by Remote Desktop Manager for macOS support: OpenSSH User Certificates (ssh-rsa-cert-v01@openssh.com / RSA-CERT)? SSH certificates issued by a HashiCorp Vault SSH CA? Authentication using an OpenSSH user certificate combined with a YubiKey PIV key via PKCS#11? Based on the logs, it appears that RDM successfully discovers the smart card keys but does not offer the OpenSSH certificate (vault-ssh-cert.pub) to the server in the same way as the native OpenSSH client. Could you please confirm whether OpenSSH User Certificates are supported by the macOS SSH engine and, if so, provide the correct configuration for this authentication model? Thank you for your assistance. Best regards, Robert

Hi all, I have a Website entry that is tunneled through Devolutions Gateway. It works fine in RDM Windows, but RDM macOS crashes as soon as I open it. Environment - RDM macOS [current version], macOS 27 - RDM Windows 2026.2.17.0 (works) - Devolutions Server and Devolutions Gateway on the current release - RDP entries through the same Gateway work fine on both Windows and macOS Entry configuration - Type: Website, embedded browser (Safari/WebKit, the only option on macOS) - URL: https://<internal-ip>:4343 - VPN/Tunnel/Gateway: Type = Devolutions Gateway, Open = Always connect Current behaviour RDM macOS crashes immediately when the entry is opened. History - Before updating DPS: the embedded browser stayed blank. - After updating DPS (macOS 2026.3.0.5 and 2026.2.5.1, before macOS 27): error "Could not connect to the server. Error Code: -1004 - Proxy Address: 127.0.0.1:<port> - Gateway: True". - At that time, lsof showed no listener on the announced proxy port (only [::1]:19443 for RDM), and curl through the proxy returned "Connection refused". The local Gateway proxy was never started. - Since upgrading to macOS 27: RDM crashes instead of showing the error. Expected RDM macOS starts the local Gateway proxy and the embedded browser loads the page, as RDM Windows does with the same entry. The Gateway itself works without issues for other session types, e.g. RDP connections work fine from both Windows and macOS. [image] Thank you. best regards Lukas

Hello Whenever I go back online, I am always asked to synchronize this item, but I don't understand what it is. Thanks [image]

Title: RDM 2026.3.1.2 (macOS): Hub connection times out when hostname has unreachable IPv6 (AAAA) addresses, no fallback to IPv4 Remark This bug report mostly serves for logging purposes and possible circumvention proposals in case any other Devolutions’ customers may experience related issues. Environment - RDM for macOS 2026.3.1.2 (.NET 10.0.12), updated 05/10/2026 from 2026.2.5.1 - macOS Tahoe 26.6.2 - Data source: Devolutions Hub Business (`example.devolutions.app`) - Network: dual-stack (native IPv4 + IPv6) Problem Every HTTP call from RDM fails: the Hub login, the update check, and so on. Other apps on the same Mac work fine. RDM throws a connect timeout: System.Threading.Tasks.TaskCanceledException: OperationCanceled ---> System.TimeoutException: net_http_connect_timedout at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(...) at System.Net.Sockets.SocketAsyncEventArgs.<DnsConnectAsync>g__Core|113_0(MultiConnectSocketAsyncEventArgs ...) ... at Devolutions.RemoteDesktopManager.Business.DataSources.HubClientDelegate.SendWithTimeoutAsync(...) at Devolutions.Hub.Clients.HubClient.GetServerConfigurationAsync(...) at Devolutions.RemoteDesktopManager.Business.DataSources.HubConnectionDataSource.Login() Cause The local DNS resolver had DNS64 enabled without a NAT64 gateway. That's a misconfiguration on my side, now fixed. It caused the Hub hostname to resolve to unreachable IPv6 addresses alongside the working IPv4 ones: $ dig +short AAAA example.devolutions.app 64:ff9b::8d65:5a60 (x4, unreachable) $ curl -6 https://example.devolutions.app -> connect timeout $ curl -4 https://example.devolutions.app -> HTTP 200 curl, browsers and other macOS apps fall back to IPv4 within milliseconds. RDM keeps trying the IPv6 addresses one after another ( MultiConnectSocketAsyncEventArgs ) until its own timeout in HubClientDelegate.SendWithTimeoutAsync expires, so it never reaches IPv4. Workaround Remove the unreachable AAAA records: disable DNS64, or turn off IPv6 on the Mac. RDM then connects immediately. Request The same failure will happen on any network with broken or partial IPv6, such as hotel, guest and some corporate networks. Could you: 1. Check whether something changed in 2026.3.1.2 in the HTTP handler or the connect timeout? I didn't see this with 2026.2.5.1 . 2. Consider IPv4/IPv6 fallback ("Happy Eyeballs", RFC 8305) in the Hub client. For example, use SocketsHttpHandler.ConnectCallback to race the addresses, or use a short per-address connect timeout instead of one overall timeout.

Hi, I have been struggling for a while around getting special characters from my Mac to a Windows Server via RDP. Sending $, |, @ and a few others (forgot which ones) seems impossible. I have tried different things like setting the Keyboard layout and Sending input as Unicode, in settings for RDP sessions but none of my efforts seems to work. Can anyone help getting these characters to work?

Since few weeks, on RDP session opened with RDM on Mac, the mouse cursor doesn't reflect the right position of the click. It's like I am clicking somewhere else.

Hello RDM for MAC osx tahoe 26.7.1 V2026.3.1.2 and V2026.3.0.5 (i make rollback) doesn't reconnect to workspaces. It rest OFF line without the possibility to see any password of credential items. Lates version in windows 11 work well with same Devolution server. Can be a Mac OSX problem? Thanks [image]

It seems like in the latest version of Remote Desktop Manager ( 2026.3.1.2) for macOS, the only way to launch an entry is to now press control + enter from the "find quickly" search box. Am I missing a setting where you can change that behavior? It seems like by default pressing return now just selects the entry in the sidebar? I would much rather be able to only press return after typing a few characters to show the host I want to connect to. I've looked through past/recent posts and it seems like a lot of the interface and settings options around this feature has changed. Thank you!

New user to RDM and I'm trying to figure out how to get my remote session display to fill my screen. I've tried turning "Scaled" on & off, no change. Tried using a virtual display, and using a HDMI dummy plug, but no change. And I've tried multiple screen resolutions, but no change. I am sure I'm missing an obvious setting somewhere but my Google & forum searching haven't turned up a solution. [image]

RDM macOS 2026.3.0.5, .NET 10.0.12 Hierarchy: Company folder > subfolder > SSH entry Company Custom field 1: somekey.pem Global variable SSH_KEY_DIR: path/to/ssh/key/dir Works in the SSH private-key path: $SSH_KEY_DIR$/somekey.pem Fails with “private key does not exist”: $SSH_KEY_DIR$/$COMPANY_CUSTOM_FIELD1$ Both $COMPANY_NAME$ and $COMPANY_CUSTOM_FIELD1$ resolve correctly in the same connection’s tab title. The private-key path is configured directly in that connection.

I'm using RDM Mac 2026.3.0.5, I have RDM configured to have the user interface configured to Use overlapping navigation , I like it this way as it means the screen real estate is maximised for RDP use. [image] For the lack of a better word, the main difficulty I have with this is that if you are in an RDP session and need to open another in order to get the navigation pane to display you have to take focus out of the remote session and press Cmd+N, I accomplish this by clicking the RDM menu and pressing this keyboard shortcut. With this latest build of RDM introducing a toolbar on the main window makes it an ideal place to put a button or shortcut to the navigation pane. Is this possible or could this be added? For reference, in the screenshot below I am connected to my Windows desktop that I need to use for a VPN connection that has no Mac equivalent. On the Windows RDM you can have the navigation pane off to the left for quick and easy access to it. The highlighted red block is the new toolbar on RDM Mac where I'm asking/proposing this could be - better yet, if this was done on the new toolbar in RDM Windows then it would mean the UI/UX would be more closely aligned between the two. [image]

Hello, I'm currently using the latest MacOS version of RDM and I am using SSH jump hosts (as a VPN). I am able to connect to a remote host which is not directly reachable via a SSH session. This works great. (also, i frequently use the Windows version of RDM, so hopefully this possible solution is cross platform) But i'm now trying to figure out if it's possible to use multiple jump hosts. SSH to JumpA and then SSH to JumpB and then SSH to targetC. This is all possible with the SSH protocol. But i'm not sure how to implement it in RDM. TargetC in my case is only available via JumpB (IPv6LL). I would use IPv4 to JumpA and then IPv4 to JumpB from JumpA and then IPv6LL from JumpB to TargetC. Here is the CLI equivalent: ssh -J user1@host1:port1,user2@host2:port2 user3@host3 This is taken from: https://wiki.gentoo.org/wiki/SSH_jump_host I can do it via the CLI. But you get prompted for password for each host. Looking to create multiple saved entries and have RDM pass the password silently to the jumps and target. Again, all this works great using the SSH Link as my one layer of Jump Host. I apply it at the folder level and all the objects inherit the VPN config. I can set it for no VPN if i'm onsite, or set it for VPN if i'm remote. NOTE: i could not get the above CLI to work for IPv4 and IPv6LL combo. I was able to get it to work if it was IPv4 from JumpB to the TargetC. [image] [image]

MacOS: Tahoe 26.6.2 RDM MacOS: 2026.2.4.4 We are seeking replacement of Microsoft RD Gateway, and GO Remote Desktop Gateway ( https://github.com/bolkedebruin/rdpgw ) is one of candidates. During the evaluation, we have succeeded to make rdpgw to support OpenID Connect and PAM/local authentication in different setup. OIDC works great for on demand connection, but PAM/local authentication fits our RD client scenario more. One of requirements to use PAM/local authentication is RD client needs to support basic authentication (via TLS). I checked RDM for possible option to enable/use basic authentication when connecting via rdpgw, but no luck. Would you be kind to elaborate more info? here's the .rdp file to test basic authentication via rdpgw. It works with Windows app (from App store) full address:s:10.104.103.111:3389 gatewayhostname:s:test04.lab123.com gatewayusagemethod:i:1 gatewaycredentialssource:i:4 gatewayprofileusagemethod:i:1 promptcredentialonce:i:0 authentication level:i:2 enablecredsspsupport:i:1 Regards, Eric

Where is the default set for RDP's remote audio property/setting? I can see the setting in the Windows equivalent version of RDM, but I don't seem to be finding it in the Mac one. [image] I think I'm being stupid here, but I'm going to ask instead of accepting defeat and not knowing or finding out 😅

Hi, New macbook pro m4 pro and having only one RDP connection opened, but for 3days, RDM is using 3.5GB of ram. Connection is opened to a LAN PC, and not even focused on the tab (using it for OTP codes mostly). Closing the RDP session does not free up the ram. (also, a bunch of about: processes that exits if application is closed) [image] [image] [image] Version: 2025.3.6.9 Thank you.

I am currently evaluating RDM to replace what I am currently doing personally for Remote Desktop across Windows and Mac platforms and ultimately hoping to pitch it for use in my team as our RDP tool of choice, particularly as it syncs to the cloud (using Devolutions Hub), doesn't require any manual interactions when switching between the two. Basically whatever is setup on the one is available everywhere else... great stuff. I have setup five sites set of connections so far, doing this as I'm going allowing as there another three dozen or so sites needing to be migrated from my current RDP solution. The problem I'm having is that I've hit a situation on two of the sites where when trying to RDP on Windows it works as expected, but connecting on Mac (with the very same connection details in RDM) I receive the following message: Unable to connect to host someserver.somedomain.local Unknown error (0x0000001C) For comparison and as a check, on the same Mac when using another RDP tool for comparison (simply the Windows app) it connects without warning or issue. I have put everything on one of the connections back to defaults, tried numerous things like without NLA, changed it Warn me in the event of an authentication issue, tried quick connect to forgo the properties that I may have customised, etc., but am not making any headway in getting it to successfully connect. What could be the issue? How can I go about troubleshooting this? I would appreciate any guidance and assistance I can get in respect of this.