riazosama commented 2 months ago

Description

I recently deployed the "Plan" service and modified the domain settings. While the service works fine in general, I'm encountering an issue during the onboarding process. When creating a new account, the onboarding flow incorrectly redirects to the old domain that was automatically generated by Coolify. This domain is not secure, and when I try to visit it, I receive a 404 "Page Not Found" error after clicking "proceed anyway."

Additional Information:

This issue also affects users who are invited to the "Plan" service. When they are redirected to the onboarding route, they are sent to the old Coolify-generated FQDN, which is insecure and results in the same 404 error.
A similar behavior occurs when deploying the service via Docker Compose. The setup includes two services with SERVICE_FQDN_SERVER and SERVICE_FQDN_WEB environment variables. While the deployment allows access to the frontend via the custom domain assigned through the Coolify dashboard, the old FQDN still causes problematic redirects leading to the 404 error.

Minimal Reproduction (if possible, example repository)

Deploy the "Plan" service and modify the domain settings.
Attempt to create a new account during the onboarding process.
Observe that the redirect takes you to the old domain generated by Coolify.
Click "proceed anyway" on the security warning.
Notice that it results in a 404 "Page Not Found" error.

Exception or Error

No response

Version

v4.0.0-beta.323

Cloud?

[ ] Yes
[X] No

RyanB28 commented 2 months ago

Same error with the WordPress Services

vinicius507 commented 2 months ago

Same here with Plane. Any workaround? Tried checking out the compose file and it declares a x-app-env that seems to not be used at all?

For now I'm trying to set SERVICE_FQDN_PLANE to a hardcoded value.

TMBL-DEV commented 1 month ago

same issue i even checked if i could find it in the db, but no luck.