makeplane / makeplane/plane

[bug]: Serve on URL path

Open
#8,168 0 comments 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Nov 24, 2025.

🐛bug
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior

I am trying to serve Plane on a path, but all resources use the root rather than prefix.

For example: I am trying to serve on http://example.com/plane, traffic indicates resources are trying to be drawn from http://examples.com/_next/static.

I would expect that after configuring ingress, that the /plane prefix would be followed.

I did check out https://github.com/makeplane/plane/issues/7003 which led me to this config for docker compose where it looked like I could configure the NextJS base URLs:
https://github.com/makeplane/plane/blob/ac5b974d673b278a3770318f8546be269b65f5e2/web/Dockerfile.web#L79-L101

However, setting those in the environment of values.yaml didn't change anything.

I'm reasonably certain my Ingress is configured properly because I see the 404 error page when navigating to http://example.com/plane/god-mode, but the traffic shows its still being directed to http://example.com/god-mode

I can find hacky ways to route this properly, but I was wondering if there is a better approach using configuration instead.

Steps to reproduce
  1. Install helm repo
  2. Set up Ingress to serve Plane on /plane
  3. Navigate to /plane, and page is not served
Environment

Production

Browser

None

Variant

Self-hosted

Version

v1.1.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.