Files
proxmox/docs/04-configuration/verification-evidence/E2E_GITEA_RESULTS.md
defiQUG bea1903ac9
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Sync all local changes: docs, config, scripts, submodule refs, verification evidence
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-21 15:46:06 -08:00

1.4 KiB

E2E Verification — Gitea (and Dev/Codespaces) Results

Date: 2026-02-14
Run: scripts/verify/verify-end-to-end-routing.sh (after adding gitea.d-bis.org, dev.d-bis.org, codespaces.d-bis.org to e2e and changing Dev VM IP to 192.168.11.59)

Domain DNS SSL HTTPS Notes
gitea.d-bis.org pass pass 200 No issues
dev.d-bis.org pass pass 200 No issues
codespaces.d-bis.org pass pass 200 No issues

Conclusion: No issues found with Gitea in the full e2e run. All three domains resolve, present valid TLS, and return HTTP 200.

Other E2E failures (not Gitea)

  • RPC 502: rpc-alltra.d-bis.org, rpc-alltra-2, rpc-alltra-3, rpc-hybx, rpc-hybx-2, rpc-hybx-3, rpc-http-prv.d-bis.org (existing RPC backend/tunnel issues).
  • HTTPS 502: dbis-admin.d-bis.org, dbis-api.d-bis.org, dbis-api-2.d-bis.org, secure.d-bis.org (backend or NPMplus → backend path).

After Dev VM IP change to .59

  1. Reconfigure LXC 5700 on Proxmox to use 192.168.11.59 (see docs/04-configuration/DEV_VM_IP_CHANGE_59.md).
  2. Update NPMplus Fourth proxy hosts so gitea/dev/codespaces forward to 192.168.11.59:3000:
    NPM_PASSWORD=xxx bash scripts/nginx-proxy-manager/update-npmplus-fourth-proxy-hosts.sh
    
  3. Re-run e2e from LAN if you want to confirm Gitea still returns 200 after the VM is on .59.