intern/diary
intern/diary
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CI Failure: Missing deployment secrets (DEPLOY_HOST) #1

New issue
Closed
opened 2026-02-16 21:52:46 -08:00 by ci · 0 comments
ci commented 2026-02-16 21:52:46 -08:00
Copy link

CI Failure Report

Workflow: Build and Deploy
Commit: 1bdfe43fd4
Run: https://git.brads.house/intern/diary/actions/runs/1

Root Cause Analysis

The workflow build-hugo.yml failed at step Deploy to server via SSH.

Error Details

usage: ssh-keyscan [-46cDHv] [-f file] [-p port] [-T timeout] [-t type]
           [host | addrlist namelist]
[runner]: exitcode '1': failure

Investigation

  1. Hugo build: Succeeded (v0.147.0, 12 pages built in 18ms)
  2. Deploy to pages branch: Succeeded (pushed to pages branch)
  3. Deploy to server via SSH: Failed

The error message is from ssh-keyscan being called without a host argument. This occurs when the secret DEPLOY_HOST is empty or not configured in the repository secrets.

Required Secrets

The workflow expects these secrets to be configured:

  • DEPLOY_HOST - SSH target hostname (MISSING - causes failure)
  • DEPLOY_SSH_KEY - Private SSH key for deployment
  • DEPLOY_USER - SSH username for deployment
  • DEPLOY_PATH - Target directory on server
  • FORGEJO_TOKEN - Already configured (used successfully in previous step)

Impact

  • The Hugo site is built and pushed to the pages branch successfully
  • The deployment to the production server via SSH fails
  • Site content is available in the pages branch but not deployed

Recommendation: @brad Add the missing repository secrets: DEPLOY_HOST, DEPLOY_SSH_KEY, DEPLOY_USER, and DEPLOY_PATH to complete the SSH deployment workflow.

## CI Failure Report **Workflow:** Build and Deploy **Commit:** 1bdfe43fd4d93a808f37558243f1a74556d2f60a **Run:** https://git.brads.house/intern/diary/actions/runs/1 ## Root Cause Analysis The workflow `build-hugo.yml` failed at step **Deploy to server via SSH**. ### Error Details ``` usage: ssh-keyscan [-46cDHv] [-f file] [-p port] [-T timeout] [-t type] [host | addrlist namelist] [runner]: exitcode '1': failure ``` ### Investigation 1. **Hugo build**: Succeeded (v0.147.0, 12 pages built in 18ms) 2. **Deploy to pages branch**: Succeeded (pushed to pages branch) 3. **Deploy to server via SSH**: Failed The error message is from `ssh-keyscan` being called without a host argument. This occurs when the secret `DEPLOY_HOST` is empty or not configured in the repository secrets. ### Required Secrets The workflow expects these secrets to be configured: - `DEPLOY_HOST` - SSH target hostname (MISSING - causes failure) - `DEPLOY_SSH_KEY` - Private SSH key for deployment - `DEPLOY_USER` - SSH username for deployment - `DEPLOY_PATH` - Target directory on server - `FORGEJO_TOKEN` - Already configured (used successfully in previous step) ### Impact - The Hugo site is built and pushed to the `pages` branch successfully - The deployment to the production server via SSH fails - Site content is available in the `pages` branch but not deployed **Recommendation:** @brad Add the missing repository secrets: `DEPLOY_HOST`, `DEPLOY_SSH_KEY`, `DEPLOY_USER`, and `DEPLOY_PATH` to complete the SSH deployment workflow.
brad closed this issue 2026-02-16 21:55:30 -08:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
pages
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
intern/diary#1
No description provided.