Reverse proxy broken (`ERR_TOO_MANY_REDIRECTS 308` on Chrome)

Is it a duplicate question? Don’t think so.

Describe the bug With the latest louislam/uptime-kuma:1.7.3-alpine docker container, reverse proxy can no longer be used and the following error appears with both caddy and https-portal.

By reverting to louislam/uptime-kuma:1.6.0-alpine resolves this issue:

To Reproduce Steps to reproduce the behavior:

Run the following docker-compose.yaml file:

version: '3.3'

services:
  https-portal:
    image: steveltn/https-portal:1
    ports:
      - '80:80'
      - '443:443'
    links:
      - uptime-kuma
    restart: always
    environment:
      DOMAINS: 'example.com -> http://uptime-kuma:3001'
      STAGE: 'production' # Don't use production until staging works
      # FORCE_RENEW: 'true'
      WEBSOCKET: 'true'
    volumes:
      - https-portal-data:/var/lib/https-portal

  uptime-kuma:
    image: louislam/uptime-kuma:1.7.3-alpine
    volumes:
      - ./uptime-kuma:/app/data
    ports:
      - 3001:3001

volumes:
  https-portal-data:

Info Uptime Kuma Version: 1.7.3 Using Docker?: Yes Docker Version: 20.10.8 OS: Centos 8 Browser: chrome, safari

[louislam]

🤣 A lot of question marks here.

Is that the “:” cause the problem?

Anyway, glad you guys can make it works.

[Vault108]

Ok this is kinda weird. I’m running 1.8.0 and it’s working now in Chrome 😆

This is running louislam/uptime-kuma:nightly-trust-proxy. What I did change was remove the “:” character in the Caddyfile from the Wiki, pretty sure that may be a typo:

subdomain.domain.com {
    reverse_proxy 127.0.0.1:3001 : <--- Removed this ":"
}

Restarted Caddy and then cleared my browser’s cache.

@louislam

Yes looks like that is, I think I posted it above. Glad it’s working. I was testing and it started working for me too 😁