-
hokori696
Hey, I'm trying to install my XMPP server on a Raspberry Pi but it don't work...
-
vanitasvitae
which server?
-
hokori696
Prosody
-
vanitasvitae
and what "doesn't work"?
-
hokori696
Well
-
hokori696
I can't connect to it
-
vanitasvitae
is it running?
-
hokori696
I think yes
-
vanitasvitae
do you have a firewall?
-
vanitasvitae
is dns configured?
-
hokori696
When a make a restart I get that:
-
hokori696
[ ok ] Restarting prosody (via systemctl): prosody.service.
-
vanitasvitae
you could ask in the prosody dev room. Maybe they can help? (not a prosody user)
-
hokori696
How can I go there ?
-
vanitasvitae
xmpp:prosody@conference.prosody.im?join
-
hokori696
And sorry, but how can I configure the DNS?
-
vanitasvitae
well, if you want to connect to the server from "outside" of your network (i.e. not your local lan) you have to enable port forwarding in your router and configure dynamic dns in case you dont have a stable IP address.
-
vanitasvitae
here is a guide that should cover everything you need: https://jacksonjs.github.io/2016/09/09/prosodyonpi/
-
Link Mauve
vanitasvitae, it’s a bad idea to suggest self-signed certificates to beginners (or to anyone really).
-
Link Mauve
This guide also uses the ssl option, which has been deprecated in recent versions of Prosody.
-
Link Mauve
And the legacy non-systemd way of starting services.
-
vanitasvitae
it was the best I found in 2 mins 😛
-
vanitasvitae
if you have a better guide, hokori696 is still here 😛
-
Link Mauve
It’s bad, you shouldn’t link it.
-
Link Mauve
At least, not without checking that it is better than nothing.
-
Link Mauve
https://homebrewserver.club/configuring-a-modern-xmpp-server.html is the guide we recommend for a modern Prosody.
-
vanitasvitae
hokori696 ^
-
hokori696
Yep sorry
-
hokori696
I already enable port forwarding
-
hokori696
And i followed this tutorial for xxmp installation http://raspberrypi.tomasgreno.cz/xmppjabber-server.html
-
hokori696
xmpp*
-
Link Mauve
Eww, suggesting Pidgin. :x
-
hokori696
😁
-
MattJ
Yeah, 99% of guides for Prosody are terrible
-
MattJ
and I grew to realise this is just true for 99% of all guides for all software setup
-
pep.
Yes. I keep failing at understanding what people like in unofficial documentations
-
MattJ
Well, I know that for Prosody we don't actually have any guide/tutorial-based content right now
-
MattJ
In general I think the problem is that guides are either written by developers who know the project too well to make a decent guide, or they are written by random people who wrote the guide while learning how to set it up themselves
-
MattJ
The good guides are in the middle
-
Holger
The other problem is that even the good guides are usually not kept up-to-date.
-
MattJ
That too
-
Ellenor Malik
> Link Mauve has written: > And the legacy non-systemd way of starting services. So apparently all operating systems which are not Linux are now legacy. You should be ashamed of yourself.
-
Link Mauve
Ellenor Malik, why? And how do you infer that?
-
Ellenor Malik
systemd absolutely requires Linux, and you are calling any way of starting prosody that does not involve systemd legacy.
-
Link Mauve
Ellenor Malik, this guide is for some Debian (derivative?) running on a Raspberry Pi, it doesn’t preclude other guides being written for other platforms.
-
Link Mauve
But on Debian, it can create actual problems to mix and match methods to start Prosody.
-
Link Mauve
We’ve seen users wonder why no changes were applied, only to realise they had two instances of Prosody running due to this issue.
-
Ellenor Malik
Underscoring the importance of PID files.
-
Link Mauve
Or, you know, using your init system to manage its services.