Skip to content
CI

docs: cover deploying behind a reverse proxy that already owns 443 #2203

Sign in to view logs

docs: cover deploying behind a reverse proxy that already owns 443

docs: cover deploying behind a reverse proxy that already owns 443 #2203

Triggered via pull request August 28, 2026 05:41
@gosunutsgosunuts
synchronize #296
docs/reverse-proxy-deployment
Status Failure
Total duration 1m 1s
Artifacts 1

ci.yml

on: pull_request
Verify
53s
Verify
Build Tunnel Image
21s
Build Tunnel Image
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
Verify
Process completed with exit code 2.
Verify: cmd/relay-server/config.go#L379
[Control Flow: Boolean Expression Complexity] condition contains 3 logical operators (mixed AND/OR); break down into well-named intermediate boolean variables or extract to a predicate function
Verify: cmd/relay-server/config.go#L200
[Control Flow: Safe Defaults + Go 1.21] replace manual fallback check with 'cmp.Or(provider, ...)' for concise, declarative default value assignment
Verify: cmd/relay-server/config.go#L139
[Control Flow: Safe Defaults + Go 1.21] replace manual fallback check with 'cmp.Or(provider, ...)' for concise, declarative default value assignment
Build Tunnel Image
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
gosuda~portal-tunnel~OC62G1.dockerbuild
38.2 KB
sha256:670deea25ddb97341acf3ec9eefd087f6795c63150fb71043d01c766e2bf9297