OIDC with Cloudflare proxied domains #48

@reddwarf666 commented on GitHub (Mar 19, 2025):

Ok, thanks. I will look into Authentik.
By the way, I was looking around and stumbled across this:
https://github.com/vouch/vouch-proxy/blob/master/config/config.yml_example_gitea

Would that work for Godoxy? I mean, I have Gitea running in my setup so... 😀

@reddwarf666 commented on GitHub (Mar 19, 2025): Ok, thanks. I will look into Authentik. By the way, I was looking around and stumbled across this: https://github.com/vouch/vouch-proxy/blob/master/config/config.yml_example_gitea Would that work for Godoxy? I mean, I have Gitea running in my setup so... 😀

adam commented

@yusing commented on GitHub (Mar 19, 2025):

Actually I'm not sure why you want things like OAuth2-Proxy and vouch.

You can simpily set these environment variables and then enable oidc middleware per app like this:

labels:
  proxy.yourapp.middlewares.oidc:

@yusing commented on GitHub (Mar 19, 2025): Actually I'm not sure why you want things like _OAuth2-Proxy_ and _vouch_. You can simpily set [these environment variables](https://github.com/yusing/godoxy/wiki#oidc) and then enable oidc middleware per app like this: ```yaml labels: proxy.yourapp.middlewares.oidc: ```

adam commented

@reddwarf666 commented on GitHub (Mar 19, 2025):

Oh, not wanting it, I was just surprised Gitea could be used as a OIDC.
I will go with what you support and Godoxy supports. And I saw in the docs Godoxy supports Authentik so I will see where that takes me.

@reddwarf666 commented on GitHub (Mar 19, 2025): Oh, not wanting it, I was just surprised Gitea could be used as a OIDC. I will go with what you support and Godoxy supports. And I saw in the docs Godoxy supports Authentik so I will see where that takes me.

adam commented

2025-12-29 09:22:05 +01:00

@reddwarf666 commented on GitHub (Mar 20, 2025):

Ok, I have Authentik running! Yay!

However, I could logon/start with the URL: https://auth.example.com/if/flow/initial-setup/
But I could access Authentic via the internal docker host address: http://docker_host:9000/if/flow/initial-setup/
So I can also see now : http://docker_host:9000/if/admin/#/administration/overview
I could create a new user, disable the default admin, logon with my new account. All looks well.

The message in a browser:
Request failed. Please try again later

My route file in Godoxy:

auth:
  scheme: http
  port: 9000
  middlewares:
    set_x_forwarded:
  homepage:
    show: true
    name: ""
    category: ""
    description: ""
    icon: https://cdn.jsdelivr.net/gh/selfhst/icons/webp/authentik.webp
  host: 192.168.2.192
  load_balance:
    link: ""
    mode: ""
  healthcheck:
    disable: true

Is there anything I need to look at from Godoxy point of view?

@reddwarf666 commented on GitHub (Mar 20, 2025): Ok, I have Authentik running! Yay! However, I could logon/start with the URL: https://auth.example.com/if/flow/initial-setup/ But I could access Authentic via the internal docker host address: http://docker_host:9000/if/flow/initial-setup/ So I can also see now : http://docker_host:9000/if/admin/#/administration/overview I could create a new user, disable the default admin, logon with my new account. All looks well. The message in a browser: `Request failed. Please try again later` ![Image](https://github.com/user-attachments/assets/cee40b41-462b-4321-9870-95bca9196261) My route file in Godoxy: ``` auth: scheme: http port: 9000 middlewares: set_x_forwarded: homepage: show: true name: "" category: "" description: "" icon: https://cdn.jsdelivr.net/gh/selfhst/icons/webp/authentik.webp host: 192.168.2.192 load_balance: link: "" mode: "" healthcheck: disable: true ``` Is there anything I need to look at from Godoxy point of view?

adam commented

@yusing commented on GitHub (Mar 20, 2025):

Remove the set_x_forwarded middleware and try again

Are you running authentik LXC or docker btw?

@yusing commented on GitHub (Mar 20, 2025): Remove the `set_x_forwarded` middleware and try again Are you running authentik LXC or docker btw?

adam commented

2025-12-29 09:22:05 +01:00

@reddwarf666 commented on GitHub (Mar 20, 2025):

Thanks. Tried that just now and get the same error. I thought to add that setting as in other solutions it was needed I think to set it. I'm running Authentik in Docker.

I was wondering about 3 things in the Authentik setup:
1)
AUTHENTIK_COOKIE_DOMAIN
Would I need to set that?
I had it set to example.com initially and got the same message. Then commented it out but same result.
Perhaps setting it to auth.example.com is needed?

2)

CLOUDFLARE_IPS
LOCAL_IPS

I saw some config from Brokenscripts where it was set like so:

CLOUDFLARE_IPS=173.245.48.0/20,103.21.244.0/22,103.22.200.0/22,103.31.4.0/22,141.101.64.0/18,108.162.192.0/18,190.93.240.0/20,188.114.96.0/20,197.234.240.0/22,198.41.128.0/17,162.158.0.0/15,104.16.0.0/13,104.24.0.0/14,172.64.0.0/13,131.0.72.0/22
LOCAL_IPS=127.0.0.1/32,10.0.0.0/8,192.168.0.0/16,172.16.0.0/12

Would that make sense?

3)

AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS
From : https://github.com/brokenscripts/authentik_traefik/blob/traefik3/my-compose/.env
# AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS: CHANGEME_IFAPPLICABLE 
# Defaults to all of: 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fe80::/10, ::1/128

This one seems to make a lot of sense somehow.

Perhaps you can have an idea about these and if they are needed?

@reddwarf666 commented on GitHub (Mar 20, 2025): Thanks. Tried that just now and get the same error. I thought to add that setting as in other solutions it was needed I think to set it. I'm running Authentik in Docker. I was wondering about 3 things in the Authentik setup: **1)** `AUTHENTIK_COOKIE_DOMAIN` Would I need to set that? I had it set to `example.com` initially and got the same message. Then commented it out but same result. Perhaps setting it to `auth.example.com` is needed? **2)** ``` CLOUDFLARE_IPS LOCAL_IPS ``` I saw some config from Brokenscripts where it was set like so: ``` CLOUDFLARE_IPS=173.245.48.0/20,103.21.244.0/22,103.22.200.0/22,103.31.4.0/22,141.101.64.0/18,108.162.192.0/18,190.93.240.0/20,188.114.96.0/20,197.234.240.0/22,198.41.128.0/17,162.158.0.0/15,104.16.0.0/13,104.24.0.0/14,172.64.0.0/13,131.0.72.0/22 LOCAL_IPS=127.0.0.1/32,10.0.0.0/8,192.168.0.0/16,172.16.0.0/12 ``` Would that make sense? **3)** ``` AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS From : https://github.com/brokenscripts/authentik_traefik/blob/traefik3/my-compose/.env # AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS: CHANGEME_IFAPPLICABLE # Defaults to all of: 127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, fe80::/10, ::1/128 ``` This one seems to make a lot of sense somehow. Perhaps you can have an idea about these and if they are needed?

adam commented

2025-12-29 09:22:05 +01:00

@yusing commented on GitHub (Mar 20, 2025):

For docker containers, you should use docker labels instead of route files. If you want to use it in a NPM way (create routes manually on WebUI), enable explicit mode like this to avoid route conflicts:

# config.yml
...
providers:
  docker:
    local!: $DOCKER_HOST # add a ! after the name

I'm not sure why you have got into that error. Let me give you an example docker compose file for authentik (basically default compose.yml with three labels added) and the .env file:

---

services:
  postgresql:
    image: docker.io/library/postgres:16-alpine
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}"]
      start_period: 20s
      interval: 30s
      retries: 5
      timeout: 5s
    volumes:
      - ./data/db:/var/lib/postgresql/data
    environment:
      POSTGRES_PASSWORD: ${PG_PASS:?database password required}
      POSTGRES_USER: ${PG_USER:-authentik}
      POSTGRES_DB: ${PG_DB:-authentik}
    env_file:
      - .env
  redis:
    image: docker.io/library/redis:alpine
    command: --save 60 1 --loglevel warning
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "redis-cli ping | grep PONG"]
      start_period: 20s
      interval: 30s
      retries: 5
      timeout: 3s
    volumes:
      - ./data/redis:/data
  server:
    image: ${AUTHENTIK_IMAGE:-ghcr.io/goauthentik/server}:${AUTHENTIK_TAG:-2024.10.1}
    labels:
      - proxy.aliases=auth
      - proxy.auth.port=9000
      - proxy.auth.healthcheck.disable=true
      - proxy.auth.middlewares.redirect_http
    restart: unless-stopped
    command: server
    environment:
      AUTHENTIK_REDIS__HOST: redis
      AUTHENTIK_POSTGRESQL__HOST: postgresql
      AUTHENTIK_POSTGRESQL__USER: ${PG_USER:-authentik}
      AUTHENTIK_POSTGRESQL__NAME: ${PG_DB:-authentik}
      AUTHENTIK_POSTGRESQL__PASSWORD: ${PG_PASS}
    volumes:
      - ./media:/media
      - ./custom-templates:/templates
    env_file:
      - .env
    depends_on:
      - postgresql
      - redis
  worker:
    image: ${AUTHENTIK_IMAGE:-ghcr.io/goauthentik/server}:${AUTHENTIK_TAG:-2024.10.1}
    restart: unless-stopped
    command: worker
    labels:
      - proxy.#1.healthcheck.disable=true
    environment:
      AUTHENTIK_REDIS__HOST: redis
      AUTHENTIK_POSTGRESQL__HOST: postgresql
      AUTHENTIK_POSTGRESQL__USER: ${PG_USER:-authentik}
      AUTHENTIK_POSTGRESQL__NAME: ${PG_DB:-authentik}
      AUTHENTIK_POSTGRESQL__PASSWORD: ${PG_PASS}
    # `user: root` and the docker socket volume are optional.
    # See more for the docker socket integration here:
    # https://goauthentik.io/docs/outposts/integrations/docker
    # Removing `user: root` also prevents the worker from fixing the permissions
    # on the mounted folders, so when removing this make sure the folders have the correct UID/GID
    # (1000:1000 by default)
    user: root
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./media:/media
      - ./certs:/certs
      - ./custom-templates:/templates
    env_file:
      - .env
    depends_on:
      - postgresql
      - redis

#.env
AUTHENTIK_TAG=2025.2
PG_PASS=REDACTED
AUTHENTIK_SECRET_KEY=REDACTED
# SMTP Host Emails are sent to
AUTHENTIK_EMAIL__HOST=smtp.mail.me.com
AUTHENTIK_EMAIL__PORT=587
# Optionally authenticate (don't add quotation marks to your password)
AUTHENTIK_EMAIL__USERNAME=REDACTED
AUTHENTIK_EMAIL__PASSWORD=REDACTED
# Use StartTLS
AUTHENTIK_EMAIL__USE_TLS=true
# Use SSL
AUTHENTIK_EMAIL__USE_SSL=false
AUTHENTIK_EMAIL__TIMEOUT=10
# Email address authentik will send from, should have a correct @domain
AUTHENTIK_EMAIL__FROM=REDACTED
AUTHENTIK_REDIS__DB=1

So basically the default docker compose and dotenv should work, without those stuff you have mentioned above.

@yusing commented on GitHub (Mar 20, 2025): For docker containers, you should use docker labels instead of route files. If you want to use it in a NPM way (create routes manually on WebUI), enable explicit mode like this to avoid route conflicts: ```yaml # config.yml ... providers: docker: local!: $DOCKER_HOST # add a ! after the name ``` I'm not sure why you have got into that error. Let me give you an example docker compose file for authentik (basically default `compose.yml` with three labels added) and the `.env` file: ```yaml --- services: postgresql: image: docker.io/library/postgres:16-alpine restart: unless-stopped healthcheck: test: ["CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}"] start_period: 20s interval: 30s retries: 5 timeout: 5s volumes: - ./data/db:/var/lib/postgresql/data environment: POSTGRES_PASSWORD: ${PG_PASS:?database password required} POSTGRES_USER: ${PG_USER:-authentik} POSTGRES_DB: ${PG_DB:-authentik} env_file: - .env redis: image: docker.io/library/redis:alpine command: --save 60 1 --loglevel warning restart: unless-stopped healthcheck: test: ["CMD-SHELL", "redis-cli ping | grep PONG"] start_period: 20s interval: 30s retries: 5 timeout: 3s volumes: - ./data/redis:/data server: image: ${AUTHENTIK_IMAGE:-ghcr.io/goauthentik/server}:${AUTHENTIK_TAG:-2024.10.1} labels: - proxy.aliases=auth - proxy.auth.port=9000 - proxy.auth.healthcheck.disable=true - proxy.auth.middlewares.redirect_http restart: unless-stopped command: server environment: AUTHENTIK_REDIS__HOST: redis AUTHENTIK_POSTGRESQL__HOST: postgresql AUTHENTIK_POSTGRESQL__USER: ${PG_USER:-authentik} AUTHENTIK_POSTGRESQL__NAME: ${PG_DB:-authentik} AUTHENTIK_POSTGRESQL__PASSWORD: ${PG_PASS} volumes: - ./media:/media - ./custom-templates:/templates env_file: - .env depends_on: - postgresql - redis worker: image: ${AUTHENTIK_IMAGE:-ghcr.io/goauthentik/server}:${AUTHENTIK_TAG:-2024.10.1} restart: unless-stopped command: worker labels: - proxy.#1.healthcheck.disable=true environment: AUTHENTIK_REDIS__HOST: redis AUTHENTIK_POSTGRESQL__HOST: postgresql AUTHENTIK_POSTGRESQL__USER: ${PG_USER:-authentik} AUTHENTIK_POSTGRESQL__NAME: ${PG_DB:-authentik} AUTHENTIK_POSTGRESQL__PASSWORD: ${PG_PASS} # `user: root` and the docker socket volume are optional. # See more for the docker socket integration here: # https://goauthentik.io/docs/outposts/integrations/docker # Removing `user: root` also prevents the worker from fixing the permissions # on the mounted folders, so when removing this make sure the folders have the correct UID/GID # (1000:1000 by default) user: root volumes: - /var/run/docker.sock:/var/run/docker.sock - ./media:/media - ./certs:/certs - ./custom-templates:/templates env_file: - .env depends_on: - postgresql - redis ``` ```shell #.env AUTHENTIK_TAG=2025.2 PG_PASS=REDACTED AUTHENTIK_SECRET_KEY=REDACTED # SMTP Host Emails are sent to AUTHENTIK_EMAIL__HOST=smtp.mail.me.com AUTHENTIK_EMAIL__PORT=587 # Optionally authenticate (don't add quotation marks to your password) AUTHENTIK_EMAIL__USERNAME=REDACTED AUTHENTIK_EMAIL__PASSWORD=REDACTED # Use StartTLS AUTHENTIK_EMAIL__USE_TLS=true # Use SSL AUTHENTIK_EMAIL__USE_SSL=false AUTHENTIK_EMAIL__TIMEOUT=10 # Email address authentik will send from, should have a correct @domain AUTHENTIK_EMAIL__FROM=REDACTED AUTHENTIK_REDIS__DB=1 ``` So basically the default docker compose and dotenv should work, without those stuff you have mentioned above.

adam commented

@reddwarf666 commented on GitHub (Mar 20, 2025):

Thanks for the help!

Applied all you suggested to my setup and still face that issue.
Welp, now I will delete everything Authentik I did and start new with your suggestions, clean slate.
I will report back!

@reddwarf666 commented on GitHub (Mar 20, 2025): Thanks for the help! Applied all you suggested to my setup and still face that issue. Welp, now I will delete everything Authentik I did and start new with your suggestions, clean slate. I will report back!

adam commented

@reddwarf666 commented on GitHub (Mar 20, 2025):

One more thing, if you try this setup from scratch, do you start docker compose as root?
I run it as myself (1000:1000) so I wanted to make sure if this is done the same as you did.

@reddwarf666 commented on GitHub (Mar 20, 2025): One more thing, if you try this setup from scratch, do you start docker compose as root? I run it as myself (1000:1000) so I wanted to make sure if this is done the same as you did.

adam commented

@reddwarf666 commented on GitHub (Mar 20, 2025):

Ok, I took the sample you gave and and replaced only the REDACTED parts with my info, like passwords and so on.
Deleted all folders and files I had and started docker compose up -d
Same result unfortunately. "Request failed. Please try again later."
As the ports are not exposed in the compose file I could also not access Authentik locally, but that is understandable.

I think there is something not right in routing via the labels, as if something is missing or something like that.
But then again, I do get a screen from Authentic so it must be reachable, just not able to log on and start the initial process.
https://auth.example.com/if/flow/initial-setup/

Any ideas? I feel I'm so, so close...

@reddwarf666 commented on GitHub (Mar 20, 2025): Ok, I took the sample you gave and and replaced only the REDACTED parts with my info, like passwords and so on. Deleted all folders and files I had and started `docker compose up -d` Same result unfortunately. "Request failed. Please try again later." As the ports are not exposed in the compose file I could also not access Authentik locally, but that is understandable. I think there is something not right in routing via the labels, as if something is missing or something like that. But then again, I do get a screen from Authentic so it must be reachable, just not able to log on and start the initial process. `https://auth.example.com/if/flow/initial-setup/` Any ideas? I feel I'm so, so close...

adam commented

@yusing commented on GitHub (Mar 20, 2025):

I've just tried to setup from scratch, as myself (1000). I cannot reproduce the error, it just worked...

Could you check for the logs from those authentik containers when you hit https://auth.example.com/if/flow/initial-setup/? Also network logs from browser's DevTools.

@yusing commented on GitHub (Mar 20, 2025): I've just tried to setup from scratch, as myself (1000). I cannot reproduce the error, it just worked... Could you check for the logs from those authentik containers when you hit `https://auth.example.com/if/flow/initial-setup/`? Also network logs from browser's DevTools.

adam commented

@reddwarf666 commented on GitHub (Mar 20, 2025):

I saw some HTTPS authentication issues I think

The logs are available: https://we.tl/t-esv0Xe31Cl

Thanks!

@reddwarf666 commented on GitHub (Mar 20, 2025): I saw some HTTPS authentication issues I think The logs are available: https://we.tl/t-esv0Xe31Cl Thanks!

adam commented

@yusing commented on GitHub (Mar 21, 2025):

That's weird. Updated the docker compose above, added a redirectHTTP middleware, see if it works for you.

@yusing commented on GitHub (Mar 21, 2025): That's weird. Updated the docker compose above, added a redirectHTTP middleware, see if it works for you.

adam commented

@reddwarf666 commented on GitHub (Mar 21, 2025):

Now I see another message when I try
https://auth.example.com/if/flow/initial-setup/

Chrome:

This page isn’t working
auth.example.com redirected you too many times.

[Try deleting your cookies](https://support.google.com/chrome?p=rl_error&hl=en-GB).
ERR_TOO_MANY_REDIRECTS

Firefox:

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept cookies.

From the network tab in developer mode:

{
	"Status": "301",
	"Version": "HTTP/3",
	"Transferred": "601 B (0 B size)",
	"Request Priority": "Highest",
	"DNS Resolution": "System"
}

{
	"Response Headers (601 B)": {
		"headers": [
			{
				"name": "alt-svc",
				"value": "h3=\":443\"; ma=86400"
			},
			{
				"name": "cf-cache-status",
				"value": "DYNAMIC"
			},
			{
				"name": "cf-ray",
				"value": "9238f8f388a58ade-AMS"
			},
			{
				"name": "content-type",
				"value": "text/html; charset=utf-8"
			},
			{
				"name": "date",
				"value": "Thu, 20 Mar 2025 23:26:05 GMT"
			},
			{
				"name": "location",
				"value": "https://auth.example.com/if/flow/initial-setup/"
			},
			{
				"name": "nel",
				"value": "{\"success_fraction\":0,\"report_to\":\"cf-nel\",\"max_age\":604800}"
			},
			{
				"name": "report-to",
				"value": "{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report\\/v4?s=z%2BBPLWp3UMq5rdCOq%2BWYqJtSM%2FgLvCNmlu%2FJbXnJ7bN7Y8rjhRzhmtv2Rf5leRUNw47QZV2IrswfzDBMTCr5aN6kxJ8DxSraBiJdkAJ9grgShpCf7j23DOvTcG2mgoaIzkA5%2F2QGCAjqtitGUIU%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}"
			},
			{
				"name": "server",
				"value": "cloudflare"
			}
		]
	}
}

And just before that message/row:

{
	"Status": "301",
	"Version": "HTTP/3",
	"Transferred": "599 B (0 B size)",
	"Request Priority": "Highest",
	"DNS Resolution": "System"
}
{
	"Response Headers (599 B)": {
		"headers": [
			{
				"name": "alt-svc",
				"value": "h3=\":443\"; ma=86400"
			},
			{
				"name": "cf-cache-status",
				"value": "DYNAMIC"
			},
			{
				"name": "cf-ray",
				"value": "9238f8f368a38ade-AMS"
			},
			{
				"name": "content-type",
				"value": "text/html; charset=utf-8"
			},
			{
				"name": "date",
				"value": "Thu, 20 Mar 2025 23:26:05 GMT"
			},
			{
				"name": "location",
				"value": "https://auth.example.com/if/flow/initial-setup/"
			},
			{
				"name": "nel",
				"value": "{\"success_fraction\":0,\"report_to\":\"cf-nel\",\"max_age\":604800}"
			},
			{
				"name": "report-to",
				"value": "{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report\\/v4?s=g9o%2Fcdaqo54et2be5pzzc0U9uiHLuE8858m0TJ9v1obe7SnNt%2BPUeO5jelaOy%2F9zEtGvGhJKYEMIwkjezJh%2FEJB1KdSd9rPCbSKfqoI1jUBYLcQwUDN9slVBdFxi8Bhgull9GHZDP0kWpeIZyqg%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}"
			},
			{
				"name": "server",
				"value": "cloudflare"
			}
		]
	}
}

Screenshot of that window:

@reddwarf666 commented on GitHub (Mar 21, 2025): Now I see another message when I try `https://auth.example.com/if/flow/initial-setup/` Chrome: ``` This page isn’t working auth.example.com redirected you too many times. [Try deleting your cookies](https://support.google.com/chrome?p=rl_error&hl=en-GB). ERR_TOO_MANY_REDIRECTS ``` Firefox: ``` The page isn’t redirecting properly Firefox has detected that the server is redirecting the request for this address in a way that will never complete. This problem can sometimes be caused by disabling or refusing to accept cookies. ``` From the network tab in developer mode: ``` { "Status": "301", "Version": "HTTP/3", "Transferred": "601 B (0 B size)", "Request Priority": "Highest", "DNS Resolution": "System" } { "Response Headers (601 B)": { "headers": [ { "name": "alt-svc", "value": "h3=\":443\"; ma=86400" }, { "name": "cf-cache-status", "value": "DYNAMIC" }, { "name": "cf-ray", "value": "9238f8f388a58ade-AMS" }, { "name": "content-type", "value": "text/html; charset=utf-8" }, { "name": "date", "value": "Thu, 20 Mar 2025 23:26:05 GMT" }, { "name": "location", "value": "https://auth.example.com/if/flow/initial-setup/" }, { "name": "nel", "value": "{\"success_fraction\":0,\"report_to\":\"cf-nel\",\"max_age\":604800}" }, { "name": "report-to", "value": "{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report\\/v4?s=z%2BBPLWp3UMq5rdCOq%2BWYqJtSM%2FgLvCNmlu%2FJbXnJ7bN7Y8rjhRzhmtv2Rf5leRUNw47QZV2IrswfzDBMTCr5aN6kxJ8DxSraBiJdkAJ9grgShpCf7j23DOvTcG2mgoaIzkA5%2F2QGCAjqtitGUIU%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}" }, { "name": "server", "value": "cloudflare" } ] } } ``` And just before that message/row: ``` { "Status": "301", "Version": "HTTP/3", "Transferred": "599 B (0 B size)", "Request Priority": "Highest", "DNS Resolution": "System" } { "Response Headers (599 B)": { "headers": [ { "name": "alt-svc", "value": "h3=\":443\"; ma=86400" }, { "name": "cf-cache-status", "value": "DYNAMIC" }, { "name": "cf-ray", "value": "9238f8f368a38ade-AMS" }, { "name": "content-type", "value": "text/html; charset=utf-8" }, { "name": "date", "value": "Thu, 20 Mar 2025 23:26:05 GMT" }, { "name": "location", "value": "https://auth.example.com/if/flow/initial-setup/" }, { "name": "nel", "value": "{\"success_fraction\":0,\"report_to\":\"cf-nel\",\"max_age\":604800}" }, { "name": "report-to", "value": "{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report\\/v4?s=g9o%2Fcdaqo54et2be5pzzc0U9uiHLuE8858m0TJ9v1obe7SnNt%2BPUeO5jelaOy%2F9zEtGvGhJKYEMIwkjezJh%2FEJB1KdSd9rPCbSKfqoI1jUBYLcQwUDN9slVBdFxi8Bhgull9GHZDP0kWpeIZyqg%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}" }, { "name": "server", "value": "cloudflare" } ] } } ``` Screenshot of that window: <img width="997" alt="Image" src="https://github.com/user-attachments/assets/a161f73c-f195-4b35-922f-34832487a9a9" />

adam commented

@reddwarf666 commented on GitHub (Mar 21, 2025):

And Godoxy just went crazy active and weird, have to restart that service:

@reddwarf666 commented on GitHub (Mar 21, 2025): And Godoxy just went crazy active and weird, have to restart that service: <img width="1196" alt="Image" src="https://github.com/user-attachments/assets/264bda4b-b2c1-497b-898a-d8e9d7dea284" />

adam commented

@yusing commented on GitHub (Mar 21, 2025):

A few more questions:

Which version of GoDoxy are you running?
Could you share these files so I can see where those problems came from? compose.yml, .env, config/config.yml

@yusing commented on GitHub (Mar 21, 2025): A few more questions: - Which version of GoDoxy are you running? - Could you share these files so I can see where those problems came from? `compose.yml`, `.env`, `config/config.yml`

adam commented

@reddwarf666 commented on GitHub (Mar 21, 2025):

I can in a moment, restarted the whole server.
And I have no issues sharing but I would rather send everything to you personally then here.
Does github have a message feature?

Edit: GoDoxy version v0.9.9-1

@reddwarf666 commented on GitHub (Mar 21, 2025): I can in a moment, restarted the whole server. And I have no issues sharing but I would rather send everything to you personally then here. Does github have a message feature? Edit: GoDoxy version v0.9.9-1

adam commented

@yusing commented on GitHub (Mar 21, 2025):

DM me on discord yusing#1154

@yusing commented on GitHub (Mar 21, 2025): DM me on discord yusing#1154

adam commented