Setting up Twenty CRM on Unraid with Nginx Proxy Manager: Issues & Solutions
Hope this is okay, did get AI to essentially re-write my few hour long into a sorta concise format
Hey everyone! I recently set up Twenty CRM (the open-source CRM platform) on my Unraid server and ran into some issues, particularly with the reverse proxy setup. I wanted to share my experience and solutions to help others who might face similar problems.
Issues I Encountered
1. "Unable to Reach Back-end" / "Failed to fetch" Error
After setting up Twenty CRM and configuring Nginx Proxy Manager, I got the dreaded "Unable to Reach Back-end" error when trying to access Twenty through my subdomain.
Root cause: My docker-compose.yml had hardcoded URLs that were overriding the .env settings.
2. WebSocket Connection Failures
Even after fixing the URLs, I still had connection issues because Twenty requires WebSocket support for proper functioning.
3. Container Networking Issues
Twenty CRM's services weren't communicating properly with each other because of incorrect service references.
5 Replies
How I Fixed It
1. Fixed Environment Variables
I changed the hardcoded URLs in docker-compose.yml to use environment variables:
Changed this:
SERVER_URL: http://192.168.x.x:3000
FRONT_BASE_URL: http://192.168.x.x:3000
To this:
SERVER_URL: ${SERVER_URL}
FRONT_BASE_URL: ${FRONT_BASE_URL}
Then in my .env file:
SERVER_URL=https://my-crm-domain.com
FRONT_BASE_URL=https://my-crm-domain.com
2. Added WebSocket Support to Nginx Proxy Manager
In the Custom Nginx Configuration section of my proxy host, I added:
Basic headers
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
WebSocket support (critical for Twenty CRM)
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
Extended timeouts for API operations
proxy_connect_timeout 120s;
proxy_send_timeout 120s;
proxy_read_timeout 120s;
Additional headers for better compatibility
proxy_buffering off;
proxy_set_header X-Forwarded-Host $host;
#3. Fixed Container References
I ensured that internal container references used service names (db, redis) while external URLs used the actual domain.
My Working Configuration Files
Here are my sanitized working configuration files if anyone needs them, change to suit your enviroment. burt it gives a decent stepping stone.
Installation Steps
Create directories:
bash
mkdir -p /mnt/user/appdata/twenty/postgres_data
mkdir -p /mnt/user/appdata/twenty/redis_data
mkdir -p /mnt/user/appdata/twenty/storage_data
mkdir -p /mnt/user/appdata/twenty/docker_data
chmod 777 /mnt/user/appdata/twenty/postgres_data
chmod 777 /mnt/user/appdata/twenty/redis_data
chmod 777 /mnt/user/appdata/twenty/storage_data
chmod 777 /mnt/user/appdata/twenty/docker_data
Set permissions appropriately in each folder, i used 777 just for installation purposes. i will change it after to something more suitable. this is not security advice. just to get it working.
Create .env and docker-compose.yml with the contents above
Run docker-compose:
bash
cd /mnt/user/appdata/twenty
docker-compose up -d
Configure Nginx Proxy Manager with WebSocket support
Access your Twenty CRM at your configured domain
I hope this helps someone else! Let me know if you have any questions.
Thanks for this. To build on it I used the above plus chatgpt over the last few hours and got it up and runnign locally (not using NGINX just within my LAN). Here's a guide that might be helpful for others that I summarized with chatgpt.