![]() See the Jabber SPAM Manifesto for details: # 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 # Mnesia is limited to 2GB, better to use an SQL backend "Access-Control-Allow-Headers": "Content-Type" # /.well-known/acme-challenge: ejabberd_acme usr/local/etc/letsencrypt/live/MY_HOSTNAME/fullchain.pem # If you already have certificates, list them here # ******* MAKE SURE YOU INDENT SECTIONS CORRECTLY ******* # ******* YAML IS INDENTATION SENSITIVE ******* # The configuration file is written in YAML. # The parameters used in this configuration file are explained at Here is the jabber.yml configuration file (I took the liberty of replacing my domain name with MY_HOST and my IP addresses with MY_IPV*): # All I did was take the default config file, add an administrator account, and add my Cerbot certificates. I haven't even gotten to the part of worrying about STUN/TURN for calls or stuff like that, all I'm trying to do is to just get the program to work. I've been trying for two days to get a simple Ejabberd setup working on a FreeBSD system, nothing too complicated, but couldn't get past a "TLS negotiation failed" error in Conversations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |