Error 404 after commands
Hello,
after a new installation under docker i couldn't connect so i did the commands mentioned on the documentation but now i have a 404 error.
Before doing the commands I had the interfaces just I could not create accounts or connect.
and in the logs no errors
42 Replies
I think I've found the solution by modifying my docker-compose, so I'm posting it below in case I'm not the only one.
Personally I use coolify for deployment so I modified the docker-compose accordingly.
Here it is.
and yes I removed the "change-vol-ownership" part as well as the worker it was for my tests that I have not finished but I will update this conversation in the future
and yes I removed the "change-vol-ownership" part as well as the worker it was for my tests that I have not finished but I will update this conversation in the future
^ ty
I'm also using coolify
let me know when you have workers, etc working
👌
Good evening,
after more than 20 reinstallations of Twenty i finally made a docker-compose that works on coolify but a problem persists that of the "change-vol-ownership" that i can't fix but it works without and i don't know how important this party is but until i find the problem i put the new version HERE.
By the way on coolify there is already Twenty you just have to search for it but it hasn't been updated for a long time I don't know who should do this but it would be nice if it was done.
Similarly, when I re-import my backups, I have to recreate the data models by hand so that the data is put in the right columns, which is a bit silly in my opinion.
But once again, thanks to the coolify team for what they do 🙂
Bonne soirée.
Translated with DeepL.com (free version)
Hey man! This looks money- I want to do the exact same thing. Im gonna try this out later tonight.
I know this isn't Coolify-related but curious... is S3 storage required for Twenty deployment? Or is there some default local storage that Twenty offers?
After trying to run @Uranium 's docker-compose above in Coolify, I got an error about the Worker not properly running. Anybody got ideas here? I can't find any good logs for this
Im curious to know if every environment variable is required? Notably, the S3 and Google Auth variables? My hope was to get something working before I go the extra to create all of these values
HI @childishbenbino, twenty comes with two different file drivers at the moment. Local disk storage and S3 storage. By default, it's using local disk storage and storing on the machine. https://twenty.com/developers/section/self-hosting/self-hosting-var#storage
For production environment (espcially in a stateless architecture), I would recommend using S3. For a POC, you can use local
You don't have to set GOOGLE_AUTH and S3 to have the worker properly running. Could you share some logs?
Hello, hmm... i don't use S3 and irs works...
I send you my env soon i'm not at home
Thanks for the info @charles ! I'm currently in the POC phase, so I appreciate the local storage option.
I think the quirk here is the nuance in deploying on Coolify. I appreciate @Uranium future follow-up to see his .env setup.
And @charles , please take note of OP's comment about Coolify's Twenty resource being outdated! Not sure who's responsible for updating thsi
Attached is my compose file. You see that I removed all S3 and Google auth calls. I provide the values for I did as the default.
According to Coolify, the server and DB and running healthy, but the worker exited.
Hey,
@charles @childishbenbino
this is my .env
And I assume you have
Build variable?
checked for all of them in Coolify?no i don't have this checked
Interesting. @Uranium , looking at my compose file above, do you see anything off?
No, I don't particularly see any issues. However, the variable
${STORAGE_LOCAL_PATH:-.local-storage}
didn't work for me, even with special character escaping disabled. I had to replace it with $${STORAGE_LOCAL_PATH:-.local-storage}
. Yet, in the rest of the docker-compose file, it works fine. Nevertheless, Coolify still replaces certain lines, especially for the change-vol-ownership part, where the characters are always escaped, which prevents the container from starting.
I'll try your docker compose on my coolify instance
look i have the sam errorInteresting, let me try
and if i do no replace by this 2 lines
- 'server-local-data:/app/packages/twenty-server/$${STORAGE_LOCAL_PATH:-.local-storage}'
- 'docker-data:/app/docker-data'
this is not work
You running this on AWS? What are your VPS specs?
not aws just VPS,
OS: Debian 12
24G RAM
6 cores
but VPS is not the problem idk...
Yeah, I thought not.
Okay, I added the a second
$
, as recommended. Im going to try againokok
Damn, same thing
what is error ?
And the logs section is giving me nothing...
oh yes because the container is not start.
I go to Logs, hit "Refresh" on Worker, and it comes up blank
The Server and DB logs look healthy to me 🤔
can you try this ? this is my own docker compose and works for me.
just remove variables you don't need
But, will that break something lol
I'll remove all the GMAIL and GOOGLE envs
Impossible my first test is without GMAIL and GOOGLE and works...
hmm
i remove it
Is it okay if I set the SERVER_URL to http://localhost:3000?
yes but instance is on your desktop or VPS ?
VPS
An AWS EC2
Ohhhh...
you can test and go to http://ipofserver:3000/ if this is not work replace localhost by ip of server
but coolify will always cause problems I don't know why and it's annoying that you always have to debug.
coolify tell me my worker is (unhealthy) but when i run docker ps my worker is healthy...
Still unable to start the worker, after changing the local host path
Maybe I should try without Coolify...
Very weird that you don't have any logs, and your docker-file looks fine to me. Unfortunately I don't have any experience with coolify
Im running Coolify on a t2.medium EC2 (4gb memory)
https://discord.com/channels/1130383047699738754/1216007393729708182/1216012474705252532
^ im wondering if the server Im trying to run it on is so small that there's no chance
might be too small indeed to run the whole stack
Hello All, I installed Twenty with Docker, the problem is Gmail sync is not working, here is my env AUTH_GOOGLE_APIS_CALLBACK_URL=xxx.xxx/auth/google-apis/get-access-token
AUTH_GOOGLE_CALLBACK_URL=xxxx.xxxx/auth/google/redirect
AUTH_GOOGLE_ENABLED=true
CALENDAR_PROVIDER_GOOGLE_ENABLED=true
MESSAGING_PROVIDER_GMAIL_ENABLED=true