-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nginx + Docker subfolder configuration #11460
Comments
For me this works:
|
And my docker-compose.yml
|
Thank you @angusvb! Will try this. |
@angusvb Thank you, this worked for the most part. I had to also add:
into the Nginx config to get file uploads working properly (and to not further modify Rocket chat's code). |
@olegberman thx, that is the part that I was still figuring out! |
@angusvb thanks for posting your config, got me off the ground! |
@angusvb This saved my day, thanks a lot for sharing! 🙏 |
Description:
Not able to get Rocket.chat to work in a subfolder
https://domain.com/chat
with Docker + Nginx. Can anyone possibly share their working configuration?Expected behavior:
Chat to load as usual.
Actual behavior:
These are errors that I'm getting (this is the closest I got to get it running):
Server Setup Information:
Configs
nginx.conf
Additional context
Hosting on the subdomain working just fine!
Now it looks like Rocket.chat tries to call
/api
path, and I can't add the same hack aslocation /sockjs {
as I have an API for a different app there. It should be calling/chat/api
and/chat/sockjs
ideally.Here is more configuration from MongoDB:
I also tried updating these values
CDN_PREFIX
andSite_Url
, and changing around the nginx config but nothing helps. Has anyone managed to get Docker+nginx+sudomain combination working?P.S. I've read through #2655, #4546, #8487 and none of these provide a solution.
Also I read https://rocket.chat/docs/installation/manual-installation/running-in-a-sub-folder/
and https://rocket.chat/docs/installation/manual-installation/configuring-ssl-reverse-proxy/
The text was updated successfully, but these errors were encountered: