[bug]: Can't Sing Up Right After Setting Up Instance

[betterthanever2]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current behavior

I have set up a self-hosted instance via Docker, first using the official shell script, then modifying the docker-compose.yml file to fit my setup.

Specifically, I disabled db and proxy because I'm using something else for both.

Now I'm at a point when the instance is up and running, has successfully finished db migration, and can be accessed at the dedicated hostname. However, when I try to sign up, I only get 404 response to the request to auth/email-check/

In the logs, I can see this line (that may or may not be related to the issue): Failed to check bucket: An error occurred (400) when calling the HeadBucket operation: Bad Request. I'm assuming this is about the minio part of the setup, but not sure what might be the cause. I'm not seeing anything about login/signup attempts.

One other issue I faced during the installation, is that when I start the docker process, I am warned that a number of env variables are not set - basically, the entire set of var defined in the x-app-env block unless they have default values defined. This is strange, because I added env_file: plane.env line, and that file contains all the necessary stuff. I had to explicitly define these via defaults right in the compose file.

And while I'm at it, I'm a little confused about these env vars. What is the difference btw PGDATABASE and POSTGRES_DB? What should be the values for ADMIN_BASE_URL, SPACE_BASE_URL and APP_BASE_URL?

Steps to reproduce

This happens during setting up the instance.

Environment

Production

Browser

None

Variant

Self-hosted

Version

v0.22dev