Once your instance is Deployed, you can connect via SSH, set up VS Code Remote, and forward ports for services like Jupyter.Documentation Index
Fetch the complete documentation index at: https://runcrate.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
SSH Connection
The SSH command is available on your instance’s detail page. The general format is:Some instances use a non-standard SSH port. Always check the port shown in your instance details.
First Connection
On your first connection, you will be asked to confirm the server fingerprint:yes to continue. This is normal for new instances.
Verify GPU Access
After connecting, confirm that your GPU is available:Port Forwarding
To access services running on your instance from your local browser, use SSH port forwarding:Common Ports
| Service | Remote Port | Local Forward Command |
|---|---|---|
| Jupyter Notebook | 8888 | -L 8888:localhost:8888 |
| TensorBoard | 6006 | -L 6006:localhost:6006 |
| Gradio | 7860 | -L 7860:localhost:7860 |
| VS Code Server | 8080 | -L 8080:localhost:8080 |
http://localhost:8888 in your browser.
VS Code Remote SSH
VS Code can connect directly to your instance for a full IDE experience.Setup Steps
- Install the Remote - SSH extension in VS Code.
- Open the Command Palette (
Cmd+Shift+P/Ctrl+Shift+P). - Select Remote-SSH: Connect to Host….
- Enter the connection string:
root@<instance-ip> -p <port>. - When prompted, select the SSH key to use.
- VS Code will install its server component on the instance and connect.
SSH Config (Optional)
For quicker access, add your instance to~/.ssh/config:
ssh runcrate-instance or select runcrate-instance from VS Code.
File Transfer
Usescp to copy files to and from your instance:
Troubleshooting
Connection refused
Connection refused
- Verify the instance status is Deployed on the dashboard.
- Confirm you are using the correct IP address and port from the instance details.
- The instance may still be starting up — wait a minute and try again.
Permission denied (publickey)
Permission denied (publickey)
- Ensure your SSH key is added to your Runcrate account and was selected during deployment.
- Verify you are using the correct key file:
ssh -i ~/.ssh/correct_key ... - Check file permissions:
chmod 600 ~/.ssh/your_key
Connection timed out
Connection timed out
- Check your local network and firewall settings.
- Verify the instance IP and port on the dashboard.
- If the instance was recently deployed, wait 1-2 minutes for networking to initialize.