Hi all,
As the title suggests, I’m trying to run an ejabberd (xmpp) server behind an nginx reverse proxy. The reason is, I want to be able to run the server on my raspberry pi at home, but have people connect to it through my VPS, which is running nginx. This would be nice because I don’t need a static ip and I don’t have to leak my ip address.
I have looked this up, but have not found an answer that works exactly for my use case.
My current nginx configuration looks like this:
stream {
upstream xmppserver {
server 10.8.0.3:5223;
}
upstream turnserver {
server 10.8.0.3:3478;
}
map $ssl_preread_alpn_protocols $upstream {
"xmpp-client" xmppserver;
"stun.turn" turnserver;
"stun.nat-discovery" turnserver;
}
server {
listen 6969;
proxy_pass $upstream;
proxy_protocol on;
}
}
And I have a DNS entry telling XMPP clients to contact my server at port 6969 (this was just for testing):
I would also need to figure out how to supply ejabberd with the correct certificates for the domain. Since it’s running on a different computer than the reverse proxy, would I have to somehow copy the certificate over every time it has to be renewed?
Thank you for your help.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System HTTP Hypertext Transfer Protocol, the Web IP Internet Protocol SSL Secure Sockets Layer, for transparent encryption TLS Transport Layer Security, supersedes SSL VPN Virtual Private Network VPS Virtual Private Server (opposed to shared hosting)
6 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #136 for this sub, first seen 13th Sep 2023, 15:05] [FAQ] [Full list] [Contact] [Source code]
Adding Wikipedia page links would make this bot much more useful for those that need this information 🤔