build fix 12

.gitea/workflows/build-and-deploy.yml

@@ -14,7 +14,7 @@ env:
   # TODO: Remove after installing internal CA certificate on the runner
   GIT_SSL_NO_VERIFY: "true"
   REGISTRY_HOST: 192.168.3.80
-  DEPLOY_REGISTRY_HOST: 10.0.0.4:5000
+  DEPLOY_REGISTRY_HOST: 192.168.3.80
   DEPLOY_SSH_HOST: 10.0.0.1
   DOCKERFILE_PATH: Dockerfile.production
   DOCKER_PLATFORM: linux/amd64

docs/DOCKER.md

@@ -407,7 +407,16 @@ Expected response:
 HTTP/1.1 401 Unauthorized
 ```
 
-When CI builds on the VPS and pushes directly to the local registry, `DEPLOY_REGISTRY_HOST` in `.gitea/workflows/build-and-deploy.yml` must include the registry port, for example `10.0.0.4:5000`. Because the local registry is plain HTTP, configure the VPS Docker daemon once:
+If CI uses the Gitea container registry, `REGISTRY_HOST` and `DEPLOY_REGISTRY_HOST` in `.gitea/workflows/build-and-deploy.yml` should point at the Gitea registry host, for example `192.168.3.80`. From the VPS build host, verify Docker can reach it:
+
+```bash
+curl -vk https://192.168.3.80/v2/
+docker login 192.168.3.80
+```
+
+If `curl` times out, fix network routing or firewall access from the VPS to the Gitea server before rerunning CI. If Docker reports a certificate error, install the Gitea registry CA certificate on the VPS Docker host or configure Docker for that internal registry according to your environment.
+
+When CI builds on the VPS and pushes directly to a separate plain-HTTP local registry instead of Gitea, `DEPLOY_REGISTRY_HOST` must include the registry port, for example `10.0.0.4:5000`. Because that local registry is plain HTTP, configure the VPS Docker daemon once:
 
 ```json
 {