Skip to content

FastX

FastX (by StarNet) is a remote graphical interface tool used to connect to and interact with remote Linux systems graphically. A key benefit of FastX is session persistence: you can disconnect from an active session without closing your running programs, allowing you to pick up right where you left off from a different location or device. For more details, visit the StarNet FastX Website.

There are two main ways to connect to CHPC services via FastX: through the web interface and through the dedicated desktop application.

On this page

The table of contents requires JavaScript to load.

CHPC FastX Usage Policy

To ensure stable performance and fair access for everyone, please adhere to the following policies and connection guidelines when using FastX.

Resource Selection & Policies
  • Default to Frisco: Users should default to using the CHPC login nodes or dedicated frisco nodes (frisco1 through frisco8) for FastX sessions.

  • Interactive Node Rules: All standard CHPC interactive node usage policies apply (see Policy 2.1.1). If you are unsure whether your workflow's resource requirements exceed what a shared interactive node should handle, route your session to a frisco node or a private owner interactive node instead.

  • Custom Installations: If your research requires FastX on a specific CHPC-supported system where it isn't currently available, please contact the CHPC team at helpdesk@chpc.utah.edu

CHPC may establish additional guidelines or update these usage policies over time to adapt to evolving user needs and cluster resource demands.

Using the FastX Web Client

Starting a Session

1. Open up to the FastX dashboard in a web browser by visiting the link below and replacing 'servername' with one of the CHPC servers, (e.g., kingspeak, notchpeak).

https://servername.chpc.utah.edu:3300  

2. Sign in using your University of Utah uNID and password and authenticate with DUO.

3. To start a new session, click on any application located on the left hand side of the screen and click on the play button that appears 

Note: Edits to the window dimension and session name can be made by clicking on the application and then the pencil icon in the bottom right corner of the application. Depending on the application you select, you may be directed solely to a terminal or to a virtual desktop.

Reconnecting to an Active Session

If you left a session running or got disconnected:

  1. Log back in to the exact same server you used originally.
  2. Find your existing session in the dashboard.

  3. Click on the session and hit the play button to open it in a new browser tab.

Keeping a Session Alive

To close your browser window while leaving your applications running in the background:

  1. Navigate back to the dashboard.

  2. Select the session you want to leave running.

  3. Open the pulldown menu next to the x icon and choose Disconnect.

Closing a Session Permanently

When you are completely finished working and want to free up server resources:

  1. Select the active session in your dashboard.

  2. Open the pulldown menu next to the x icon and choose Terminate.

 

Using the FastX Desktop Client

If you prefer using the desktop application rather than a web browser, follow StarNets user guide to set up connections, launch sessions, and manage your work using either FastX 4 or FastX 3 (both versions have the same user guide).

Installing FastX Desktop Client

On the FastX web client, there is an Announcements section. At the bottom there will be two links - the 'Desktop Clients' link will take you to see the download links for the Mac, Linux, and Windows operating systems. Download and install the appropriate client.

How to connect to a CHPC server

When you launch the FastX desktop client, two windows will appear: a FastX Window and inside it a Connections Window.

In the Connections window, click the + icon in the upper right corner to define a new server.

Fill out the connection details:

    • Host: Enter a node address (e.g., frisco.chpc.utah.edu or notchpeak.chpc.utah.edu).

    • User: Your University of Utah uNID.

    • Port: Leave it as 22.

    • Name: A label for the connection (e.g., frisco)

 

FastX Troubleshooting

The most common issue we see are connection errors related to storage quotas in the home directory. Because FastX writes to your home directory, being over quota will prevent you from logging into FastX. If you receive a connection error, connect via regular ssh and check your home directory usage with `mychpc batch --storage`. If you are over quota, please clean it up and you will be able to connect via FastX again.

If you have any other issues with FastX, please contact User Services at helpdesk@chpc.utah.edu.

Last Updated: 8/26/26