-
-
Notifications
You must be signed in to change notification settings - Fork 77
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 template for proxy management? #213
Comments
There is no special configuration needed for serving user content. It’s just plain files which can be served with any web server, including Nginx. Just point the server to the directory you’ve configured in |
Thanks, I'm on Keila again and it seems to be super improved! Tried to use Nginx with docker-compose and it run but when I try to compose a new campaign:
Please, can you suggest how to enable this connection within the proxy? I tried to proxy the path to keila localhost exposed container but it didn't work. |
Hey @satoshinotdead, you can find more details about setting up Nginx as a websocket proxy on the Nginx blog: https://www.nginx.com/blog/websocket-nginx/ The important bit is this bit in the location config which allows the browser to request an upgrade from a normal request to a Websocket:
|
Hi there! I tried this config before posting but it don't work:
And tried to proxy the /live/websocket location but it seems that's not the way to configure it and of course, didn't work too. Do you know what I'm missing here? Thanks for your following up :) |
Are you seeing anything in the nginx or in the Keila logs? Did you make sure to restart/reload nginx after updating your settings? |
I only see 403 forbidden console errors and this messages on logs: Nginx reverse proxy (hosted on server)
Keila Docker container
I pruned containers and volumes, restarted and force-recreated but the issue persists. I suspect we need to tweak a little bit the Nginx template. I will look into this and update if I find a solution. |
Did you maybe not set the |
... or maybe you are missing the |
Tried localhost (127.0.0.1) and the https proxied and that was the same.
Tried changing |
So you are trying to access Keila on localhost? If you are using a domain such as |
Well, I'm using reverse proxy from Nginx so URL_HOST can be localhost (routed by Nginx from external internet, using the port locally exposed). BTW I tried with our host (mail.domain.com) too but the wss socket issue persists. |
No, it can’t be |
Fair enough, checked (3 times). It's not working with I will update if I found something. |
I hope you find a solution for your setup! Please keep up updated here in this issue in case someone else ends up having the same issue 😊 |
Have you found the solution?
|
[EDIT] @Marthaarman no, I didn't find a solution. We are currently on #333 :) |
I wonder if someone can share their template to upstream Keila without exposing totally and only at localhost.
There are specific configurations that could fits well with Keila itself and not with another apps.
Kudos for great development! 🙏
The text was updated successfully, but these errors were encountered: