Fix GITEA_DOMAIN value — was set with an https:// scheme prefix

git_pull_execute.sh, varaverk.plg, and gitea_ssh_setup.sh all treat
GITEA_DOMAIN as a bare hostname (gitea_ssh_setup.sh even builds its own
https:// API URL from it). The live value on HOST1 had the scheme
included, which would build a malformed SSH URL
(ssh://git@https://git.gmer4lfe.com:221/...) — hadn't been hit yet since
HOST2's install succeeded via Tailscale peer detection before ever
reaching this fallback tier.
This commit is contained in:
Gmer4Lfe
2026-07-04 23:10:05 -04:00
parent a6fe820a61
commit 223d5ebfc9
+1 -1
View File
@@ -274,7 +274,7 @@
# Falls back to GITEA_DOMAIN if local and Tailscale both fail. # Falls back to GITEA_DOMAIN if local and Tailscale both fail.
GITEA_CONTAINER="Gitea" GITEA_CONTAINER="Gitea"
GITEA_REPO_PATH="FailedProxy/Varaverk.git" GITEA_REPO_PATH="FailedProxy/Varaverk.git"
GITEA_DOMAIN="" # e.g. git.yourdomain.com — requires NPM + DNS GITEA_DOMAIN="git.gmer4lfe.com" # e.g. git.yourdomain.com — requires NPM + DNS
TARGET_DIR="/boot/config/plugins/varaverk" TARGET_DIR="/boot/config/plugins/varaverk"
GITEA_SSH_KEY="/root/.ssh/unraid_gitea" GITEA_SSH_KEY="/root/.ssh/unraid_gitea"
SSH_PORT=221 # Gitea SSH port (default 22, Gitea often uses 221/222) SSH_PORT=221 # Gitea SSH port (default 22, Gitea often uses 221/222)