Skip to content
ArchForge
☰ Menu
Sign up
archadmin/archforge-external-statuspublic

Repository files, collaboration, releases and project activity.

◫ Insights
More
MilestonesCommitsWikiDiscussionsProjectsActivityCODEOWNERSArch LinuxInsights
archforge-external-status / GIT-DOMAIN-UPDATE-1.0.2.mdmain
↓ Download raw⑂ Commit Blame◷ File history
▤ GIT-DOMAIN-UPDATE-1.0.2.md1519 bytes

Quick start: install the domain + SSL wizard through ArchForge Git

  1. Extract FULL into your existing Git checkout on your laptop, keeping its .git directory. Or extract the UPDATE-FROM-1.0.1 ZIP directly over that checkout. Neither archive includes real secrets or a database.
  2. Commit and push the new files to your archforge-external-status repository on archforge.nl.
  3. On your second Debian 13 VPS, use the same checkout you used for the original installation:
cd ~/archforge-external-status
git pull --ff-only
sudo bash ./configure-domain.sh

Already signed in as root? Run bash ./configure-domain.sh instead of sudo.

Do not run ./install.sh or ./update.sh again just to link the domain. The new wizard configures the existing installation without changing the admin, database or secrets.

The wizard asks for your domain status.archforge.nl, the public IPv4 address of VPS 2, optional public IPv6, and optional ACME email. It requires correct DNS A/AAAA records before touching configuration. Ensure inbound TCP 80/443 are reachable at VPS 2 through your provider firewall and any active UFW. The wizard validates Caddy, reloads it and checks whether the trusted HTTPS certificate is really available. Caddy renews certificates automatically.

Verify afterwards:

curl -fsS https://status.archforge.nl/healthz
sudo journalctl -u caddy -n 80 --no-pager

See DOMAIN-SSL-DEBIAN-13.md for full details. No changes are made to archforge.nl itself.