Fixes for timeouts (maybe?) and fix for Traefik Basic Auth password
Some checks failed
ci/woodpecker/push/ci Pipeline failed
ci/woodpecker/push/deploy unknown status

This commit is contained in:
2026-02-07 14:11:44 -03:00
parent 49fa4cbc36
commit 29be8d6307
3 changed files with 25 additions and 5 deletions

View File

@@ -68,10 +68,10 @@ services:
MAIL_FROM: 'mifi Holdings Shorty <noreply@mifi.holdings>' MAIL_FROM: 'mifi Holdings Shorty <noreply@mifi.holdings>'
MAIL_PASSWORD: '${SMTP_PASSWORD:?Set SMTP_PASSWORD}' MAIL_PASSWORD: '${SMTP_PASSWORD:?Set SMTP_PASSWORD}'
NODE_ENV: production NODE_ENV: production
OIDC_ENABLED: 'true' # OIDC_ENABLED: 'true'
OIDC_ISSUER: 'https://git.mifi.dev' # OIDC_ISSUER: 'https://git.mifi.dev'
OIDC_CLIENT_ID: '2a6d1ecd-4e2f-42e5-922e-22e878230488' # OIDC_CLIENT_ID: '2a6d1ecd-4e2f-42e5-922e-22e878230488'
OIDC_CLIENT_SECRET: '${OIDC_CLIENT_SECRET:?Set OIDC_CLIENT_SECRET}' # OIDC_CLIENT_SECRET: '${OIDC_CLIENT_SECRET:?Set OIDC_CLIENT_SECRET}'
REDIS_ENABLED: 'true' REDIS_ENABLED: 'true'
REDIS_HOST: kutt_redis REDIS_HOST: kutt_redis
REDIS_PORT: '6379' REDIS_PORT: '6379'
@@ -85,6 +85,7 @@ services:
- 'traefik.http.routers.kutt-mifi.tls.certresolver=letsencrypt' - 'traefik.http.routers.kutt-mifi.tls.certresolver=letsencrypt'
- 'traefik.http.routers.kutt-mifi.service=kutt-short' - 'traefik.http.routers.kutt-mifi.service=kutt-short'
- 'traefik.http.services.kutt-short.loadbalancer.server.port=3000' - 'traefik.http.services.kutt-short.loadbalancer.server.port=3000'
- 'traefik.http.services.kutt-short.loadbalancer.serversTransport=kutt-long-timeout'
qr_api: qr_api:
image: ${REGISTRY:-git.mifi.dev}/mifi-holdings/shorty-qr-api:${IMAGE_TAG:-latest} image: ${REGISTRY:-git.mifi.dev}/mifi-holdings/shorty-qr-api:${IMAGE_TAG:-latest}
@@ -122,7 +123,7 @@ services:
- 'traefik.http.routers.qr-web.tls.certresolver=letsencrypt' - 'traefik.http.routers.qr-web.tls.certresolver=letsencrypt'
- 'traefik.http.routers.qr-web.service=qr-web' - 'traefik.http.routers.qr-web.service=qr-web'
- 'traefik.http.routers.qr-web.middlewares=qr-web-basicauth' - 'traefik.http.routers.qr-web.middlewares=qr-web-basicauth'
- 'traefik.http.middlewares.qr-web-basicauth.basicauth.users=mifi:$$2y$$05$$TS20fkfrmJ3MLc.cgfM6OcuowOstcy/2DTOq0YfirUDU3b0vtNz.' - 'traefik.http.middlewares.qr-web-basicauth.basicauth.users=mifi:$$apr1$$9fgAWvE1$$bLGgUtpFjdaexkV5gooWq.'
- 'traefik.http.services.qr-web.loadbalancer.server.port=3000' - 'traefik.http.services.qr-web.loadbalancer.server.port=3000'
networks: networks:

View File

@@ -28,3 +28,5 @@ Dockerfile
# Generated # Generated
next-env.d.ts next-env.d.ts
*.tsbuildinfo *.tsbuildinfo
traefik-kutt-timeout.example.yml

View File

@@ -0,0 +1,17 @@
# Example Traefik dynamic config: longer backend timeout for Kutt.
#
# Use a SEPARATE file (e.g. serverstransports.yaml or kutt-timeout.yaml), NOT inside
# routers.yaml — Traefik can reject serversTransports in a file it treats as routers-only.
# Place this file in the same directory as your other dynamic config (e.g. /etc/traefik/conf.d/)
# so the file provider picks it up.
#
# Then uncomment the serversTransport label on the kutt service in docker-compose.portainer.yml.
#
# responseHeaderTimeout: time to wait for backend response headers (0 = no timeout).
# 300s helps avoid 504 Gateway Timeout when Kutt or OIDC is slow.
# If 504s persist, also raise entrypoint transport.respondingTimeouts.readTimeout in Traefik static config.
http:
serversTransports:
kutt-long-timeout:
forwardingTimeouts:
responseHeaderTimeout: "300s"