Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some valid server addresses are not accepted when using -via #1815

Closed
LMattsson opened this issue Aug 20, 2024 · 1 comment
Closed

Some valid server addresses are not accepted when using -via #1815

LMattsson opened this issue Aug 20, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@LMattsson
Copy link
Contributor

Describe the bug
When doing a regular login (i.e. not using -via), the following server addresses are allowed in the VNC server input field:

<host>:<port>
<host>::<port>
<host>:<display>

When using -via with <host>::<port> or <host>:<display>, I can log in without any issues. However, using -via with <host>:<port> is not possible and the error message below is shown:

The connection was dropped by the server before the session could be established.

Attempt to reconnect?

To Reproduce
Steps to reproduce the behavior:

  1. Run vncviewer -via <host>
  2. Input e.g. localhost:5902 in the VNC server field (only one colon)
  3. Click connect
  4. Enter the password for SSH in the terminal
  5. Instead of logging in to TigerVNC, the error message above is shown.

Expected behavior
The same server address should work for login regardless if -via is used or not.

Client (please complete the following information):

  • OS: Fedora 39
  • VNC client: TigerVNC
  • VNC client version: 1.13.1
  • Client downloaded from: my Linux distribution

Server (please complete the following information):

  • OS: RHEL 9
  • VNC server: TigerVNC
  • VNC server version: 1.13.1
  • Server downloaded from: my Linux distribution
  • Server was started using: systemctl start vncserver@:2.service
@LMattsson LMattsson added the bug Something isn't working label Aug 20, 2024
@CendioOssman
Copy link
Member

Fixed in e6d4d3c.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants