Personal Globus Endpoint

Note: after the system upgrade of June-July 2018, some of the globus endpoints or data-transfer nodes (DTN) which are named in this documentation will no longer be in service. Please check back for updated information once the new filesystems are in use.  

The easiest and most convenient way to send and receive files on your personal machine is to create a personal Globus endpoint there, so that you can transfer directly to other Globus endpoints (typically endpoints on a Globus server like the NeSI cluster). In order to do this, install Globus ConnectPersonal.

This can be done via the web interface or the command-line.

Globus connectpersonal installation 

Using Browser Instructions at If you have problems with this installation, the command-line installation is recommended.

Using Command-line

Status of Globus personal endpoint connection

Once the installation is complete, you should see a notification you are now connected to Globus (green light).


An alternative confirmation that you are connected can be found at the shell, by verifying that you have an open ssh session connected to globus:

$ ps -aef | grep ssh |grep globus abcd123@username~/globus/connect_personal/png$ ps -aef|grep ssh | grep globus abcd123 12881 12880 0 16:37 pts/8 00:00:00 ssh -F /dev/null -o CheckHostIP no -o ServerAliveInterval 15 -o ServerAliveCountMax 8 -o StrictHostKeyChecking yes -o UserKnownHostsFile "/home/abcd123/.globusonline/lta/relay-known-hosts.txt" -T -l x_relay2 -i /home/abcd123/.globusonline/lta/relay-anonymous-key.pem -R 0: -p 2223

If you are connected, you will see something like the above (response indented for readablilty). Notice that an open Globus Connect Personal connection is an ssh connection to

If you close this connection, select Connect on the icon to reconnect:


or if the icon has been closed (by a reboot), open it again by running (from the directory where the globusconnect script  lives) the command

$ ./globusconnect &

Using your Globus personal endpoint

When your personal endpoint is registered against your globus ID, that endpoint is available to you as a source or destination for file-transfer, and its label appears in the endpoint list you are prompted with:

With an open connection to Globus Connect Personal (green light on the above icon):


select your personal endpoint and you will see your home-directory there
select a nesi# endpoint that you have access to and you will see your home-directory on that cluster.
adjust paths as necessary
Now Globus can move files between these two endpoints.

Was this article helpful?
0 out of 0 found this helpful