Carl Marien

Hello Ivan,

Thank you for testing, that confirms the class changes every session.

The HTML control ID also matches a field’s placeholder, so please try this under Login → HTML control ID:

Username ID: [USERNAME]

Password ID: [PASSWORD]

Login button ID: [Enter]

Type the placeholder exactly as shown, with the capital.

If you use the embedded browser, also set Autofill on every page navigation to Yes in the Login tab.

If the code still isn’t filled, please send your RDM version and tell me if you use embedded or external mode.

Best regards,

Hello,

Thank you for your patience. I was able to reproduce the issue on Fedora 45. It comes from Fedora 45 moving to OpenSSL 4, which the runtime bundled with Remote Desktop Manager does not detect yet. I’ve reported it to our development team so it can be fixed in a future version.

In the meantime, you can work around it by telling the runtime to use OpenSSL 4.

To test it once, run this from a terminal:

DOTNET_OPENSSL_VERSION_OVERRIDE=4 remotedesktopmanager

To make it permanent, so Remote Desktop Manager also starts from the application menu:

mkdir -p ~/.config/environment.d
echo "DOTNET_OPENSSL_VERSION_OVERRIDE=4" > ~/.config/environment.d/rdm-openssl.conf

Then log out and back in to your session.

Let me know if this works for you.

Best regards,

Hello,

Thank you for the details and the full error output.

I’m installing Fedora 45 on a test machine so I can reproduce the issue on our side. I’ll keep you informed as soon as I have results.

Best regards,

Hello,

Thank you for the version. We confirmed that 2026.3.16 still has this behaviour. It’s tracked by our development team, but a fix isn’t scheduled in a specific version yet.

For now, the most reliable workaround is a fixed terminal size on your SSH entries:

1. Select all the Cisco SSH entries, right-click > Edit > Batch edit > Edit entries (Advanced). You can also edit each entry.

2. Go to Terminal settings.

3. Set Terminal size to Fixed size and enter the columns and rows you want (for example 120 × 40).

With this, every session opens with the right size, even when you open several at the same time, and the --More-- prompt only comes after a full screen.

We’ll update you when the fix is available in a release.

Best regards,

Thank you for confirming that version 2026.3.2.1 fixes the crash when an SSH session closes.

Thank you as well for sharing the settings that fixed the light context menu. Giving the Flatpak read access to xdg-config/gtk-3.0 and setting GTK_THEME to the dark variant is a good way to make the terminal menu follow your system theme. It will help other users who see the same thing.

About the ~/.ssh folder, your suggestion has been passed on to the team. For now, the override you use is still the way to let RDM read your known hosts and save keys there.

Since everything is working on your side, I will close this ticket. If anything else comes up, just reply here.

Best regards,

Hello,

Thank you both for confirming that version 2026.3.2.1 fixes the missing Syntax highlighting settings. We’ll go ahead and close this case.

If anything related comes up after you update your other machines, just reply here and we’ll take another look.

Best regards,

Hi Andreas,

Thank you for testing 2026.3.2.1 and for the detailed feedback.

I’ve passed your four points to our development team:

1. The mouse cursor is very small when HiDPI optimization is off and desktop scaling is 100%

2. Scrollbars appear in fullscreen in both Dynamic resolution and Scrollbars modes

3. A 1 px non-remote line shows at the top (sometimes at the side) of the session

4. When HiDPI optimization is off, the Automatic desktop scaling setting still uses the client OS scale instead of 100%

I’ll get back to you as soon as I hear from them.

Best regards,

Hello,

Thank you for confirming that 2026.3.2.1 fixes the issue. Ctrl+D, the function keys and Insert now reach the SSH session again, as expected.

I’ll mark this thread as resolved. If anything related comes back, reply here and we’ll look into it.

Best regards,

Hello,

Thank you for testing version 2026.3.2.1 and for the detailed feedback.

1. Reconnect always applies to the last tab

We tried this on our side with several SSH tabs open in 2026.3.2.1, and we could not reproduce it. Reconnect applied to the active tab each time. To help us find what is different in your setup, could you send us:

• A screenshot of RDM showing your open tabs, ideally taken just after you trigger Reconnect and the wrong tab reconnects.

• How you start the reconnect: the Ctrl+R shortcut, the menu (which menu?), or the tab’s right-click context menu. If you use more than one, please tell us whether they all behave the same way.

• Whether your tabs are docked in the main window or undocked/detached.

2. Duplicating a Quick Connect tab

Thank you for confirming. This is still with our development team, and we’ll let you know when a fix is available.

3. SFTP

We’re glad the SFTP button now opens the browser. Thank you for the suggestions: an option to hide hidden files and folders, and sorting options such as alphabetical order for folders. We’ll pass both to our development team as feature requests.

Best regards,

Hello,

Thank you for testing and for the detailed feedback.

We’re glad to hear that 2026.3.2.1 resolves the issue. The fix covers both the original Alt/Meta problem in SSH sessions and the arrow-key problem in Windows RDP sessions after switching tabs.

We’ll consider this topic resolved. Thank you both for your patience and collaboration.

Best regards,

Hello,

Thank you for checking the remote and for sharing the output.

You are right, the Flatpak “current” branch is still on 2026.3.1.2.

The 2026.3.2.1 build did not publish correctly to the Flatpak repository, and our team is fixing it now.

This delay is not expected, it is not the usual release schedule.

I do not have an exact date yet, but a normal flatpak update will install 2026.3.2.1 as soon as it is available.

In the meantime, if the crashes get in your way, you can use version 2026.3.2.1 from the DNF repository, which you used before without issue.

Thank you as well for the details on the ~/.ssh folder.

Storing known hosts in a folder RDM already has access to, such as ~/.rdm, is a clear proposal, and I will pass it on to the team.

I am glad the override works well for you in the meantime.

Once you are on 2026.3.2.1, please let me know if the SSH crash or the light context menu still shows up.

Best regards,

Hello,

Thank you for reporting this. We know about formatting problems in the new editors that came with Remote Desktop Manager 2026.3, and our development team is working on them.

To link your case to the right ticket, could you send us:

1. Your exact RDM version (Help > About).

2. Where you write these notes: an entry’s Documentation tab (Markdown or HTML page), a Document entry (Word/RTF), or the Notes field?

3. Your workspace type (Devolutions Server, Devolutions Cloud, SQL Server, …).

As soon as we have this, we’ll add your case to the existing ticket and let you know when a fix is released.

Best regards,

Hello,

Thank you for the details and screenshots.

We have reproduced this behaviour. In current RDM 2026.3 builds, when several SSH sessions open at the same time, every tab except the first connects with a small default terminal size (13 rows × 48 columns). The tab is resized when it’s shown, but Cisco IOS only reads the terminal size at login. That’s why you see the extra line wrapping and the --More-- prompt after only a few lines. Sessions opened one at a time aren’t affected. This is logged with our development team as a regression and will be fixed in an upcoming release.

Until then, any of these will work around it:

1. Use a fixed terminal size (recommended): edit the SSH entries (you can select them all and use Batch edit), go to Terminal settings, set Terminal size to Fixed size and enter the columns and rows you want (for example 120 × 40). Every session then opens with that size, even when you open several at once.

2. Run terminal length 0 (and terminal width 0 if needed) on the switch once the session is open. You can add these as an After opening typing macro on the entries.

3. Open the sessions one at a time.

Could you confirm which RDM version you’re using (Help > About)? That way we can make sure you get the version with the fix.

Best regards,

Hello,

Thank you for the detailed report.

The crash when an SSH session closes is a known issue in the 2026.3 builds before 2026.3.2.1.

It is fixed in version 2026.3.2.1, released on November 2.

Please update the Flatpak with flatpak update, then check the version under Help, About.

After the update, closing the tab, using Close from the navigation pane, rebooting the remote host or cancelling the key import should no longer close RDM.

About the ~/.ssh folder, a Flatpak app runs in a sandbox and only sees the folders it is given.

For now, the override is still the way to let RDM read and save keys in that folder.

I will pass your suggestion to make it a default to the team.

About the light context menu in the SSH terminal, the terminal uses a native GTK menu, while the rest of the window is drawn by RDM.

Installing the Flathub GTK theme that matches your desktop, such as Breeze, may make that menu follow your dark theme.

If it still shows in light mode on 2026.3.2.1, a screenshot would help us report it.

If RDM still crashes after the update, start it from a terminal and keep the full output.

Best regards,

Hello,

Thank you for confirming. I’m glad to hear that version 2026.3.2.1 fixed the issue and that closing the tab now disconnects the session correctly.

Thank you again for your detailed report and measurements. They helped us reproduce the issue and get it fixed.

I’m marking this topic as resolved. If the issue comes back or you need anything else, just reply here or open a new topic.

Best regards,

Hello David,

Thank you for the detailed description.

When you create entries from a template group, Remote Desktop Manager only asks for the destination.

It does not open the Properties window like a single template does, so there is no prompt for the host or URL at that point.

There is another workflow that gives you the result you want:

1. Create the Website entry first with Add > Add entry (or from a single Website template), and enter the real URL in its properties.

2. Right-click the new entry and select Edit > Edit (special actions), then choose Convert with template and click OK.

3. Select your template group, tick Add template subentries, make sure your entry’s URL is kept, and click OK.

The template group’s subentries are then added under your entry.

Their variables resolve against the URL you have already entered, so there is no need to edit the parent afterwards.

The steps are also described here: https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/convert-an-entry-with-template-groups/

Best regards,

Hello,

Thank you for the detailed report and the screenshots.

We were able to reproduce this on Remote Desktop Manager 2026.3.16.

When you use Auto-Typing from the Home ribbon, it uses the entry selected in the Navigation pane instead of the session in the active tab.

If a credential entry or another session is selected there, its credentials are typed.

We have reported this to our development team so it can be fixed.

Until then, either of these will type the correct credentials:

• Right-click the session tab and select Auto-Typing, as you noticed.

• Click the session’s own entry in the Navigation pane before you use Auto-Typing from the ribbon.

Best regards,

Hello,

Following up on the first behavior you described, where the ribbon Auto-Typing keeps typing the same password while the Navigation pane is minimized.

We have now reproduced it on Remote Desktop Manager 2026.3.16.

Auto-Typing from the Home ribbon uses the entry selected in the Navigation pane instead of the session in the active tab.

Switching tabs does not change that selection, and it stays the same while the pane is minimized.

That is why the last typed value keeps coming back until you open the pane again.

We have reported this to our development team so it can be fixed.

Until then, click the session’s own entry in the Navigation pane before you use Auto-Typing from the ribbon.

Best regards,

Hello Ivan,

Our development team got back to me. The HTML control ID fields accept an element’s id, name or class name. Placeholder and aria-label values aren’t supported. The OTP field on the Veeam page has a class that stays the same between sessions, so we can use that:

In the entry, under Login → HTML control ID:

Username ID: [USERNAME]

Password ID: [PASSWORD]

One time password ID: gMKwFf

Login button ID: [Enter]

Keep the OTP set up under General → One-time password (OTP). In our test with a page built like the Veeam login, opened in the embedded browser, the code was filled in.

Veeam generates that class name automatically, so a future Veeam update could change it. If the OTP stops filling, inspect the code field again and use the new last class in its class="…" value.

Could you try it and let me know if it works on your appliance?

Best regards,

Hello Rob,

Thanks for the extra test, that’s very helpful.

This looks like the same underlying problem: when the server rejects the write (disk full or no permission on the destination folder), Remote Desktop Manager doesn’t show the error and still reports the transfer as completed.

I’ll update this thread as soon as I have news from the team.

Best regards,

Hello,

Thank you for the detailed report and the captures, they made this very easy to test.

I reproduced the issue in our lab with RDM 2026.3.16.0 and an rclone WebDAV server.

With the Home directory set to /, RDM sends the request to // and every item loses its first character.

The subfolders also cannot be opened, because RDM then asks the server for the shortened names.

I confirm this is a bug in RDM, not in your server.

I reported it to our QA team with both of your requests.

The first is to build the names correctly from the server answer.

The second is to accept / as the Home directory without sending //.

I will let you know as soon as a fix is available in a release.

Best regard

Hello,

Thank you for the detailed logs and the curl comparison, they helped a lot.

I was able to reproduce the issue in our lab with Remote Desktop Manager on Windows.

I set up a Pure-FTPd server that refuses the EPSV command, like your server does.

Remote Desktop Manager logs in, falls back to PASV and gets a valid reply, but it never opens the data connection.

Because of that, it never sends LIST or MLSD, and the remote pane stays empty.

Each refresh only sends PASV again, which is why you see it twice in your log.

On the same server with EPSV allowed, the listing works right away.

This confirms the problem is in the FTP component of Remote Desktop Manager, which is shared by Windows and macOS.

I am reporting it to our development team, and I will update you as soon as I have news on a fix.

There is currently no setting to disable EPSV in the FTP entry.

In the meantime, here are a few workarounds:

Ask your hosting provider to allow EPSV, since the server lists it as supported but refuses it.

Use SFTP instead, if your hosting provider offers it.

Use the FileZilla or WinSCP FTP entry type, which opens the connection in that external application.

Best regards,

Hallo Herr Weyerstrass,

vielen Dank für Ihre Rückmeldung.

Damit wir das genauer eingrenzen können: Ist das Verhalten mit der Version 2026.3.16.0 exakt dasselbe wie vorher? Also: Die Anmeldeseite wird angezeigt, aber der Button „Weiter mit Microsoft“ wird nicht automatisch geklickt und sonst passiert nichts?

Oder hat sich etwas verändert, zum Beispiel:

• Der Button wird kurz markiert oder fokussiert, aber nicht ausgelöst

• Eine Fehlermeldung oder ein Hinweis erscheint

• Die Seite lädt neu oder leitet weiter, ohne dass der Klick erfolgt

Könnten Sie außerdem unter Hilfe > Info kurz bestätigen, dass die Version 2026.3.16.0 angezeigt wird?

Vielen Dank und freundliche Grüße

Hello,

Thank you for the update, and we’re glad Auto-Typing works again in 2026.3.16.0.

We tried to reproduce the two behaviors you described on 2026.3.16.0 but couldn’t. To keep this forum organized, could you please open a new forum thread for each of them? Please include:

• The exact steps to reproduce it

• A screenshot or a short recording (shared through a OneDrive/SharePoint link or a similar file-sharing service)

Since the original problem is now resolved, we’ll close this thread.

Best regards,

Hello,

Thank you for your patience.

Our QA team has reproduced the remaining issue with the arrow keys in Windows RDP sessions.

It is tracked as its own bug, and the fix has passed our internal testing.

The fix will be included in Remote Desktop Manager Linux 2026.3.2.0, which should be released in the next few days.

Until then, pressing the Alt key once after you return to the RDP tab restores normal input.

Switching to another tab and back also works.

Once 2026.3.2.0 is out, please update and let us know if the issue is resolved.

Best regards,