Accessing the Mill Cluster

Getting access to the Mill cluster as a member of the Missouri S&T faculty or student body is as simple as filling out the request form (https://missouri.qualtrics.com/jfe/form/SV_e5n4I8cvzo77jr8) and waiting for confirmation of account creation. After that you can connect using a traditional SSH client like Putty or MobaXterm (username@mill.mst.edu), or you can use the OpenOnDemand web interface (https://mill-ondemand-p1.itrss.mst.edu/) for shell and GUI access. 

Accessing With SSH From Windows 

While it is possible to use SSH through PowerShell, we recommend installing a dedicated SSH client like PuTTY or MobaXterm, both of which are available in AppsAnywhere. This is both because they have more features than the PowerShell implementation, and because we have more experience with these and will be able to provide better support to you if you use them. Each of these SSH clients has a different process for connecting to a remote host, but the information that is important for all of them is the host address: mill.mst.edu, the port: 22, and your username, which is the first part of your email address. If you have set up a vanity address for your email, you will need to use your original address. 

In MobaXterm, first click on the “Session” button in the top left corner with the screen icon. Then, the SSH button, which should be the first in the top row. You should see a form where you can set the remote host ( mill.mst.edu ) then check the box to specify your username (first part of your email) and the port should already be 22. Now click the OK button with the green check mark. You will be prompted for your password, which is the same as for other campus services like Outlook and OneDrive. In the future when you open MobaXterm these settings should be saved as a profile on the left side under “user sessions”. To reopen a connection to the mill, simply double-click the entry there. 

Accessing With SSH From Mac 

The Mac Terminal application supports SSH, so a basic SSH connection is simple. If you need to use a program with a GUI though, you will need to install and setup XQuartz to enable x-forwarding. With this in mind, and the usual poor performance of x-forwarding you may find it easier and better to use your GUI applications in a desktop session through OpenOnDemand. Check the knowledgebase for more information about that in the Basic Usage article. 

To connect with a basic SSH session from the Mac Terminal use the following command: 

ssh USERNAME@mill.mst.edu 

 -or- 

ssh –x USERNAME@mill.mst.edu 

You will then be prompted for your password, which will be your university password, the same one you use for any other university service. The characters you type in the password field will not be shown. 

NOTE: If you are off-campus you will need to be connected to the campus VPN (https://it.mst.edu/services/vpn/), or use previously set up public/private key authentication, or use OOD instead which is available anywhere. 

Accessing With SSH From Linux 

Unless something has gone very wrong, your terminal application supports SSH, so a basic SSH connection is simple. If you need to use a program with a GUI, you will need to enable x-forwarding for your session. Doing this is simple, you just need to add the -x flag to your SSH command before your username. X-forwarding performance is usually poor though, so you may still find it easier and better to use your GUI applications in a desktop session through OpenOnDemand. Check the knowledgebase for more information about that in the Basic Usage article. 

To connect with a basic SSH session from the Linux Terminal use the following command: 

ssh USERNAME@mill.mst.edu 

 -or- 

ssh –x USERNAME@mill.mst.edu  

You will then be prompted for your password, which will be your university password, the same as any other university service. The characters you type in the password field will not be shown. 

NOTE: If you are off-campus you will need to be connected to the campus VPN (https://it.mst.edu/services/vpn/), or use previously set up public/private key authentication, or use OOD instead which is available anywhere.