SELF HOSTED Unable to Reach back-end.
HI Y'all I am new to Twenty CRM trying to see if it would work for our use cause. I recently insalled the docker compsoe 1-click installation(yesterday) and I was getting Unable to Reach back-end the whole day tryed everything could't get it working eventully i delted everything for the 3rd time and reinstalled it and then it was working for me, loged in and can play around, then when i shared it with my colleagues to test they now keep gettting Unable to Reach back-end , so i don't quite understand why.
I am using an old pc with unbuntu on it as a server, with the Latest version of docker and twenty, how do i reslove this problem, I don't see anything on the forms about it I did go through the docker trouble shooting doc but don't really see anything there that i think would work.
appreciate any help. Cheers

17 Replies
Hello there, please share twenty-server container logs
now mine is showing Can't Reach Back-end as well
heres my server logs
Logs look ok, please share your obfuscated
.env
what is this obfuscated?
heres my .env
TAG=v1.1.1
#PG_DATABASE_USER=postgres
#PG_DATABASE_PASSWORD=replace_me_with_a_strong_password_without_special_characters
#PG_DATABASE_HOST=db
#PG_DATABASE_PORT=5432
#REDIS_URL=redis://redis:6379
SERVER_URL=http://localhost:6060
Use openssl rand -base64 32 for each secret
APP_SECRET=replace_me_with_a_random_string
STORAGE_TYPE=local
STORAGE_S3_REGION=eu-west3
STORAGE_S3_NAME=my-bucket
STORAGE_S3_ENDPOINT=
=== Randomly generated secret ===
APP_SECRET=**
PG_DATABASE_PASSWORD=**
SERVER_URL=http://localhost:6060/Are you able to hit your server from this url ? Please remove trailing slash
my actully .env file doesn't have the trailing / it was added when i pasted it into chat
I use my server ip with port 6060, but it's a local server,
Please try scoping the issue to either the server or the front.
Server logs looks ok
Front does not seem to hit the server at all -> means front configuration could be wrong
Try hitting your server from its exposed url directly ( using postman or curl ) to determine what it's exactly
192.168.*.** is:6060 so it's pointing to localhost I can ping the server when i am ssh' into my server as well
When you're on the server only, does not mean it's exposed by the server to the local network
I am changeing my url from local host to my server ip. but heres what i got from my curl
http://192.168.8.223:6060
this should be your SERVER_URL
The server returns the front too, what's your curling here is the spa initial index.html
-> "REACT_APP_SERVER_BASE_URL": "http://localhost:6060" That's not goodjust changed the url to that, and it works like a charm
Cool !
thanks for your help, and apoalgies for being a. rockie😭 😂
No worries my pleasure you did great
Have a nice day
and you too