upd: plane to v0.28.0 (with fixes)

[pozitp]

• Updated Compose to version v0.28.0.
• Reviewed the original plane repository and removed unnecessary command sections.
• Updated the proxy container.
• Updated the template for the environment because nginx is gone and has been replaced by Caddy.
• Removed the unnecessary domain variable.
• Added the full URL of the repository.
• Added proxy_config and proxy_data volumes as needed.
• Replaced "https" with "http" on CORS, as in the original Compose file.
• Removed the version because the plane requires the latest Compose file version.
• Updated the meta file to v0.28.0.
• Replaced rabbitmq_user with ${rabbitmq_user}.

I used this Compose file and environment on my production server, and everything is working correctly. There were no errors during the build, and there are no errors in the logs.

Edited: I tested the Base64 configuration on the preview site. Everything works correctly. The only thing is that you need to wait a while for everything to get ready.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	f2bb312

[Siumauricio]

I wonder why when I register I redirect to this route?

[Harikrishnan1367709]

[pozitp]

You need to wait some time to get everything up

[pozitp]

I wonder why when I register I redirect to this route?

I had the same issue when first deployed, but after fixes and multiple restarts, it suddenly disappeared (but I don't register new users) :)

I tried to determine what caused that problem, but ended up with nothing. After registration, everything redirects and works flawlessly, but registration itself does not. Maybe it's a Plane problem; otherwise, I don't know.

[MarkNLD]

I wonder why when I register I redirect to this route?

I have the same issue. After log-in, or when entering god mode, I am greated with a 404. Manually changing the URL to /god-mode/general/ "resolves" the issue.

[MarkNLD]

@Siumauricio the 404 bug already existed in current v0.27.1 - it should not stop us from updating. @pozitp actually replied that the bug seems to have become less permanent.

I am hoping that after updating to this version the 404 bug is completely resolved, and if not we can continu debugging it.

Also @pozitp would you be available to get us to Plane v1.0.0?

[MarkNLD]

Unfortunately updating to v0.28.0 failed @pozitp

4 containers are not starting, I see the following error:
django.db.utils.OperationalError: connection failed: FATAL: password authentication failed for user "aniyah.dibbert21"

I am also seeing now seeing the same issues as @Siumauricio

[MarkNLD]

I fixed the 404's in v0.28.0 by changing WEB_URL and CORS_ALLOWED_ORIGINS to include https:// instead of http://

Old:

WEB_URL=http://someurl.traefik.me
CORS_ALLOWED_ORIGINS=http://someurl.traefik.me

New:

WEB_URL=https://someurl.traefik.me
CORS_ALLOWED_ORIGINS=https://someurl.traefik.me

[MarkNLD]

@Siumauricio I believe this can be merged now

[Siumauricio]

When the user register, it redirects to https, and fails and shows this error

[MarkNLD]

Upon testing the latest fix I am also greeted with a 404 after initial set-up. I am redirected to https://test-plane-qoone2-13d9f0-94-142-246-193.traefik.me/god-mode/general

When checking my environment I am seeing different URL's:
APP_DOMAIN=test-plane-qoone2-c6d1e9-94-142-246-193.traefik.me WEB_URL=https://test-plane-qoone2-13d9f0-94-142-246-193.traefik.me CORS_ALLOWED_ORIGINS=https://test-plane-qoone2-66a173-94-142-246-193.traefik.me

No idea what's going on

[MarkNLD]

When I import v28, manually set the APP_DOMAIN, WEB_URL and CORS_ALLOWED_ORIGINS parameters to http the set-up works fine. No errors.

When I set it to https the CORS and 404 errors occur or Plane does not even start.

[pozitp]

When I import v28, manually set the APP_DOMAIN, WEB_URL and CORS_ALLOWED_ORIGINS parameters to http the set-up works fine. No errors.

When I set it to https the CORS and 404 errors occur or Plane does not even start.

so we actually got into the initial state? 😁 perhaps only setting app_domain with http can actually fix, but i'm not sure about that

[pozitp]

When I import v28, manually set the APP_DOMAIN, WEB_URL and CORS_ALLOWED_ORIGINS parameters to http the set-up works fine. No errors.

When I set it to https the CORS and 404 errors occur or Plane does not even start.

so we actually got into the initial state? 😁 perhaps only setting app_domain with http can actually fix, but i'm not sure about that

And no.

I reviewed this: https://github.com/makeplane/plane/blob/preview/deployments/aio/community/start.sh#L116.

It contains FQDN, not URL, so it won't actually help. As I said, redirects sometimes work and sometimes don't. And also we need to wait some time to get everything up. I will try updating to v1.1.0 and report back if it resolves the issue.

[DouglasAR01]

When I import v28, manually set the APP_DOMAIN, WEB_URL and CORS_ALLOWED_ORIGINS parameters to http the set-up works fine. No errors.
When I set it to https the CORS and 404 errors occur or Plane does not even start.

so we actually got into the initial state? 😁 perhaps only setting app_domain with http can actually fix, but i'm not sure about that

And no.

I reviewed this: https://github.com/makeplane/plane/blob/preview/deployments/aio/community/start.sh#L116.

It contains FQDN, not URL, so it won't actually help. As I said, redirects sometimes work and sometimes don't. And also we need to wait some time to get everything up. I will try updating to v1.1.0 and report back if it resolves the issue.

Did it solve the issue? 👀

[MarkNLD]

We managed to update to Plane v1.1.0 within Dokploy. What can I share for others to replicate it?