vncconnect(1)

πŸ“¦ version 3.3.1, in nixos 26.05, nixpkgs unstable

πŸ’… vncconnect(1) β€” the TurboVNC reverse-connection bestie πŸ’…

okay so this is vncconnect, part of the TurboVNC squad, and honestly? it's giving "tiny tool, huge main character energy." let's get into it 🫢


✨ NAME ✨

vncconnect β€” connect a TurboVNC session to a listening VNC viewer. that's it, that's the vibe πŸ’–


🌸 SYNOPSIS 🌸

vncconnect [-display VNC-display] [-disconnect] client[:port]

πŸ¦‹ DESCRIPTION πŸ¦‹

bestie. listen. vncconnect is the little icon that initiates a "reverse connection" between a TurboVNC session and a VNC viewer that's been started up in "listen mode." πŸ”₯

so the viewer? it should be running on the machine specified by client, and it should be listening on the port specified by port. and if you don't specify port? no stress, the default of 5500 is used. slay, defaults. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -display VNC-display β€” the X display of the TurboVNC session you wanna connect to a listening viewer. if you don't say anything, it just reads from the DISPLAY environment variable (default behavior, lowkey iconic).
  • -disconnect β€” yeets all listening viewers off a particular TurboVNC session. disconnect era πŸ’…

πŸ’€ EXIT CODES πŸ’€

okay this part actually matters so pay attention, no cap πŸ‘€

when you're using it to initiate a reverse connection, vncconnect will exit with status 0 if the connection was successful. it'll exit with status 1 if the connection failed β€” and fr fr, that happens if:

  • there was no listening viewer running on the specified client and port
  • a firewall prevented the connection
  • reverse connections had been disallowed in the TurboVNC Server's security configuration file 😭

when you're using it to disconnect reverse connections, vncconnect will exit with status 0 if one or more listening viewers were successfully disconnected. otherwise? status 1. that's the whole mood. πŸ“


🌈 SEE ALSO 🌈

go read those too, iykyk πŸ’œ


πŸ‘‘ AUTHORS πŸ‘‘

VNC was originally developed at AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. TurboVNC, based on TightVNC, is provided by The VirtualGL Project. many other people participated in development, testing and support β€” absolute legends, every single one 🫢

Man page authors:

  • Tim Waugh <twaugh@redhat.com>
  • Constantin Kaplinsky <const@tightvnc.com>
  • D. R. Commander <information@turbovnc.org>

and that's the whole page babes ✨ this one's from TurboVNC, dated October 2018 β€” shoutout to the vncconnect(1) girlies, we stay reverse-connecting πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from
  • nixos 26.05: turbovnc 3.3
  • nixpkgs unstable: turbovnc 3.3.1
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms