neptun: serve the vhosts that are actually in production
Probing the live Debian VPS turned up three mismatches between what it serves and what this config declares: - git.mgaction.town had no vhost at all. Gitea's web UI and HTTPS clones are public today; only its SSH side (the :2222 socat forward) had been ported, so a deploy would have taken the web side offline. - Audiobookshelf is served as abs.mgaction.town, not the longer audiobookshelf.mgaction.town this config used. The mobile app is configured with the short name. - The apex returns 200 from Caddy. Left unserved deliberately, so it now gets Caddy's default 404; noted in a comment so it doesn't look like an oversight next time. Gitea's ROOT_URL was http:// while Caddy terminates TLS for that name. Gitea builds absolute URLs from it, so clone buttons, redirects and webhooks were handing out downgraded links. Also record that defaultGateway6 is confirmed rather than assumed -- `ip -6 route show default` on the VPS gives "default via fe80::1 dev eth0 metric 1024 onlink". Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -22,7 +22,10 @@
|
||||
server = {
|
||||
DOMAIN = "git.mgaction.town";
|
||||
SSH_DOMAIN = "git.mgaction.town";
|
||||
ROOT_URL = "http://git.mgaction.town/";
|
||||
# https, not http: neptun's Caddy terminates TLS for this name. Gitea
|
||||
# builds its absolute URLs (clone buttons, redirects, webhooks) from
|
||||
# ROOT_URL, so an http:// value hands out downgraded links.
|
||||
ROOT_URL = "https://git.mgaction.town/";
|
||||
HTTP_PORT = 3000;
|
||||
START_SSH_SERVER = true;
|
||||
SSH_PORT = 2222;
|
||||
|
||||
Reference in New Issue
Block a user