remmina creates SSH tunnel despite SSH tunnel being disabled

Problem Description

I have a server which forwards a VNC connection on some port. I can however connect to that forwarding server via ssh. In the connection settings I have disabled the SSH Tunnel.

Using remmina's debug window, I can see, that remmina successfully establishes a SSH tunnel to my forwarding server, but then fails to connect to the VNC port because that is only accessible from without the tunnel (and yes, I want this. there is already VPN and layered security)

What is the expected correct behavior?

If I disable the SSH Tunnel, then remmina should not try to use an ssh tunnel, even if the server I connect to can be connected to via ssh. It should just respect my configuration settings.

If one wants this autoconfiguration to be happening below the hood, then the SSH Tunnel configuration section should contain a checkbox named autoconfiguration, which in my case I would uncheck.

If I connect via remmina -c vnc://host:port (i.e. without using a profile) everything works as desired btw.

Relevant logs and/or screenshots

This window can help you find connection problems.
You can stop and start the logging at any moment using the On/Off switch.
The stats button (Ctrl+T), can be useful to gather system info you may share when reporting a bug.
There is more info about debugging Remmina on https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging
(DEBUG) - (rcw_map_event) - Mapping: RemminaConnectionWindow
(DEBUG) - (remmina_protocol_widget_map_event) - Map plugin function not implemented
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Opening connection
(DEBUG) - (remmina_plugin_vnc_init) - Disable smooth scrolling is set to 0
(DEBUG) - (remmina_plugin_vnc_init) - Adding GDK_SMOOTH_SCROLL_MASK
(DEBUG) - (remmina_protocol_widget_open_connection_real) - Have SSH
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - SSH tunnel initialization…
(DEBUG) - (remmina_plugin_vnc_open_connection) - [2025-05-05T22:22:40.659797+02] - host - user - Connected to rmthost:5948 via VNC
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - Calling remmina_public_get_server_port (tunnel)
(DEBUG) - (remmina_protocol_widget_start_direct_tunnel) - server: rmthost, port: 5948
(DEBUG) - (remmina_plugin_vnc_rfb_output) - VNC returned: ConnectClientToTcpAddr6: connect
(DEBUG) - (remmina_plugin_vnc_rfb_output) - VNC returned: Unable to connect to VNC server
(DEBUG) - (remmina_plugin_vnc_main) - Client initialization failed
(DEBUG) - (remmina_plugin_vnc_main) - Client not authenticated
(DEBUG) - (remmina_plugin_vnc_main) - Client not connected with error: Unable to connect to VNC server

Local System Description

  • Client (OS name and version): nixos
  • Remmina version ( remmina --version ): 1.4.36 (git n/a)
  • Installation(s):
    • Distribution package.
    • PPA.
    • Snap.
    • Flatpak.
    • Compiled from sources.
    • Other - detail:
  • Desktop environment (GNOME, Unity, KDE, ..):
  • Plugin(s):
    • RDP - freerdp version ( xfreerdp --version ):
    • VNC
    • SSH
    • SFTP
    • SPICE
    • WWW
    • EXEC
    • Other (please specify):
  • GTK backend (Wayland, Xorg):

Contributions

In return, or to fix this issue, I'd be willing to:

  • Fix this myself.
  • Donate ___ and/or have donated ___ towards fixing it.
  • Take a donation of ___ to fix it.
  • Update the documentation.
  • Update the wiki.
  • Translate Remmina in my native language(s) (___) on Hosted Weblate.
Edited by Devvi the Lopper