Post of happiness - Jabber on your server in 10 minutes
Publish to a personal blog - because there will not be a detailed description, instructions and other things.
This is just a post of happiness of a person who discovered Jabber for himself from the other side.
The bottom line is that I needed my Debian Jabber server with https connection for paranoid communication from the ICQ office.
From past experiments, I remembered that the Jabber server is complex, cunning and not always pliable without reading manuals.
')
But this time I decided to start not with eJabberd and others, but with
OpenFire .
Considering that I already had Java installed - I am not on friendly terms with it and just put apt-get-nuv all jre-and other packages - the installation was limited to downloading the .deb-package of OpenFire and dpkg -i - by installation.
You will not believe! He just took and established. No shamanism, no tambourines - that's how he took it and put it! (Next, I highlight bold keywords to navigate through this happy delirium)
It only took me once to read the manual to see a line like “I tune on port 9090”.
Distraction from the topic - my server is behind the router. In my case, I had to open ports - 9090 for the admin panel, 9091 for the https admin panel, 5222 for the zhabber itself, 7777 for file transfer, and went into the admin panel - ip_server : 9091
And again - a miracle! They managed to make the admin panel simple, understandable and friendly. As a DB, I chose MySQL - so the only unnecessary gesture was to have a separate user and database.
Setting up the server - a few clicks - admin password, small ticks - what to do to the server in what cases. I increased the size of the offline log and set up forced SSL. And, also included the ability to transfer files.
Thin moment - the name of the server - I had to edit the setting, changing from skazkinserver to domain.ru for digestible accounts.
ICQ Gate is easy to configure - please turn on the IM module ... wait ... Done, use it!
Modules, by the way, there is enough. Test support GTalk, - and the mass of the bourgeois type Gadugadu, AOL and so on. Just turn on and use.
Customization of users - do you want them to register themselves or with pens each? Maybe make a group? You do not want? Well, whatever you want!
Conveniently! Clear!
After the settings - /etc/init.d/openfire restart - and please! New account in Miranda-IM.
Post of happiness Post of happiness! Now I have my HTTPS Jabber server and ICQ-gate !!! :) Never before has server setup been so easy :)
UPD: Weeds that I ran into and fixed:
No clients were added - it was impossible to write to newly added ones - ICQ / other jabbers
1. Server settings-> Security settings - if there is no normal SSL certificate - Server Connection must be set to Optional and ticked below - Accept self-signed certificates. Server dialback over TLS is now available
2. Server To Server - set both items in Allowed - both about the server and about the clients
ICQ did not start the first time
Enable in Server-> Gateways, in the same place set the encoding in cp1251
The rest of the little things were decided by prescribing port redirects on the router.
Minor cons
UserInfo is not readable from the ICQ gate - well, there are no extended statuses: (Nothing, you can survive without it
This is just a post of happiness of a person who discovered Jabber for himself from the other side.
The bottom line is that I needed my Debian Jabber server with https connection for paranoid communication from the ICQ office.
From past experiments, I remembered that the Jabber server is complex, cunning and not always pliable without reading manuals.
')
But this time I decided to start not with eJabberd and others, but with
OpenFire .Considering that I already had Java installed - I am not on friendly terms with it and just put apt-get-nuv all jre-and other packages - the installation was limited to downloading the .deb-package of OpenFire and dpkg -i - by installation.
You will not believe! He just took and established. No shamanism, no tambourines - that's how he took it and put it! (Next, I highlight bold keywords to navigate through this happy delirium)
It only took me once to read the manual to see a line like “I tune on port 9090”.
Distraction from the topic - my server is behind the router. In my case, I had to open ports - 9090 for the admin panel, 9091 for the https admin panel, 5222 for the zhabber itself, 7777 for file transfer, and went into the admin panel - ip_server : 9091
And again - a miracle! They managed to make the admin panel simple, understandable and friendly. As a DB, I chose MySQL - so the only unnecessary gesture was to have a separate user and database.
Setting up the server - a few clicks - admin password, small ticks - what to do to the server in what cases. I increased the size of the offline log and set up forced SSL. And, also included the ability to transfer files.
Thin moment - the name of the server - I had to edit the setting, changing from skazkinserver to domain.ru for digestible accounts.
ICQ Gate is easy to configure - please turn on the IM module ... wait ... Done, use it!
Modules, by the way, there is enough. Test support GTalk, - and the mass of the bourgeois type Gadugadu, AOL and so on. Just turn on and use.
Customization of users - do you want them to register themselves or with pens each? Maybe make a group? You do not want? Well, whatever you want!
Conveniently! Clear!
After the settings - /etc/init.d/openfire restart - and please! New account in Miranda-IM.
Post of happiness Post of happiness! Now I have my HTTPS Jabber server and ICQ-gate !!! :) Never before has server setup been so easy :)
UPD: Weeds that I ran into and fixed:
No clients were added - it was impossible to write to newly added ones - ICQ / other jabbers
1. Server settings-> Security settings - if there is no normal SSL certificate - Server Connection must be set to Optional and ticked below - Accept self-signed certificates. Server dialback over TLS is now available
2. Server To Server - set both items in Allowed - both about the server and about the clients
ICQ did not start the first time
Enable in Server-> Gateways, in the same place set the encoding in cp1251
The rest of the little things were decided by prescribing port redirects on the router.
Minor cons
UserInfo is not readable from the ICQ gate - well, there are no extended statuses: (Nothing, you can survive without it
Source: https://habr.com/ru/post/58636/
All Articles