SSH Access - Revision history

Prins089 at 11:12, 31 August 2026

2026-08-31T11:12:01Z

← Older revision		Revision as of 11:12, 31 August 2026
Line 21:		Line 21:
	</syntaxhighlight>		</syntaxhighlight>

	If the connection is refused, check your ~~firewall settings — SSH needs port 22 open~~.		If the connection is refused, check if your IP is (temporarily) banned from connecting: https://unban.anunna.wur.nl/unban

	=== Windows ===		=== Windows ===

Haars001 at 11:59, 14 July 2026

2026-07-14T11:59:51Z

← Older revision		Revision as of 11:59, 14 July 2026
Line 9:		Line 9:
	You are automatically redirected to a currently valid login server. An SSH client is built in on Linux and macOS; on Windows you usually install one, such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] or MobaXTerm.		You are automatically redirected to a currently valid login server. An SSH client is built in on Linux and macOS; on Windows you usually install one, such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] or MobaXTerm.

	Note that access may be restricted to certain IP ranges, and SSH may be blocked where port 22 is closed by a firewall. (For example, WUR FB-IT does not allow port 22 over WiFi to certain systems.)		Note that access may be restricted to certain IP ranges, and SSH may be blocked (see [[Unblocking your IP\|here]]) where port 22 is closed by a firewall. (For example, WUR FB-IT does not allow port 22 over WiFi to certain systems.)

	'''The login server is an access point only — it is not for CPU- or memory-intensive work.''' Anything beyond light, interactive use belongs in a job; see [[Login Nodes]] and [[Scheduler Overview (Slurm)]].		'''The login server is an access point only — it is not for CPU- or memory-intensive work.''' Anything beyond light, interactive use belongs in a job; see [[Login Nodes]] and [[Scheduler Overview (Slurm)]].
Line 38:		Line 38:

	== See also ==		== See also ==
			* [[Unblocking your IP]]
	* [[Login Nodes]]		* [[Login Nodes]]
	* [[Compute Nodes]]		* [[Compute Nodes]]

Haars001: Link Create shortcut log-in command from See also (orphan fix) (via update-page on MediaWiki MCP Server)

2026-06-19T20:35:29Z

Link Create shortcut log-in command from See also (orphan fix) (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 20:35, 19 June 2026
Line 41:		Line 41:
	* [[Compute Nodes]]		* [[Compute Nodes]]
	* [[Data Transfer Methods]]		* [[Data Transfer Methods]]
			* [[Create shortcut log-in command]] — SSH aliases and ~/.ssh/config shortcuts
	* [[ssh_without_password\|SSH without password]]		* [[ssh_without_password\|SSH without password]]
	* [[Scheduler Overview (Slurm)]]		* [[Scheduler Overview (Slurm)]]

Haars001: IA migration §2: polish — trim Windows/PuTTY walkthrough, move worker-node section to Compute Nodes, fix links (via update-page on MediaWiki MCP Server)

2026-06-18T12:20:06Z

IA migration §2: polish — trim Windows/PuTTY walkthrough, move worker-node section to Compute Nodes, fix links (via update-page on MediaWiki MCP Server)

Show changes

Haars001: Haars0011 moved page Log in to Anunna to SSH Access: IA migration §2: rename Log in to Anunna → SSH Access (leaving redirect) (via move-page on MediaWiki MCP Server)

2026-06-18T12:19:53Z

Haars0011 moved page Log in to Anunna to SSH Access: IA migration §2: rename Log in to Anunna → SSH Access (leaving redirect) (via move-page on MediaWiki MCP Server)

← Older revision	Revision as of 12:19, 18 June 2026
(No difference)

Honfi001: /* MobaXTerm on Windows */

2024-06-10T14:31:15Z

MobaXTerm on Windows

@@ Line 24: / Line 24: @@
 === MobaXTerm on Windows ===
 The program uses a full Cygwin stack, so commands from Mac and Linux can be used. Though MobaXTerm provides the Mobakeygen extension, which has an intuitive interface and is very convenient.
 ==== Generating an SSH key pair ====

Honfi001 at 12:49, 12 April 2024

2024-04-12T12:49:19Z

← Older revision		Revision as of 12:49, 12 April 2024
Line 27:		Line 27:
	==== Generating an SSH key pair ====		==== Generating an SSH key pair ====

	# From the ~~Menu~~ choose '''Tools''' > MobaKeygen SSH Key Generator		# From the main menu choose '''Tools''' > MobaKeygen SSH Key Generator
	# ~~click~~ on '''Generate''' and move your mouse to generate entropy		# Click on '''Generate''' and move your mouse to generate entropy
	# Type in a passphrase for the key		# Type in a passphrase for the key
	# Save keys with a meaningful name		# Save keys with a meaningful name

Honfi001 at 12:48, 12 April 2024

2024-04-12T12:48:03Z

← Older revision		Revision as of 12:48, 12 April 2024
Line 1:		Line 1:
	== Log on using ssh ==		== Log on using ssh ==
	One can log in to [[Anunna \| Anunna]] using ~~ssh~~ (default port tcp 22). The address of the login server is:		One can log in to [[Anunna \| Anunna]] using the '''S'''ecure '''Sh'''ell Protocol (SSH) (default port tcp 22). The address of the login server is:
	login.anunna.wur.nl		login.anunna.wur.nl

Line 18:		Line 18:
	ssh [user name]@login.anunna.wur.nl		ssh [user name]@login.anunna.wur.nl
	</pre>		</pre>

			----


			=== MobaXTerm on Windows ===
			The program uses a full Cygwin stack, so commands from Mac and Linux can be used. Though MobaXTerm provides the Mobakeygen extension, which has an intuitive interface and is very convenient.

			==== Generating an SSH key pair ====

			# From the Menu choose '''Tools''' > MobaKeygen SSH Key Generator
			# click on '''Generate''' and move your mouse to generate entropy
			# Type in a passphrase for the key
			# Save keys with a meaningful name

	=== PuTTY on Windows ===		=== PuTTY on Windows ===

Prins089: to

 to fix code blocks

2023-06-22T08:43:44Z

<source> to <pre> to fix code blocks

← Older revision		Revision as of 08:43, 22 June 2023
Line 15:		Line 15:
	A Command Line Interface ([http://en.wikipedia.org/wiki/Command-line_interface CLI]) ssh client is available from any Linux or MacOSX terminal. Secure shell (ssh) protocols require port 22 to be open. Should a connection be refused, the firewall settings of the system should be checked. Alternatively, local ICT regulations may prohibit the use of port 22. Wageningen UR FB-ICT for instance does not allow traffic through port 22 over WiFi to certain systems.		A Command Line Interface ([http://en.wikipedia.org/wiki/Command-line_interface CLI]) ssh client is available from any Linux or MacOSX terminal. Secure shell (ssh) protocols require port 22 to be open. Should a connection be refused, the firewall settings of the system should be checked. Alternatively, local ICT regulations may prohibit the use of port 22. Wageningen UR FB-ICT for instance does not allow traffic through port 22 over WiFi to certain systems.

	<~~source lang='bash'~~>		<pre>
	ssh [user name]@login.anunna.wur.nl		ssh [user name]@login.anunna.wur.nl
	</~~source~~>		</pre>

	=== PuTTY on Windows ===		=== PuTTY on Windows ===
Line 104:		Line 104:
	In a complete emergency, it is then possible to log on to any of the worker nodes via the login node. Logging on to the worker nodes does not require password authentication, you should therefore not be prompted to provide a password. This is not normally allowed - be aware that running tasks outside of SLURM is prohibited, but so far there has not been any serious abuse of this. This is provided to allow you to get a little more insight in what your job is doing.		In a complete emergency, it is then possible to log on to any of the worker nodes via the login node. Logging on to the worker nodes does not require password authentication, you should therefore not be prompted to provide a password. This is not normally allowed - be aware that running tasks outside of SLURM is prohibited, but so far there has not been any serious abuse of this. This is provided to allow you to get a little more insight in what your job is doing.

	<~~source lang='bash'~~>		<pre>
	ssh [user name]@[node name]		ssh [user name]@[node name]
	</~~source~~>		</pre>

	For instance:		For instance:

	<~~source lang='bash'~~>		<pre>
	ssh dummy001@node049		ssh dummy001@node049
	</~~source~~>		</pre>

	Again, it is not permitted to run jobs outside the scheduling software (slurm). So logging on to a worker node is for analyses of running jobs only.		Again, it is not permitted to run jobs outside the scheduling software (slurm). So logging on to a worker node is for analyses of running jobs only.

Haars001: /* See also */

2021-02-10T17:55:57Z

← Older revision		Revision as of 17:55, 10 February 2021
Line 121:		Line 121:
	* [[Using _Slurm \| Submit jobs with Slurm]]		* [[Using _Slurm \| Submit jobs with Slurm]]
	* [[ssh_without_password \| ssh without password]]		* [[ssh_without_password \| ssh without password]]
			* [[File_transfer \| File transfer options]]

	== External links ==		== External links ==
	* [http://en.wikipedia.org/wiki/Secure_Shell secure shell on Wikipedia]		* [http://en.wikipedia.org/wiki/Secure_Shell secure shell on Wikipedia]
	* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage]		* [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY homepage]