[bug]: Rabbit password variable in plane.env doesn't work (RABBITMQ_PASSWORD)

[dassels]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When I change value in plane.env for RABBITMQ_PASSWORD to non-default value, "Waiting for API Service to Start" goes into loop.

Expectation: Startup should complete.

It seems like there is no way to change the default passwords in .env file, and only defaults can be used.

Steps to reproduce

1. Set password in plane.env for RABBITMQ_PASSWORD to non-default value.
2. Starting container results in this error:

api-1  |   File "/usr/local/lib/python3.12/site-packages/amqp/connection.py", line 668, in _on_close
api-1  |     raise error_for_code(reply_code, reply_text,
api-1  | amqp.exceptions.AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.

3. Set AMQP_URL to AMQP_URL=amqp://${RABBITMQ_USER}:${RABBITMQ_PASSWORD}@${RABBITMQ_HOST}:${RABBITMQ_PORT}/${RABBITMQ_VHOST} (similar to what's described in issue: [bug]: variable in plane.env doesn't work (POSTGRES_PASSWORD, SECRET_KEY) #4749 to see if that fixes it).

New error shows, similar to error in issue 4749

api-1  |   File "/usr/local/lib/python3.12/site-packages/kombu/utils/url.py", line 70, in url_to_parts
api-1  |     parts.port,
api-1  |     ^^^^^^^^^^
api-1  |   File "/usr/local/lib/python3.12/urllib/parse.py", line 182, in port
api-1  |     raise ValueError(f"Port could not be cast to integer value as {port!r}")
api-1  | ValueError: Port could not be cast to integer value as 'sw.H'

Environment

Production

Browser

Mozilla Firefox

Variant

Self-hosted

Version

v0.24.1

[akshat5302]

Hey @dassels, could you please try setting up the password without any special characters or symbols and see if that resolves the problem?

[dassels]

I tried as you said, using just numbers and letters and the startup process was able complete. Thank you. This also worked for the postgres password change as well, so we are able to change it too.

If the parser is not able to handle special characters, perhaps a note in the docs notifying users to limit password to letter and numbers only will help out users during install.

[YashRaj1506]

@dassels @akshat5302 I think it is not related to using special characters as a password, i checked it locally earlier when i changed my plane/.env RABBITMQ_PASSWORD to "Pl@n!", I was also getting the same errors as @dassels showed above, but later after playing around a bit i realised that RABBITMQ_PASSWORD are present in two .env's. Other one is in plane/apiserver/.env, Now when we put the same password at both places then the projects works totally fine.