[bug]: Admin service redirect broken on fresh install to microk8s

[dev-null-2007]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When accessing /god-mode through an ingress/reverse proxy, as with hitting the "Get Started" button on a new install, the admin service issues a 301 redirect to hostname:3000/god-mode/ (with its internal listening port appended), causing an ERR_CONNECTION_REFUSED since port 3000 is not externally accessible.

This is on a new self-host instance, installed on microk8s using helm with the makeplane/plane-ce-1.4.1 chart, showing app version 1.2.0. Note that while I am still currently running an nginx ingress, I plan to migrate to traefik in the near future, so for me at least this might hopefully be a non-issue before too long.

Suspected root cause (per Claude):

The admin pod's nginx listens on port 3000 without port_in_redirect off, so trailing-slash redirects (e.g. /god-mode → /god-mode/) include the internal port in the Location header. The standard ingress-level fix for this — injecting port_in_redirect off or a rewrite rule via nginx.ingress.kubernetes.io/configuration-snippet — is unavailable when snippet annotations are disabled, which is the default in current ingress-nginx versions (disabled following CVE-2021-25742).

Steps to reproduce

1. Deploy Plane CE via Helm on microk8s using ingress-nginx with snippet annotations disabled (the current default)
2. Navigate to the Plane homepage
3. Click "Get Started"
4. Observe 301 redirect to hostname:3000/god-mode/ and subsequent connection failure

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.2.0

[dev-null-2007]

I've removed some assumptions in the title and description about the problem being related to the admin pod relying on ingress configuration snippets; took a deeper look and that doesn't appear to be the case. I'm not certain how it's supposed to work or why it's not working in my configuration, just that the straightforward way to fix it - nginx ingress configuration snippets - isn't working.

[akshat5302]

Hey @dev-null-2007, which ingress controller are you using? We’ve tested this with ingress-nginx and Traefik, and it works fine on both.

The ingress controller automatically adds a trailing slash if it’s missing. So /god-mode becomes /god-mode/.

Could you try accessing it with the trailing slash explicitly added?

https://plane-domain/god-mode/

[Vansh5632]

Hey, I have raised a fix you can check that out and guide me through that

PR: #8826

[dev-null-2007]

Hey @dev-null-2007, which ingress controller are you using? We’ve tested this with ingress-nginx and Traefik, and it works fine on both.

The ingress controller automatically adds a trailing slash if it’s missing. So /god-mode becomes /god-mode/.

Could you try accessing it with the trailing slash explicitly added?

https://plane-domain/god-mode/

Hi @akshat5302, thanks for the response, I am using nginx-ingress.

To test, I spun up a second instance in a new namespace, and confirmed it exhibits the same problem (redirect to port 3000). Running curl -v http://plane2.mydomain/god-mode/ does seem to work properly - likely because it doesn't wind up getting a 301 redirect.

FWIW, @Vansh5632's fix looks like it should work in my case, though I can't say whether it might cause unintended consequences in other configurations.

Thank you!