Remote Desktop - Revision history

Nipsy: Add fuse information for Hyper-V drive redirection to work correctly.

2026-07-23T08:19:14Z

Add fuse information for Hyper-V drive redirection to work correctly.

← Older revision		Revision as of 08:19, 23 July 2026
Line 272:		Line 272:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
			programs.fuse.enable = true;

	services = {		services = {
	xrdp = {		xrdp = {
Line 295:		Line 297:

	If in doubt, you can always run <code>ss --vsock -l</code>. If nothing shows up, then XRDP isn't listening where it should be and something about the above has changed.		If in doubt, you can always run <code>ss --vsock -l</code>. If nothing shows up, then XRDP isn't listening where it should be and something about the above has changed.

			Enabling fuse allows you to configure drive redirection in VMConnect and any drives selected will appear under <code>~/thinclient_drives</code> by default. Without enabling this programs option, you will receive a command not found error in <code>~/.local/share/xrdp/xrdp-chansrv.*.log</code> related to fusermount3.

	=== GNOME RDP ===		=== GNOME RDP ===

DHCP: add wikipedia links for VNC and RDP + minor style fixes.

2026-07-10T09:34:11Z

add wikipedia links for VNC and RDP + minor style fixes.

← Older revision		Revision as of 09:34, 10 July 2026
Line 6:		Line 6:
	== Server Protocols ==		== Server Protocols ==

	* VNC		* [[Wikipedia:VNC\|VNC]]
	* RDP		* [[Wikipedia:Remote Desktop Protocol\|RDP]]

	== Self hosting ==		== Self hosting ==
Line 31:		Line 31:
	To start a desktop session or window manager, one currently has to do this manually because servers still have hard-coded paths to <code>/usr/share/xsessions</code> to look for <code>.desktop</code> files. That means one has to write a script that starts the desktop session, window manager, or any other X application.		To start a desktop session or window manager, one currently has to do this manually because servers still have hard-coded paths to <code>/usr/share/xsessions</code> to look for <code>.desktop</code> files. That means one has to write a script that starts the desktop session, window manager, or any other X application.

	Some servers will automatically run <code>$HOME/.vnc/xstartup</code> but the more secure option is to write an executable script and run <code>vncserver -xstartup $pathToScript</code>		Some servers will automatically run <code>$HOME/.vnc/xstartup</code> but the more secure option is to write an executable script and run <code>vncserver -xstartup $pathToScript</code>.

	An example script:		An example script:
Line 42:		Line 42:
	</syntaxhighlight>		</syntaxhighlight>

	<code>pathToScript</code> can also be a path to an executable like <code>${pkgs.icewm}/bin/icewm</code>		<code>pathToScript</code> can also be a path to an executable like <code>${pkgs.icewm}/bin/icewm</code>.

	=== TigerVNC ===		=== TigerVNC ===
Line 60:		Line 60:
	The server is installed by adding the following line:<br/>		The server is installed by adding the following line:<br/>
	<code>services.x2goserver.enable = true;</code><br/>		<code>services.x2goserver.enable = true;</code><br/>
	to /etc/nixos/configuration.nix.		to <code>/etc/nixos/configuration.nix</code>.

	=== Guacamole ===		=== Guacamole ===

	==== Guacamole Server ====		==== Guacamole Server ====
	In nixos the guacamole server component is provided by [https://github.com/NixOS/nixpkgs/blob/nixos-24.05/nixos/modules/services/web-apps/guacamole-server.nix guacamole-server]		In nixos the guacamole server component is provided by [https://github.com/NixOS/nixpkgs/blob/nixos-24.05/nixos/modules/services/web-apps/guacamole-server.nix guacamole-server].

	A basic server setup service entry would look like this:		A basic server setup service entry would look like this:
Line 121:		Line 121:
	In nixos the guacamole client component is provided by the [https://github.com/NixOS/nixpkgs/blob/nixos-24.05/nixos/modules/services/web-apps/guacamole-client.nix guacamole-client] component.		In nixos the guacamole client component is provided by the [https://github.com/NixOS/nixpkgs/blob/nixos-24.05/nixos/modules/services/web-apps/guacamole-client.nix guacamole-client] component.

	This is the part of the service that provides the webportal for end users.		This is the part of the service that provides the webportal for end users.

	A basic client setup service entry would look like this:		A basic client setup service entry would look like this:
Line 140:		Line 140:
	See the [https://search.nixos.org/options?type=packages&query=services.guacamole-client search.nixos options] for other configuration options.		See the [https://search.nixos.org/options?type=packages&query=services.guacamole-client search.nixos options] for other configuration options.

	The webportal this provides is served by the tomcat server, and listens on port <code>8080</code> by default. The <code>settings.guacd-port</code> tells the client software how to communicate with the guacamole-server component.		The webportal this provides is served by the tomcat server, and listens on port <code>8080</code> by default. The <code>settings.guacd-port</code> tells the client software how to communicate with the guacamole-server component.

	The [https://guacamole.apache.org/doc/gug/configuring-guacamole.html#guacamole-properties upstream documentation] has the list of <code>guacamole.properties</code> options that can be provided for this setting.		The [https://guacamole.apache.org/doc/gug/configuring-guacamole.html#guacamole-properties upstream documentation] has the list of <code>guacamole.properties</code> options that can be provided for this setting.

	At this point if you are intending to serve the webportal directly, then the service can be reached at the url <code>http://<your-computer-ip:8080/guacamole</code>.		At this point if you are intending to serve the webportal directly, then the service can be reached at the url <code>http://<your-computer-ip:8080/guacamole</code>.

	==== Reverse Proxy ====		==== Reverse Proxy ====

DHCP: Style fixes and improvements

2026-07-10T09:25:07Z

Style fixes and improvements

Show changes

Nipsy: /* XRDP */

2026-05-05T23:44:31Z

XRDP

← Older revision		Revision as of 23:44, 5 May 2026
Line 290:		Line 290:
	</syntaxhighlight>		</syntaxhighlight>

	As documented in [https://github.com/nixos/nixpkgs/issues/304855 this issue], the current behavior of the XRDP module in NixOS is to provide the --port parameter on the CLI in the systemD unit file. It does print a message indicating it's ignoring anything provided in the configuration saying <code>--port parameter found, ini override</code> in journalctl.		As documented in [https://github.com/nixos/nixpkgs/issues/304855 this issue], the current behavior of the XRDP module in NixOS is to provide the <code>--port</code> parameter on the CLI in the systemD unit file. It does print a message indicating it's ignoring anything provided in the configuration saying <code>--port parameter found, ini override</code> in journalctl.

	If in doubt, you can always run <code>ss --vsock -l</code>. If nothing shows up, then XRDP isn't listening where it should be and something about the above has changed.		If in doubt, you can always run <code>ss --vsock -l</code>. If nothing shows up, then XRDP isn't listening where it should be and something about the above has changed.

Nipsy: /* XRDP */ document enhanced session mode under Hyper-V

2026-05-05T23:42:54Z

XRDP: document enhanced session mode under Hyper-V

@@ Line 265: / Line 265: @@
 networking.firewall.allowedTCPPorts = [ 3389 ];
 </syntaxhighlight>
 === GNOME RDP ===

Dangerflask: Add suggestion for x11vnc instead of TigerVNC as remote/server

2026-02-20T06:48:21Z

Add suggestion for x11vnc instead of TigerVNC as remote/server

← Older revision		Revision as of 06:48, 20 February 2026
Line 44:		Line 44:
	<code>pathToScript</code> can also be a path to an executable like <code>${pkgs.icewm}/bin/icewm</code>		<code>pathToScript</code> can also be a path to an executable like <code>${pkgs.icewm}/bin/icewm</code>

	=== ~~Tiger VNC~~ ===		=== TigerVNC ===

	Nixpkgs has a package but no service.		Nixpkgs has a package but no service.
Line 51:		Line 51:

	For an automated nixos config see [[TigerVNC]].		For an automated nixos config see [[TigerVNC]].

			However, you'll more likely have success running [https://search.nixos.org/packages?channel=unstable&query=x11vnc&show=x11vnc x11vnc] on the remote/far-away server, while only using `vncviewer` from the TigerVNC package from where you're sitting. Quality documentation for x11vnc usage is at its [https://github.com/LibVNC/x11vnc/?tab=readme-ov-file#readme official repository].

	=== x2go ===		=== x2go ===

Johanno at 23:13, 13 February 2026

2026-02-13T23:13:28Z

← Older revision		Revision as of 23:13, 13 February 2026
Line 49:		Line 49:
	The server component can be started using the <code>vncserver</code> command.		The server component can be started using the <code>vncserver</code> command.
	To connect, use the <code>vncviewer</code> command.		To connect, use the <code>vncviewer</code> command.

			For an automated nixos config see [[TigerVNC]].

	=== x2go ===		=== x2go ===

Sandro: Fix syntax highlighting

2026-01-22T23:01:24Z

Fix syntax highlighting

Show changes

Sandro: /* Self hosting */

2026-01-22T22:31:56Z

Self hosting

← Older revision		Revision as of 22:31, 22 January 2026
Line 10:		Line 10:

	== Self hosting ==		== Self hosting ==
	* [[RustDesk]] (nixpkgs: rustdesk-server)		* [[RustDesk]] available in nixpkgs as rustdesk-server

	== Clients ==		== Clients ==

Sandro: Remove wont fix issue

2026-01-22T22:31:31Z

Remove wont fix issue

← Older revision		Revision as of 22:31, 22 January 2026
Line 267:		Line 267:

	<code>services.meshcentral.enable = true;</code>		<code>services.meshcentral.enable = true;</code>

	~~However, the agent (client) is not available. ([https://github.com/NixOS/nixpkgs/issues/167527 Request])~~

	[[Category:Applications]]		[[Category:Applications]]
	[[Category:Desktop]]		[[Category:Desktop]]
	[[Category:Server]]		[[Category:Server]]