adam

joined 1 year ago
[–] adam@discuss.tchncs.de 1 points 11 months ago

I switched to fedora some months ago and I've been really enjoying it. Maybe worth a shot.

[–] adam@discuss.tchncs.de 0 points 1 year ago (1 children)

When did he ever talk about those things? Did I miss something?

[–] adam@discuss.tchncs.de 7 points 1 year ago* (last edited 1 year ago) (2 children)

That could be done after the user enters both the email/username and password

Edit: sorry, I think I misunderstood what you said, but if someone is using something like "sign in with google", we've had separate buttons for that for ages.

[–] adam@discuss.tchncs.de 11 points 1 year ago* (last edited 10 months ago)

No matter what I'm doing on my computer, I'll always hide it when someone enters my room

[–] adam@discuss.tchncs.de 1 points 1 year ago

I already have a constant ip on the vpn I still don't get it, sorry

[–] adam@discuss.tchncs.de 1 points 1 year ago (2 children)

How would I use that in this situation? I don't get it. I already have a vpn set up to communicate between the two devices, and have been successfully running multiple services in this configuration for about a month. It's just XMPP that I'm having trouble with.

[–] adam@discuss.tchncs.de 1 points 1 year ago (4 children)

The vps communicates with the rpi through a vpn.

I have not heard of duck dns nor lstio, but I'll check it out when I get home.

 

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.