Remote Desktop - Revision history

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]]

Sandro: Remove default setting for gnome

2026-01-22T22:27:31Z

Remove default setting for gnome

← Older revision		Revision as of 22:27, 22 January 2026
Line 254:		Line 254:
	To fix this we need to enable and start the systemd unit at boot using <code>wantedBy = [ "graphical.target" ];</code> as shown below:		To fix this we need to enable and start the systemd unit at boot using <code>wantedBy = [ "graphical.target" ];</code> as shown below:

	<syntaxhighlight lang="nix">services.gnome.gnome-remote-desktop.enable = true; ~~# 'true' does not make the unit start automatically at boot~~		<syntaxhighlight lang="nix">services.gnome.gnome-remote-desktop.enable = true;
	systemd.services.gnome-remote-desktop = {		systemd.services.gnome-remote-desktop = {
	wantedBy = [ "graphical.target" ]; # for starting the unit automatically at boot		wantedBy = [ "graphical.target" ]; # for starting the unit automatically at boot
	};		};
	services.displayManager.autoLogin.enable = false;		services.displayManager.autoLogin.enable = false;
	~~services.getty.autologinUser = null;~~
	networking.firewall.allowedTCPPorts = [ 3389 ];</syntaxhighlight>		networking.firewall.allowedTCPPorts = [ 3389 ];</syntaxhighlight>

Fschn90: tiny fix of syntax in nginx reverse proxy config

2025-09-30T08:11:41Z

tiny fix of syntax in nginx reverse proxy config

← Older revision		Revision as of 08:11, 30 September 2025
Line 140:		Line 140:

	services.nginx = {		services.nginx = {
	enable = true;		<nowiki> </nowiki> enable = true;
	upstreams."guacamole_server" = {		<nowiki> </nowiki> upstreams."guacamole_server" = {
	extraConfig = ''		<nowiki> </nowiki> extraConfig = <nowiki>''</nowiki>
	keepalive 4;		<nowiki> </nowiki> keepalive 4;
	'';		<nowiki> </nowiki> <nowiki>''</nowiki>'';
	servers = {		<nowiki> </nowiki> servers = {
	"127.0.0.1:8080" = {};		<nowiki> </nowiki> "127.0.0.1:8080" = {};
	};		<nowiki> </nowiki> };
	};		<nowiki> </nowiki> };
	virtualHosts."remote.mydomain.net" = {		<nowiki> </nowiki> virtualHosts."remote.mydomain.net" = {
	forceSSL = true; # redirect http to https		<nowiki> </nowiki> forceSSL = true; # redirect http to https
	enableACME = true;		<nowiki> </nowiki> enableACME = true;
	locations."/" = {		<nowiki> </nowiki> locations."/" = {
	extraConfig = ''		<nowiki> </nowiki> extraConfig = <nowiki>''</nowiki>
	proxy_buffering off;		<nowiki> </nowiki> proxy_buffering off;
	proxy_set_header Upgrade $http_upgrade;		<nowiki> </nowiki> proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection $http_connection;		<nowiki> </nowiki> proxy_set_header Connection $http_connection;
	proxy_set_header X-Real-IP $remote_addr;		<nowiki> </nowiki> proxy_set_header X-Real-IP $remote_addr;
	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;		<nowiki> </nowiki> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	proxy_set_header Host $host;		<nowiki> </nowiki> proxy_set_header Host $host;
	proxy_set_header X-NginX-Proxy true;		<nowiki> </nowiki> proxy_set_header X-NginX-Proxy true;
	proxy_pass http://guacamole_server/guacamole$request_uri;		<nowiki> </nowiki> proxy_pass http://guacamole_server/guacamole$request_uri;
	proxy_redirect http://guacamole_server/ https://$server_name/;		proxy_redirect http://guacamole_server/ https://$server_name/;
	'';		<nowiki> </nowiki> <nowiki>''</nowiki>'';
	};		};
	};		};

Crazivik at 09:30, 11 August 2025

2025-08-11T09:30:31Z

← Older revision		Revision as of 09:30, 11 August 2025
Line 254:		Line 254:
	To fix this we need to enable and start the systemd unit at boot using <code>wantedBy = [ "graphical.target" ];</code> as shown below:		To fix this we need to enable and start the systemd unit at boot using <code>wantedBy = [ "graphical.target" ];</code> as shown below:

	<syntaxhighlight lang="nix">services.gnome.gnome-remote-desktop.enable = true; # 'true' does not make the unit start ~~by default~~ at boot		<syntaxhighlight lang="nix">services.gnome.gnome-remote-desktop.enable = true; # 'true' does not make the unit start automatically at boot
	systemd.services.gnome-remote-desktop = {		systemd.services.gnome-remote-desktop = {
	wantedBy = [ "graphical.target" ]; # for starting the unit ~~by default~~ at boot		wantedBy = [ "graphical.target" ]; # for starting the unit automatically at boot
	};		};
	services.displayManager.autoLogin.enable = false;		services.displayManager.autoLogin.enable = false;