![]() ![]() On approved request, remote contact will display in your chat list.įinally, You can start messaging between both accounts. When remote user approve or reject your request, eJabberd notify you the status of your request. Now, add other account from Actions > Add Contact menu options. Now start Gajim (from non root account) and login to Gajim on both systems with different-2 user accounts. Use following command to install Gajim two systems. ![]() For this example we will use Gajim xmpp client, You may also use other alternatives like Pidgin etc. Now install a XMPP client on your system. So first of all create two user accounts in our virtual host as per showing in below image. To verify setup we will use XMPP client and login with two different users and then try messaging between them. If you have access ejabberd through localhost, then input login details of localhost admin account as created in above step. Input admin username and password of host im. as shown above. Access access your domain on port 5280 followed by /admin $ sudo service ejabberd restartĮJabberd admin web panel start on default port 5280. "im." Access eJabberd Web PanelĪfter making all above configuration, let’s restart eJabberd service using following command. Now edit ejabberd configuration file /etc/ejabberd/ejabberd.yml in text editor and add acl for admin user for im. $ ejabberdctl register admin im. password $ ejabberdctl register admin localhost password Below commands will create admin accounts for both virtual hosts localhost and im. Now you need to create admin accounts for your domain. So at first I make a host file entry to map im. with eJabberd server ip address. You may only use localhost for you local system, but for remote server use a domain or sub-domain. $ sudo apt-get install ejabberdįor this installation we are using domain im. in configuration. ![]() This will also installed Erlang programming language packages. You just need to use run below commands to install eJabberd packages. See the Jabber SPAM Manifesto for details:īut when I try to create room or send_message to a specific room, I always get 403 error (for access denied).EJabberd packages are available under default system repositories. # Think twice before enabling registration from any # network (see access_rules section above). # Only accept registration requests from the "trusted" # Avoid buggy clients to make their bookmarks public Uncomment this when you have SQL configured:Īccess_max_user_messages: max_user_offline_messages # For small servers SQLite is a good fit and is very easy So, maybe some of the problems and annoyances you found in 2.0.1 are solved in 2.0.5 or will be solved in 2.1.0. And there will be many improvements in ejabberd 2.1.0 once released. # Mnesia is limited to 2GB, better to use an SQL backend There were many bugfixes related to PubSub in ejabberd 2.0.x releases after 2.0.1. #ca_file: "/etc/letsencrypt/live/localhost/fullchain.pem" # - /etc/letsencrypt/live/localhost/privkey.pem # - /etc/letsencrypt/live/localhost/fullchain.pem # When using let's encrypt to generate certificates Here is the ejabberd.yml for the production environment : default_db: sqlĮxtauth_program: "PATH_TO_EXTERNAL_SCRIPT_AUTH"Ĭa_file: "/home/ejabberd/conf/cacert.pem" On my local PC, everything works because ejabberd is installed on the same PC. I'm currently trying to configure ejabberd to allow the admin user to execute commands from remote ip address. ![]()
0 Comments
Leave a Reply. |