Tag Info

Hot answers tagged

6

One word: ejabberd. No web interface though and docs suck at large.


5

It would be best to see your actual configuration, but MUCs normally have to be enabled as services. The service discovery is indeed the way to discover the MUC service and browse chat rooms, but the client should be able to bookmark them or put them on the roster for use next time. Anyway, in /etc/ejabberd/ejabberd.cfg have you enabled mod_muc? If so, ...


5

You have two options regarding user registration. You can either manually create user accounts on the server, or you can enable in-band registration, which allows anyone who can connect to the server to register an account. If you want to create accounts manually, run this on the server for each user: sudo ejabberdctl register <username> ...


4

It's not ejabberd what handles audio/video talk. It's handled with Jingle (XEP-0166), which is client-to-client protocol extension for XMPP. The clients have to support it.


3

These are a little tricky to find out on the internet - hopping randomly through the "StartSSL" marked ones in this public directory, some were using self-signed certificates, and others were using the same certificates as on their HTTP services (not an "XMPP" cert). Of the couple that I did find using these special XMPP certs, there were two differences ...


2

Stop ejabberd. /etc/init.d/ejabberd stop 2.Kill processes: beam, beam.smp, epmd killall ejabberd killall beam killall beam.smp killall epmd 3.Remove the files in /var/lib/ejabberd (Create a backup copy of this folder just in case) rm -rf /var/lib/ejabberd/* rm -rf /var/lib/ejabberd/.erlang.cookie 4.Try to start ...


2

You can use iptables to limit the number of connection attempts per minute an IP address can attempt. Since these are automated attacks most of the time the script moves on to find another target once it's blocked. This example is for tcp port 22 (ssh) and will allow 3 connection attempts per minute before dropping packets from that IP address. iptables ...


2

You need to point your xmpp hostnames to the EC2 instances, either using CNAME records to Amazon's hostnames: xmpp1.example.com. IN CNAME ec2-192-0-2-76.us-west-1.compute.amazonaws.com. or using A records directly to the IP: xmpp1.example.com. IN A 192.0.2.76 The advantage of the CNAME approach is that other EC2 instances looking up the name ...


2

The solution turned out to be be creating shared roster groups via the web admin interface. name: operators members: operator1@domain, operator2@domain, ... displayed groups: operators name: everybody members: @all@ displayed groups: operators I also set the operators' Pidgin to hide offline users or else the buddy list quickly grows too long as new ...


2

Typically you ensure that: the config file is not visible by anyone but ejabberd (and root) ejabberd has its own credentials for LDAP, which can even be limited to only doing what ejabberd needs to do A separate file provides no more security than above. Having a dedicated LDAP user/password for ejabberd means that even if a compromise does happen, you ...


2

Try a larger instance size for your haproxy node. t1.micro instances have horrible network and IO performance, and I wouldn't be surprised if one if those were causing the problem.


1

Requiring StartTLS: {s2s_use_starttls, require}. instead of {s2s_use_starttls, true}. (keep in mind this will currently make you unable to connect to gmail.com and all domains they host). Weak ciphers: See http://www.process-one.net/docs/ejabberd/guide_en.html#sec27. I think this means doing something like adding {ciphers, "..."} to the ejabberd_c2s ...


1

Had my domain pointing to the wrong ip address of the server.


1

There are several points for you to try. First, ensure you have no, or a low-resolution avatar set. There's an outstanding bug related to Adium and ejabberd for this. Next, start Adium in debug mode (hold Option while starting) so you can get logging output and see what Adium says. It may also be worthwhile to check the security options for the ...


1

I'd say you're putting a lot on a single box. Memory is just one metric. You could be hitting CPU bottlenecks when you get traffic, or you're limiting I/O. iostat will give an idea on the disk activity. You'll probably see the issue go away if you move services to their own servers (have your web server separate from the jabber one).


1

My instinct of scaling systems generally says that a cluster of external databases would be a better thing than having lots of internal databases. I've never actually looked at scaling ejabberd, but generally it's good to separate services into clusters. This quora answer seems to agree about scaling to a separate DB when you've many nodes.


1

Seems like you have modified authentication mechanism to some thing other than "internal". If yes, then you have to configure virtual hosts in the external database being used.


1

Here are the MUC relevant bits of my ejabberd.conf for what it is worth - works for me : {access, muc_admin, [{allow, admin}]}. {access, muc, [{allow, all}]}. {mod_muc, [{access, all}, {access_create, all}, {access_admin, muc_admin}]}, The mod_muc is of course only valid as part of the modules stanza. Your configuration looks fine to my innocent ...


1

Tigase (www.tigase.org) is very good option. http://www.tigase.org/content/tigase-10mb-ram


1

It uses the clustering capabilities of Erlang : - The ability to message any process on a any node in the erlang cluster - it also uses mnesia, erlang's distributed database for storing the routing table, which contains the JID <-> client process id mapping. When a message enters ejabberd, it looks up the recipient JID in this table, and sends it to the ...


1

I suggest the use of DNS-based load balancing. By defining multiple SRV records, not only you achieve load balancing, but this can be distributed as you wish (for example you may want 60% of the load on a server with higher capacity, and the remaining to a smaller one), but you can also define failover servers. An SRV query for an XMPP server like ejabberd ...


1

I ended up using ejabberdctl to get information about the underlying mnesia database. Then set ERLANG_NODE within the file /etc/defaults/ejabberd to, in my case, ejabberd@vps. Et viola the service came up upon typing /etc/init.d/ejabberd start. Upon startup the process reports failed after a period of 30 seconds. Yet I could access the web management ...


1

To my knowledge there are no alternatives, but depending on your XMPP client you can do a whole lot of things from there when logged in as an administrative user.


1

You can't change the the name without recompiling the code. It's hardcoded in src/mod_muc/mod_muc.erl


1

you can export part of your ldaptree with ldapsearch to an ldif file and add it too your other ldap server with ldapadd or ldapmodify. there are also products which support automatic or semi automatic replication in one direction like the fedora directory server. jabber can be authenticated against ldap, but i can't tell you how. perhaps someone else can ...


1

It looks to be possible. Do you have any specific problems with the C# example on http://www.ejabberd.im/extauth? All you have to do is make a Console Application that prints out 21 or 20 depending whether it was a success or failure.


1

Something is wrong with the script, if your using Ubuntu i'd suggest su'ing to the ejabberd account and attempt to run the script. I had a similar issue where it was refusing to authenticate due to permission issues when the script tried to open a log file.



Only top voted, non community-wiki answers of a minimum length are eligible