> For the complete documentation index, see [llms.txt](https://wiki.solids.group/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.solids.group/computing/server-access.md).

# Server Access

{% hint style="warning" %}
Most of this is old and no longer relevant.
{% endhint %}

Group servers are accessed using Secure Shell, usually called SSH.

You must be on the appropriate campus network or connected through VPN before you can access internal servers.

## Windows

1. Download and install PuTTY from [putty.org](http://www.putty.org/).
2. Open PuTTY.
3. Enter the server hostname, such as `servername.uccs.edu`.
4. When prompted, enter your username.
5. When prompted, enter your password.

You can also include the username in the hostname:

```
username@servername.uccs.edu
```

Linux systems do not display password characters while you type. This is normal.

## macOS or Linux

Open a terminal and run:

```bash
ssh servername.uccs.edu
```

or:

```bash
ssh username@servername.uccs.edu
```

When prompted, enter your password. The terminal will not display password characters while you type.

## Change Your Password

After logging in for the first time, change your password immediately:

```bash
passwd
```

Enter your current password, then enter your new password twice.

After this, set up public-key authentication using [SSH Public Keys](/computing/ssh-public-keys.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.solids.group/computing/server-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.