Unable to Reach Back-end
Hello, I'm encountering the issue "Unable to Reach Back-end" while accessing my app.
Installed using docker compose, using reverse proxy with nginx, I configured the SERVER_URL in the .env for that
Running on Ubuntu 24.04
I have absolutely no errors in logs in twenty-server-1 / twenty-worker-1 / twenty-db-1 and twenty-redis-1, I can provide screenshots if needed.
When I try to access to URL/graphql, I got
{"errors":[{"message":"Must provide query string."}]}
And on the front-end, I see briefly the app with the login pop-up before seeing the "Unable to Reach Back-end" on /welcome after 1 second
Thank's in advance
36 Replies
Hello what twenty version are you running please ?
Do you have any logs such as cors errors in your browser console ?
Let me check
I don't know how to find the version I'm using, but I downloaded it yesterday following the doc with
bash <(curl -sL https://raw.githubusercontent.com/twentyhq/twenty/main/packages/twenty-docker/scripts/install.sh) so I'm assume I've the latest oneecho $APP_VERSION in your twenty-server or have a check to your .env TAG env var
1.0.2
Are the complete error logs in the browser:
URL/graphql, I got {"errors":[{"message":"Must provide query string."}]}I have this when I try to access myurl/graphql
Please inspect a graphql req from the network tab looking for errors field in the response body
Yes that's expected please what's the response body of one of them
:/
Even when refreshing the tab with opened console network tab ?
Yup
For the 4 different ones
Might be coming from
using reverse proxy with nginx
Do you see any logs on the twenty-server container ? -> that would result from a successfully hitting reqNop, nothing
Last logs from yesterday after the start
{"errors":[{"message":"Must provide query string."}]} I don't think this error is generated by twenty-serverNothing in twenty-worker neither
Please try to reproduce with a basic vanilla one click install instance in order to start debugging your other one
Sure, can I change the 3000 port to run both at the same time or should I stop the actual one while setting up the new ?
nvm I can choose in the install
Can't start the installation
Please inspect server logs
And the installation killed my other twenty-server and twenty-db containers to create new ones
I think at this point I'm just gonna remove both installations and create a new fresh one
And see how it goes from there
Yeah you need the remove previous volumes
Actually I have removed and deleted all previous containers and volumes, start back from a new installation and I have the same error with the database
Since it's a fresh installation, can't figure out why it's not working
I think the old database is not completely deleted, but since I used docker prune and delete volumes, idk why
you need to docker compose down -v
Yeah I just find the hidden volumes and deleted it
Okay so, new fresh install, no reverse proxy, I acceed from my vanilla IP URL, and still the same issue
But this time, at the end of the installation, I got this :
But the server is running, and I checked the logs and see no errors
Does Twenty support installation via Coolify or not?
Up
You can find several self hoster that are deploying twenty on Coolify yes
What was the final thing that helped with the localhost issue?
do you know of a new coolify docker script? Every one I test seems to crash
I'm sorry but I don't it's community maintained