Remote Access Terminal - Revision history

Wikisailor: /* Remote Access */

2026-02-20T17:25:23Z

Remote Access

← Older revision		Revision as of 17:25, 20 February 2026
Line 6:		Line 6:
	==Remote Access==		==Remote Access==

	The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver#Installation of Wireguard \| Wireguard VPN]]''' on Vannila or '''[[VPNserver \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.		The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver#Installation of Wireguard \| Wireguard VPN]]''' on Vannila or '''[[VPNserver#Installation of OpenVPN \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.

	===Remote Access (RDP) to Windows 11 Desktops===		===Remote Access (RDP) to Windows 11 Desktops===

Wikisailor: /* Remote Access */

2026-02-20T17:24:03Z

Remote Access

← Older revision		Revision as of 17:24, 20 February 2026
Line 6:		Line 6:
	==Remote Access==		==Remote Access==

	The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver \| Wireguard VPN]]''' on Vannila or '''[[VPNserver \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.		The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver#Installation of Wireguard \| Wireguard VPN]]''' on Vannila or '''[[VPNserver \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.

	===Remote Access (RDP) to Windows 11 Desktops===		===Remote Access (RDP) to Windows 11 Desktops===

Wikisailor: /* Remote Access */

2026-02-20T17:23:08Z

Remote Access

← Older revision		Revision as of 17:23, 20 February 2026
Line 6:		Line 6:
	==Remote Access==		==Remote Access==

	The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver \| Wireguard VPN]]''' on Vannila or '''[[~~Remote Access Terminal~~ \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.		The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver \| Wireguard VPN]]''' on Vannila or '''[[VPNserver \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.

	===Remote Access (RDP) to Windows 11 Desktops===		===Remote Access (RDP) to Windows 11 Desktops===

Wikisailor: /* Remote Access */

2026-02-20T17:22:40Z

Remote Access

← Older revision		Revision as of 17:22, 20 February 2026
Line 6:		Line 6:
	==Remote Access==		==Remote Access==

	The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[~~Remote Access Terminal~~ \| Wireguard VPN]]''' on Vannila or '''[[Remote Access Terminal \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.		The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[VPNserver \| Wireguard VPN]]''' on Vannila or '''[[Remote Access Terminal \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.

	===Remote Access (RDP) to Windows 11 Desktops===		===Remote Access (RDP) to Windows 11 Desktops===

Wikisailor: /* Remote Access */

2026-02-20T17:20:30Z

Remote Access

← Older revision		Revision as of 17:20, 20 February 2026
Line 6:		Line 6:
	==Remote Access==		==Remote Access==

	The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both Wireguard VPN on Vannila or OpenVPN on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.		The sole reason for these VMs is to give access to a desktop machine from a remote location. As there are two different platforms with different strengths it seems reasonable that we will need different remote access protocols. RDP would seem the logical choice for the Windows 11 VMs but NoMachine seems like a solution better suited to Linux desktop VM/s. Both of these connection methods do offer some sort of security it will be assumed that the remote access will be over a VPN link. A major part of the reason is that Cloudflare will only proxy port 443 so any port other than that will have to be a DNS only on Cloudflare's control pannel. If we need to be DNS only we will need to have confidence in the remote access protocol in use and we know that while RDP has some encryption it has a few vulnerabilities, NoMachine is also supposed to have encription built in but it is not known how good it is. An easy method of being sure that we are communicating securely is to connect to a VPN and have all of the remote access go through that which makes everything easier in that we will have the laptop pre configured to connect to both '''[[Remote Access Terminal \| Wireguard VPN]]''' on Vannila or '''[[Remote Access Terminal \| OpenVPN]]''' on Voavanga and setup any other VPN clients as needed. As an added benefit to securing the remote access connections The VPN/s will allow other less secure protocols to be used like SMB or NFS and while it will not add much to security SSH / SCP operations are a bit simpler, we could even use FTP if we wanted to but there seems little point when SFTP is almost as easy.

	===Remote Access (RDP) to Windows 11 Desktops===		===Remote Access (RDP) to Windows 11 Desktops===

Wikisailor: /* Docker Installation with N8N & NPM */

2025-06-10T12:58:41Z

Docker Installation with N8N & NPM

← Older revision		Revision as of 12:58, 10 June 2025
Line 45:		Line 45:
	====[[Docker Installation with N8N & NPM]] ====		====[[Docker Installation with N8N & NPM]] ====

	Even though the GPU switch over has been delayed the Docker installation of N8N has been completed and to allow https access NPM has also been installed. Further details can be found '''[[Docker Installation with N8N & NPM \| here]]''';.		Even though the GPU switch over has been delayed the Docker installation of N8N has been completed and to allow https access NPM has also been installed. Further details can be found '''[[Docker Installation with N8N & NPM \| here]]'''.

	==== Jellyfin====		==== Jellyfin====

	As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos		As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos

Wikisailor: /* Docker Installation with N8N & NPM */

2025-06-10T12:58:04Z

Docker Installation with N8N & NPM

← Older revision		Revision as of 12:58, 10 June 2025
Line 45:		Line 45:
	====[[Docker Installation with N8N & NPM]] ====		====[[Docker Installation with N8N & NPM]] ====

	Even though the GPU switch over has been delayed the Docker installation of N8N has been completed and to allow https access NPM has also been installed. Further details can be found '''[[Docker Installation with N8N & NPM \| here]]'';.		Even though the GPU switch over has been delayed the Docker installation of N8N has been completed and to allow https access NPM has also been installed. Further details can be found '''[[Docker Installation with N8N & NPM \| here]]''';.

	==== Jellyfin====		==== Jellyfin====

	As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos		As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos

Wikisailor: /* Docker Installation with N8N & NPM */

2025-06-10T12:57:37Z

Docker Installation with N8N & NPM

← Older revision		Revision as of 12:57, 10 June 2025
Line 45:		Line 45:
	====[[Docker Installation with N8N & NPM]] ====		====[[Docker Installation with N8N & NPM]] ====

	Even though the GPU switch over has been delayed the installation of N8N has been completed and to allow https access NPM has also been installed		Even though the GPU switch over has been delayed the Docker installation of N8N has been completed and to allow https access NPM has also been installed. Further details can be found '''[[Docker Installation with N8N & NPM \| here]]'';.

	==== Jellyfin====		==== Jellyfin====

	As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos		As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos

Wikisailor: /* N8N & NPM Install */

2025-06-10T12:56:14Z

N8N & NPM Install

← Older revision		Revision as of 12:56, 10 June 2025
Line 43:		Line 43:
	The 5070 GP was tested to be passed through to '''[[Lychee]]''' and while the move from Walnut was quite straight forward the drivers that Nvidia released did not work that includes both the tested drivers an the beta drivers. more details of the process can be found '''[[GPU PCI Pass Through \| here]]'''.		The 5070 GP was tested to be passed through to '''[[Lychee]]''' and while the move from Walnut was quite straight forward the drivers that Nvidia released did not work that includes both the tested drivers an the beta drivers. more details of the process can be found '''[[GPU PCI Pass Through \| here]]'''.

	====N8N & NPM ~~Install~~====		====[[Docker Installation with N8N & NPM]] ====

	Even though the GPU switch over has been delayed the installation of N8N has been completed and to allow https access NPM has also been installed		Even though the GPU switch over has been delayed the installation of N8N has been completed and to allow https access NPM has also been installed

Wikisailor: /* N8N & NPM Install */

2025-06-10T12:55:52Z

N8N & NPM Install

← Older revision		Revision as of 12:55, 10 June 2025
Line 43:		Line 43:
	The 5070 GP was tested to be passed through to '''[[Lychee]]''' and while the move from Walnut was quite straight forward the drivers that Nvidia released did not work that includes both the tested drivers an the beta drivers. more details of the process can be found '''[[GPU PCI Pass Through \| here]]'''.		The 5070 GP was tested to be passed through to '''[[Lychee]]''' and while the move from Walnut was quite straight forward the drivers that Nvidia released did not work that includes both the tested drivers an the beta drivers. more details of the process can be found '''[[GPU PCI Pass Through \| here]]'''.

	====~~[[Docker Installation with~~ N8N & NPM]] ====		====N8N & NPM Install====

	Even though the GPU switch over has been delayed the ~~Docker~~ installation of N8N has been completed and to allow https access NPM has also been installed ~~further details can be found '''[[Docker Installation with N8N & NPM \| here]]'''~~		Even though the GPU switch over has been delayed the installation of N8N has been completed and to allow https access NPM has also been installed

	==== Jellyfin====		==== Jellyfin====

	As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos		As there are no useable drivers available the Jellyfin switch over to lychee has been delayed. However, The VM does have a 2TB hard drive added from PearPool to allow for storage of any videos