GESD32 Technology Department • Verified Troubleshooting Workflow

GitHub and Hostinger publishing guide with progress tracking.

A modern operational guide showing the problems discovered during the Vegeta Docs deployment, the root causes, and the verified fixes that made GitHub pushes and Hostinger publishing work.

Open full guide

Troubleshooting Progress

0 of 0 complete

0Diagnosis complete

0Fixes complete

0Security complete

Verified Working

Final working state is confirmed.

GitHub SSH authentication works, changes push to `main`, Hostinger builds with `npm run build`, and public output is generated in `dist/` while `internal/` remains excluded.

Executive Summary

What failed, what was verified, and what fixed the deployment.

SUMMARY

Final outcome

Hostinger initially rejected the repository.Error: Unsupported framework or invalid project structure. GitHub push initially failed over HTTPS.The server had no interactive HTTPS credentials available. Both issues were resolved.Added a static Node build structure and switched GitHub authentication to SSH.

Hostinger Invalid Project Structure

The repository needed a recognizable deployable structure.

HOSTINGER

Problem found

Hostinger error captured.Unsupported framework or invalid project structure. Check files and supported frameworks. Repository was a bare static site.It had index.html, README.md, docs, public, internal, and assets. Missing project manifest was identified.No package.json, no build script, and no standard output directory existed.

Fix applied

Added package.json.Defined project metadata, Node version, build command, and start command. Added static build script.scripts/build-static.js creates dist and copies public-safe paths. Added local preview script.scripts/serve-static.js serves the built dist folder locally.

Static Build Structure That Worked

These files and Hostinger settings made the deployment valid.

BUILD

Working build configuration

Build command verified.npm run build Output directory verified.dist Public-safe paths only.index.html, docs, public, and assets are copied into dist. Internal path excluded.Excluded path: internal/

Hostinger settings

Repository selected.vegetagesd32/vegeta-docs Branch selected.main Build command set.npm run build Publish/output directory set.dist Node version requirement met.Node 18 or newer.

GitHub HTTPS Push Failure

The local environment could commit but could not push over HTTPS.

GITHUB

Problems verified

HTTPS push failed.fatal: could not read Username for 'https://github.com': No such device or address GitHub CLI missing.gh: command not found GitHub token missing.GITHUB_TOKEN_NOT_SET Git credential store missing.GIT_CREDENTIALS_MISSING

Root cause

The repository remote used HTTPS, but the Hermes/Vegeta environment had no GitHub HTTPS credentials, no stored token, no credential helper, and no GitHub CLI authentication.

SSH Authentication Fix

SSH was the cleanest persistent authentication path for this environment.

SSH

Commands that worked

Generate dedicated SSH key.

mkdir -p ~/.ssh
chmod 700 ~/.ssh
ssh-keygen -t ed25519 -C "email@domain.com" -f ~/.ssh/id_ed25519 -N ""
chmod 600 ~/.ssh/id_ed25519
chmod 644 ~/.ssh/id_ed25519.pub

Add public key to GitHub.GitHub → Settings → SSH and GPG keys → New SSH key → Authentication Key. Title used: Hermes Vegeta GESD32. Switch remote to SSH.git remote set-url origin git@github.com:vegetagesd32/vegeta-docs.git Verify GitHub SSH authentication.ssh -o StrictHostKeyChecking=accept-new -T git@github.com Push to GitHub.git push origin main

Problem and Fix Matrix

Operational record of each problem, cause, and corrective action.

RCA

Hostinger project error

Cause: no project manifest/build command. Fix: package.json + build-static.js + dist output.

HTTPS push failure

Cause: no HTTPS credentials in non-interactive environment. Fix: SSH authentication.

Missing gh CLI

Cause: gh not installed. Fix: use pure git and SSH; no gh required.

Internal docs exposure risk

Cause: repository contains internal/ path. Fix: build script excludes internal/.

Repeatable Procedure

Use this process for future documentation repositories published through Hostinger.

PLAYBOOK

Future deployment checklist

Check repository state.

git status --short
git remote -v
git log --oneline -3

Verify or add static build support.package.json, scripts/build-static.js, scripts/serve-static.js Run build locally.npm run build Verify restricted paths are excluded.Do not publish internal/ unless the Technology Director approves and access controls are verified. Commit and push.

git add .
git commit -m "build: add Hostinger-compatible static site scripts"
git push origin main
git ls-remote origin main

Verification Checklist

Do not mark the workflow complete until these are verified.

VERIFY

Acceptance checks

Build succeeds.npm run build dist folder is generated. internal/ is excluded. GitHub SSH authentication succeeds.ssh -T git@github.com Remote main points to expected commit.git ls-remote origin main Hostinger site loads successfully.