Reverse proxy broken (`ERR_TOO_MANY_REDIRECTS 308` on Chrome) #610

vwxyzjn · 2021-10-08T21:55:58Z

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

The text was updated successfully, but these errors were encountered:

louislam · 2021-10-09T08:36:35Z

Not sure what happen, I cannot reproduce. As there is no redirect logic in Uptime Kuma, I assume it is not an Uptime Kuma problem.

Vault108 · 2021-10-09T12:42:21Z

@vwxyzjn By any chance did you configure caddy with logging? If so could you post your log file and cady config file if possible? Will help me troubleshoot the issue.

Not sure what happen, I cannot reproduce. As there is no redirect logic in Uptime Kuma, I assume it is not an Uptime Kuma problem.

I have an may idea of what the problem may be. I think it's related to caddy. I will debug and run some tests when I get home.

vwxyzjn · 2021-10-09T13:30:38Z

Here is a video to reproduce the error https://streamable.com/hwse9c

vwxyzjn · 2021-10-09T13:31:50Z

This is Caddy's error

2021/10/09 13:31:03.303 INFO    using adjacent Caddyfile
2021/10/09 13:31:03.304 WARN    input is not formatted with 'caddy fmt' {"adapter": "caddyfile", "file": "Caddyfile", "line": 3}
2021/10/09 13:31:03.305 INFO    admin   admin endpoint started  {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["127.0.0.1:2019", "localhost:2019", "[::1]:2019"]}
2021/10/09 13:31:03.305 INFO    http    server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "srv0", "https_port": 443}
2021/10/09 13:31:03.305 INFO    http    enabling automatic HTTP->HTTPS redirects       {"server_name": "srv0"}
2021/10/09 13:31:03.305 INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc0002bb110"}
2021/10/09 13:31:03.306 INFO    http    enabling automatic TLS certificate management  {"domains": ["status.jtuantuan.com"]}
2021/10/09 13:31:03.307 INFO    tls     cleaning storage unit   {"description": "FileStorage:/root/.local/share/caddy"}
2021/10/09 13:31:03.308 INFO    tls     finished cleaning storage units
2021/10/09 13:31:03.316 INFO    autosaved config (load with --resume flag)      {"file": "/root/.config/caddy/autosave.json"}
2021/10/09 13:31:03.316 INFO    serving initial configuration
2021/10/09 13:31:10.672 ERROR   http.log.error  read tcp [::1]:46442->[::1]:3001: read: connection reset by peer        {"request": {"remote_addr": "144.118.76.208:1144", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Sec-Websocket-Key": ["PllP47yJuEL0vem1rnguBg=="], "Sec-Websocket-Version": ["13"], "Cache-Control": ["no-cache"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15"], "Connection": ["Upgrade"], "Upgrade": ["websocket"], "Accept": ["*/*"], "Sec-Websocket-Extensions": ["permessage-deflate"], "Accept-Encoding": ["gzip, deflate"], "Origin": ["https://status.jtuantuan.com"], "Pragma": ["no-cache"], "Accept-Language": ["en-US,en;q=0.9"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "http/1.1", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.000874329, "status": 502, "err_id": "vq3vz5ahv", "err_trace": "reverseproxy.statusError (reverseproxy.go:857)"}
2021/10/09 13:31:10.702 ERROR   http.log.error  read tcp [::1]:46446->[::1]:3001: read: connection reset by peer        {"request": {"remote_addr": "144.118.76.208:1149", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Accept": ["*/*"], "Sec-Websocket-Key": ["swYANUDiCQgcrQ5MFV5iZA=="], "Sec-Websocket-Version": ["13"], "Accept-Language": ["en-US,en;q=0.9"], "Cache-Control": ["no-cache"], "Accept-Encoding": ["gzip, deflate"], "Origin": ["https://status.jtuantuan.com"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15"], "Sec-Websocket-Extensions": ["permessage-deflate"], "Connection": ["Upgrade"], "Upgrade": ["websocket"], "Pragma": ["no-cache"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "http/1.1", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.000568555, "status": 502, "err_id": "9pbxmu7yg", "err_trace": "reverseproxy.statusError (reverseproxy.go:857)"}
2021/10/09 13:31:10.830 ERROR   http.log.error  read tcp [::1]:46450->[::1]:3001: read: connection reset by peer        {"request": {"remote_addr": "144.118.76.208:1150", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Pragma": ["no-cache"], "Upgrade": ["websocket"], "Origin": ["https://status.jtuantuan.com"], "Sec-Websocket-Version": ["13"], "Accept-Encoding": ["gzip, deflate, br"], "Sec-Websocket-Extensions": ["permessage-deflate; client_max_window_bits"], "Connection": ["Upgrade"], "Cache-Control": ["no-cache"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36"], "Accept-Language": ["en-US,en;q=0.9"], "Sec-Websocket-Key": ["oEllzlUmUeJ9urtYzPt4og=="]}, "tls": {"resumed": true, "version": 772, "cipher_suite": 4865, "proto": "", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.000710085, "status": 502, "err_id": "5wegrniwh", "err_trace": "reverseproxy.statusError (reverseproxy.go:857)"}
2021/10/09 13:31:12.370 ERROR   http.log.error  read tcp [::1]:46456->[::1]:3001: read: connection reset by peer        {"request": {"remote_addr": "144.118.76.208:1144", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Accept-Language": ["en-US,en;q=0.9"], "Sec-Websocket-Extensions": ["permessage-deflate"], "Accept-Encoding": ["gzip, deflate"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15"], "Connection": ["Upgrade"], "Upgrade": ["websocket"], "Sec-Websocket-Key": ["J9oBZ84ZveJJUJMbDoL8YA=="], "Pragma": ["no-cache"], "Accept": ["*/*"], "Sec-Websocket-Version": ["13"], "Cache-Control": ["no-cache"], "Origin": ["https://status.jtuantuan.com"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "http/1.1", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.00074004, "status": 502, "err_id": "vt99n72w9", "err_trace": "reverseproxy.statusError (reverseproxy.go:857)"}
2021/10/09 13:31:13.762 ERROR   http.log.error  dial tcp [::1]:3001: connect: connection refused        {"request": {"remote_addr": "144.118.76.208:1144", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Accept": ["*/*"], "Cache-Control": ["no-cache"], "Accept-Encoding": ["gzip, deflate"], "Connection": ["Upgrade"], "Upgrade": ["websocket"], "Pragma": ["no-cache"], "Sec-Websocket-Key": ["FZ3lHnuoVA36Q4tCgCVORA=="], "Sec-Websocket-Version": ["13"], "Accept-Language": ["en-US,en;q=0.9"], "Sec-Websocket-Extensions": ["permessage-deflate"], "Origin": ["https://status.jtuantuan.com"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15"]}, "tls": {"resumed": false, "version": 772, "cipher_suite": 4865, "proto": "http/1.1", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.000562, "status": 502, "err_id": "6ux9yikht", "err_trace": "reverseproxy.statusError (reverseproxy.go:857)"}
2021/10/09 13:31:14.055 ERROR   http.log.error  dial tcp [::1]:3001: connect: connection refused        {"request": {"remote_addr": "144.118.76.208:1046", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Sec-Websocket-Extensions": ["permessage-deflate; client_max_window_bits"], "Connection": ["Upgrade"], "Pragma": ["no-cache"], "Accept-Encoding": ["gzip, deflate, br"], "Accept-Language": ["en-US,en;q=0.9"], "Sec-Websocket-Key": ["+302pmbXWh9T7taJGgr9Ig=="], "Sec-Websocket-Version": ["13"], "Cache-Control": ["no-cache"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36"], "Upgrade": ["websocket"], "Origin": ["https://status.jtuantuan.com"]}, "tls": {"resumed": true, "version": 772, "cipher_suite": 4865, "proto": "", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.000564388, "status": 502, "err_id": "txpiqu0ey", "err_trace": "reverseproxy.statusError (reverseproxy.go:857)"}

louislam · 2021-10-09T13:51:16Z

Have you tried 1.7.3 instead of 1.7.3-alpine?

vwxyzjn · 2021-10-09T13:53:16Z

just tried. Same thing. I had also tried just louislam/uptime-kuma:1

vwxyzjn · 2021-10-09T13:54:11Z

As there is no redirect logic in Uptime Kuma,

in the uptime’s log, there is

Listening on 3001
Redirect to setup page
Redirect to setup page
Redirect to setup page
Redirect to setup page
Redirect to setup page

Vault108 · 2021-10-09T14:19:06Z

2021/10/09 13:31:14.055 ERROR http.log.error dial tcp [::1]:3001: connect: connection refused {"request": {"remote_addr": "144.118.76.208:1046", "proto": "HTTP/1.1", "method": "GET", "host": "status.jtuantuan.com", "uri": "/socket.io/?EIO=4&transport=websocket", "headers": {"Sec-Websocket-Extensions": ["permessage-deflate; client_max_window_bits"], "Connection": ["Upgrade"], "Pragma": ["no-cache"], "Accept-Encoding": ["gzip, deflate, br"], "Accept-Language": ["en-US,en;q=0.9"], "Sec-Websocket-Key": ["+302pmbXWh9T7taJGgr9Ig=="], "Sec-Websocket-Version": ["13"], "Cache-Control": ["no-cache"], "User-Agent": ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.81 Safari/537.36"], "Upgrade": ["websocket"], "Origin": ["https://status.jtuantuan.com"]}, "tls": {"resumed": true, "version": 772, "cipher_suite": 4865, "proto": "", "proto_mutual": true, "server_name": "status.jtuantuan.com"}}, "duration": 0.000564388,

Checked the url redirect it seems like it's trying to redirect to HTTPS but its getting the 502 error.

if possible can you post your Caddy config?

vwxyzjn · 2021-10-09T14:20:28Z

Hmmm I don’t think I have used a Caddy config. It’s just that caddy file and run.

vwxyzjn · 2021-10-09T14:21:53Z

Why wouldn’t louislam/uptime-kuma:1.6.0-alpine Cause the problem? It doesn’t feel like a caddy error…

vwxyzjn · 2021-10-09T14:23:47Z

Maybe this https://caddy.community/t/too-many-redirects-occurred-trying-to-open-site/6656/4 is helpful

louislam · 2021-10-09T14:27:03Z

The big change between 1.7.3 and 1.6.0 is that I merged the "dumb-init" change and upgraded Node.js to 14.18.0 which were done in 1.7.1

Could you also try 1.7.0, thanks.

Vault108 · 2021-10-09T14:39:50Z

Hmmm I don’t think I have used a Caddy config. It’s just that caddy file and run.

yes, sorry that is the caddy config. Could you post that and try 1.7.0 like Louislam said

vwxyzjn · 2021-10-09T14:42:25Z

The caddyfile is simply

status.jtuantuan.com
reverse_proxy localhost:3001

I can confirm 1.7.0 works

Vault108 · 2021-10-09T14:59:05Z

The caddyfile is simply
status.jtuantuan.com
reverse_proxy localhost:3001
I can confirm 1.7.0 works

Please try the following:

status.jtuantuan.com {
    reverse_proxy 127.0.0.1:3001 
}

also @louislam it looks like there is an extra : in the config for caddy.
https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy#caddy

vwxyzjn · 2021-10-09T15:02:42Z

@Vault108 Thanks for the reply. I was following documentation here: https://caddyserver.com/docs/quick-starts/reverse-proxy.

Also, I have tried with the following below, and it didn't make any difference. Like the experiments suggested, this shouldn't be a problem with Caddy.

status.jtuantuan.com {
    reverse_proxy 127.0.0.1:3001 
}

Vault108 · 2021-10-09T15:08:13Z

@Vault108 Thanks for the reply. I was following documentation here: https://caddyserver.com/docs/quick-starts/reverse-proxy.

Also, I have tried with the following below, and it didn't make any difference. Like the experiments suggested, this shouldn't be a problem with Caddy.
status.jtuantuan.com {
    reverse_proxy 127.0.0.1:3001 
}

No worries! :) I will have to debug more later on when i get home
Could you try if you have not already to set https up? https://caddyserver.com/docs/quick-starts/https#https-quick-start

louislam · 2021-10-09T15:11:55Z

Thank you so much for testing. I just made a nightly build without dumb-init:

Remember to backup your database, it will upgrade your db to 1.8.0

louislam/uptime-kuma:nightly-no-dumb-init

If this is still not working, it maybe a bug of Node.js 14.18.0

louislam · 2021-10-09T15:41:17Z

Found this similar issue on the Caddy forum.
https://caddy.community/t/spa-too-many-redirects/12795

Btw, what is your caddy version? Did you pull the latest version of caddy?

vwxyzjn · 2021-10-09T15:51:37Z

I think it was the latest 2.4.5

…

________________________________ From: Louis Lam ***@***.***> Sent: Saturday, October 9, 2021 11:41:27 AM To: louislam/uptime-kuma ***@***.***> Cc: Costa Huang ***@***.***>; Mention ***@***.***> Subject: Re: [louislam/uptime-kuma] Reverse proxy broken (`ERR_TOO_MANY_REDIRECTS 308` on Chrome) (#610) Found this similar issue on the Caddy forum. https://caddy.community/t/spa-too-many-redirects/12795 Btw, what is your caddy version? Did you pull the latest version of caddy? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#610 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABKMJE646BMF7PC6VPL2LYTUGBPCPANCNFSM5FUPDJAQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Vault108 · 2021-10-09T18:16:46Z

@louislam Wait, quick question is HTTPS-Portal different than Caddy?? Using both would most likely cause issues!

vwxyzjn · 2021-10-09T18:17:49Z

I think they are different and I was not using them at the same time.

Vault108 · 2021-10-09T18:23:48Z

I think they are different and I was not using them at the same time.

They are, i have created a centos vps and am in the process of copying your settings, hopefully we can find out the issue.

Vault108 · 2021-10-09T18:40:30Z

Why wouldn’t louislam/uptime-kuma:1.6.0-alpine Cause the problem? It doesn’t feel like a caddy error…

Now i could not reproduce your issue directly, now I am not to familiar with docker, but could this be an issue with docker alpine it self?

just tried. Same thing. I had also tried just louislam/uptime-kuma:1

I did however get it running on louislam/uptime-kuma:1 but i did have to run
sudo setcap CAP_NET_BIND_SERVICE=+eip $(which caddy)

louislam · 2021-10-09T18:58:23Z

Now i could not reproduce your issue directly, now I am not to familiar with docker, but could this be an issue with docker alpine it self?

No, because @vwxyzjn had tried 1.7.3 which is Debian base.

Vault108 · 2021-10-10T00:57:48Z

Now i could not reproduce your issue directly, now I am not to familiar with docker, but could this be an issue with docker alpine it self?

No, because @vwxyzjn had tried 1.7.3 which is Debian base.

Yea I thought so. I'll continue to try to reproduce the issue.

Vault108 · 2021-10-11T07:45:16Z

So after EXTENSIVE trying I was able to get the issue to reproduce using both caddy and Https-portal. (still not sure how I reproduced it exactly but I did, I will try to document how I reproduced it later on)
Here is where it gets weird, if I press CTRL + Shit + R on the white page it loads the page normally and actually redirects properly. I also have no issues if I open the url in Firefox.
@vwxyzjn are you able to try either of those?

dbrennand · 2021-10-11T17:34:43Z

Hi,

Hmmm this issue is interesting.

I'm using Caddy and uptime-kuma docker images and I'm also experiencing this issue only with Chromium based browsers. This isn't the first time I've had issues with net::ERR_TOO_MANY_REDIRECTS 308 when using Caddy to reverse proxy to applications and access them using Chrome.

I experienced a similar issue with Planka and now again with Uptime-Kuma... 🤔

Is Uptime-Kuma also using Express.js as the web app framework? If so, I think I resolved my issue with Planka by enabling the trust proxy. However, as stated in my issue for Planka, I was never quite sure if that solved the issue.

Caddy version: 2.4.5
Uptime-Kuma version: 1.8.0-debian

My docker-compose.yaml file:

version: "3"
services:
  caddy:
    image: caddy:2.4.5
    container_name: caddy
    network_mode: host
    volumes:
      - caddy-data:/data
      # Mount Caddyfile
      - ./caddy/Caddyfile:/etc/caddy/Caddyfile
    environment:
      - ACME_EMAIL=
    restart: always
  uptime-kuma:
    image: louislam/uptime-kuma:1.8.0-debian
    container_name: uptime-kuma
    ports:
      - "127.0.0.1:3001:3001"
    volumes:
      - uptime-kuma:/app/data
    restart: unless-stopped

volumes:
  caddy-data:
  uptime-kuma:

Caddyfile:

{
    email {env.ACME_EMAIL}
}
...
uptime.net.domain.tld {
    reverse_proxy localhost:3001 :
}
...

louislam · 2021-10-11T18:39:39Z

Since @vwxyzjn is ok with 1.7.0, I try to build images that reverted some important change.

@vwxyzjn @dbrennand would you able to try?

Older Node 14 (14.17.6)
louislam/uptime-kuma:nightly-node-14.17.6

No dumb-init
louislam/uptime-kuma:nightly-no-dumb-init

Is Uptime-Kuma also using Express.js as the web app framework

Yes, it is express.js. I will try to build this too tomorrow.

dbrennand · 2021-10-11T19:04:41Z

Hi @louislam

Both images louislam/uptime-kuma:nightly-node-14.17.6 and louislam/uptime-kuma:nightly-no-dumb-init have the same issue.

louislam · 2021-10-12T14:19:48Z

Hi @louislam

Both images louislam/uptime-kuma:nightly-node-14.17.6 and louislam/uptime-kuma:nightly-no-dumb-init have the same issue.

Thank you for testing, I have enabled "trust proxy" for this build, feel free to try.

louislam/uptime-kuma:nightly-trust-proxy

dbrennand · 2021-10-12T15:18:59Z

No worries, hopefully I can test later this evening and I'll report back o7 😄

dbrennand · 2021-10-12T18:40:05Z

@louislam Hasn't made a difference sadly. How exactly did you enable trust proxy? Which type did you use?

louislam · 2021-10-12T19:06:30Z

app.enable("trust proxy");

http://expressjs.com/zh-tw/api.html#app.enable

I double checked, this line is presented in the container.

dbrennand · 2021-10-14T17:05:35Z

Not really sure on the next course of action here :-(

vwxyzjn · 2021-10-14T17:20:01Z

Hmm, not sure what happened, but it seems fine now... LOL

dbrennand · 2021-10-14T17:21:24Z

Hmm, not sure what happened, but it seems fine now... LOL

What about when using 1.8.0.

vwxyzjn · 2021-10-14T17:24:30Z

It's fine... I didn't even change any configuration.

dbrennand · 2021-10-14T17:27:17Z

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

Vault108 · 2021-10-14T17:59:12Z

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 😁

louislam · 2021-10-14T18:03:48Z

🤣 A lot of question marks here.

Is that the ":" cause the problem?

Anyway, glad you guys can make it works.

vwxyzjn · 2021-10-14T18:54:13Z

For whatever reason, caddy works file and https-portal also worked....

vwxyzjn added the bug Something isn't working label Oct 8, 2021

louislam added help and removed bug Something isn't working labels Oct 9, 2021

louislam added the investigating label Oct 9, 2021

louislam added Unknown and removed investigating labels Oct 13, 2021

louislam closed this as completed Oct 23, 2021

Reverse proxy broken (ERR_TOO_MANY_REDIRECTS 308 on Chrome) #610

Reverse proxy broken (ERR_TOO_MANY_REDIRECTS 308 on Chrome) #610

Comments

vwxyzjn commented Oct 8, 2021

louislam commented Oct 9, 2021

Vault108 commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

louislam commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

Vault108 commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

louislam commented Oct 9, 2021

Vault108 commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

Vault108 commented Oct 9, 2021 • edited

vwxyzjn commented Oct 9, 2021

Vault108 commented Oct 9, 2021 • edited

louislam commented Oct 9, 2021

louislam commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021 via email

Vault108 commented Oct 9, 2021

vwxyzjn commented Oct 9, 2021

Vault108 commented Oct 9, 2021

Vault108 commented Oct 9, 2021

louislam commented Oct 9, 2021

Vault108 commented Oct 10, 2021

Vault108 commented Oct 11, 2021 • edited

dbrennand commented Oct 11, 2021 • edited

louislam commented Oct 11, 2021 • edited

dbrennand commented Oct 11, 2021 • edited

louislam commented Oct 12, 2021

dbrennand commented Oct 12, 2021

dbrennand commented Oct 12, 2021

louislam commented Oct 12, 2021

dbrennand commented Oct 14, 2021

vwxyzjn commented Oct 14, 2021 • edited

dbrennand commented Oct 14, 2021

vwxyzjn commented Oct 14, 2021

dbrennand commented Oct 14, 2021 • edited

Vault108 commented Oct 14, 2021

louislam commented Oct 14, 2021

vwxyzjn commented Oct 14, 2021

Reverse proxy broken (`ERR_TOO_MANY_REDIRECTS 308` on Chrome) #610

Reverse proxy broken (`ERR_TOO_MANY_REDIRECTS 308` on Chrome) #610

Vault108 commented Oct 9, 2021 •

edited

Vault108 commented Oct 9, 2021 •

edited

Vault108 commented Oct 11, 2021 •

edited

dbrennand commented Oct 11, 2021 •

edited

louislam commented Oct 11, 2021 •

edited

dbrennand commented Oct 11, 2021 •

edited

vwxyzjn commented Oct 14, 2021 •

edited

dbrennand commented Oct 14, 2021 •

edited