3 ms·
How would I actually go about doing this? By default I can see that the process binds to localhost:8443, which is not accessible via other devices. Running the
by Natfan 6y ago
How would I actually go about doing this? By default I can see that the process binds to localhost:8443, which is not accessible via other devices. Running the following command doesn't seem to work either:
galene -http 0.0.0.0:8443
Using a nginx server as a reverse proxy, I have the following that works for HTTP but not WebSocket:
server {
server_name galene.domain.com;
location / {
proxy_pass https://127.0.0.1:8443/;
proxy_set_header Host $host;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/natfan.io/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/natfan.io/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
Thoughts? Happy to move this to Github if that's easier too.
- jech 6y agoBy default, we bind to ":8443", which is Go's notation for port 8443 on all IP addresses, IPv4 and IPv6. Galène's WebSocket is located at /ws, and I believe that nginx requires that you configure this specially. See https://www.nginx.com/blog/websocket-nginx/ https://www.nginx.com/blog/websocket-nginx/. An alternative to reverse proxying is to use HTTP redirects: you can define a group as {"redirect":"https://otherserver.example.com:8443/group/groupname https://otherserver.example.com:8443/group/groupname"} and Galène will send an HTTP redirect whenever somebody attempts to join this group. I'll be glad to continue this conversation on the mailing list (https://lists.galene.org/postorius/lists/galene.lists.galene.org/ https://lists.galene.org/postorius/lists/galene.lists.galene...).