💾 Archived View for station.martinrue.com › mp0 › f24ca101d3a74c30a8d7cc344f7d4abc captured on 2023-11-14 at 10:59:57. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-11-04)

➡️ Next capture (2023-12-28)

🚧 View Differences

-=-=-=-=-=-=-

👽 mp0

Returned to my old plans of getting self-hosted xmpp server in my home network. Configured Prosody behind NAT with port forwarding. Got one quite strange bug: clients can connect from outside of home network, but can't connect from home network due to SSL error.

2 months ago

Actions

👋 Join Station

6 Replies

👽 mp0

Just for history: solved the problem by changing the router to the one which can be flashed with OpenWRT. I have prosody xmpp server now! · 2 weeks ago

👽 tm85

@mp0 Thanks for the guide. As for your question, you can accomplish the same thing by using the device's IP address as the hostname the cert. For security reasons (internal IP address leakage), you might want to use a separate SSL cert for access from your LAN. · 2 months ago

👽 mp0

@tm85 My setup is based on this manual: https://landchad.net/prosody/ · 2 months ago

👽 mp0

@tm85 - yes, it looks like some error with passing hostname when connecting from local network. I'm wondering if it possible to setup default hostname for IP connections · 2 months ago

👽 tm85

By the way, could you drop me your prosody conf? I've been pretty unsuccessful in configurikg it myself · 2 months ago

👽 tm85

SSL certs are tied to a hostname. If you're connecting by IP address, whether locla or global, the certificate name check will fail · 2 months ago