Failed to start upterm - socket not found after maximum retries. Diagnostics: - Upterm data directory: /tmp/upterm-data - Expected socket directory: /tmp/upterm-data/runtime/upterm - Socket directory does not exist - Tmux sessions: No tmux sessions - Tmux error log: - Upterm command output: Error: error reading GitHub user keys: Get "https://github.com/ehelms.keys": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Usage: upterm host [flags] Examples: # Host a terminal session running $SHELL, attaching client's IO to the host's: upterm host # Accept client connections automatically without prompts: upterm host --accept # Host a terminal session allowing only specified public key(s) to connect: upterm host --authorized-keys PATH_TO_AUTHORIZED_KEY_FILE # Host a session executing a custom command: upterm host -- docker run --rm -ti ubuntu bash # Host a 'tmux new -t pair-programming' session, forcing clients to join with 'tmux attach -t pair-programming': upterm host --force-command 'tmux attach -t pair-programming' -- tmux new -t pair-programming # Use a different Uptermd server, hosting a session via WebSocket: upterm host --server wss://YOUR_UPTERMD_SERVER -- YOUR_COMMAND Flags: --accept Automatically accept client connections without prompts. --authorized-keys string Specify a authorize_keys file listing authorized public keys for connection. --codeberg-user strings Authorize specified Codeberg users by allowing their public keys to connect. -f, --force-command string Enforce a specified command for clients to join, and link the command's input/output to the client's terminal. --github-user strings Authorize specified GitHub users by allowing their public keys to connect. Configure GitHub CLI environment variables as needed; see https://cli.github.com/manual/gh_help_environment for details. --gitlab-user strings Authorize specified GitLab users by allowing their public keys to connect. -h, --help help for host --hide-client-ip Hide client IP addresses from output (auto-enabled in CI environments). --known-hosts string Specify a file containing known keys for remote hosts (required). (default "/home/runner/.ssh/known_hosts") --no-sftp Disable file transfer via SFTP/SCP. By default, clients can transfer files with the same access as the terminal session. -i, --private-key strings Specify private key files for public key authentication with the upterm server (required). (default [/home/runner/.ssh/id_ed25519,/home/runner/.ssh/id_rsa]) -r, --read-only Host a read-only session, preventing client interaction. Also restricts SFTP to download-only. --server string Specify the upterm server address (required). Supported protocols: ssh, ws, wss. (default "ssh://uptermd.upterm.dev:22") --skip-host-key-check Automatically accept unknown server host keys and add them to known_hosts (similar to SSH's StrictHostKeyChecking=accept-new). This bypasses host key verification for new connections. --srht-user strings Authorize specified SourceHut users by allowing their public keys to connect. Global Flags: --debug enable debug level logging (log file: /tmp/upterm-data/state/upterm/upterm.log). 2026/04/30 14:00:40 ERROR Error executing command error="error reading GitHub user keys: Get \"https://github.com/ehelms.keys\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" - Upterm binary check: Upterm version 0.22.0 Git commit: 1d809fde337afd99c149978ee08b37b16fe11a6f Build date: 2026-01-14T05:11:39Z - XDG_RUNTIME_DIR (passed to upterm): /tmp/upterm-data/runtime - XDG_RUNTIME_DIR (actual directory): /tmp/upterm-data/runtime - USER: runner - UID: 1001 - Platform: linux === Troubleshooting Steps === 1. Check tmux and upterm are installed and in PATH 2. Verify upterm-server setting is correct 3. Check network connectivity to upterm server 4. Review

Process completed with exit code 1.

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: owenthereal/action-upterm@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/