1 -- Information on configuring Prosody can be found on our
2 -- website at http://prosody.im/doc/configure
4 -- Tip: You can check that the syntax of this file is correct
5 -- when you have finished by running: luac -p prosody.cfg.lua
6 -- If there are any errors, it will let you know what and where
7 -- they are, otherwise it will keep quiet.
10 ---------- Server-wide settings ----------
11 -- Settings in this section apply to the whole server and are the default settings
12 -- for any virtual hosts
14 -- This is a (by default, empty) list of accounts that are admins
15 -- for the server. Note that you must create the accounts separately
16 -- (see http://prosody.im/doc/creating_accounts for info)
17 -- Example: admins = { "user1@example.com", "user2@example.net" }
20 -- Enable use of libevent for better performance under high load
21 -- For more information see: http://prosody.im/doc/libevent
22 --use_libevent = true;
24 -- This is the list of modules Prosody will load on startup.
25 -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
26 -- Documentation on modules can be found at: http://prosody.im/doc/modules
30 "roster"; -- Allow users to have a roster. Recommended ;)
31 "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
32 "tls"; -- Add support for secure TLS on c2s/s2s connections
33 "dialback"; -- s2s dialback support
34 "disco"; -- Service discovery
36 -- Not essential, but recommended
37 "private"; -- Private XML storage (for room bookmarks, etc.)
38 "vcard"; -- Allow users to set vCards
40 -- These are commented by default as they have a performance impact
41 "privacy"; -- Support privacy lists
42 "compression"; -- Stream compression
45 "version"; -- Replies to server version requests
46 "uptime"; -- Report how long server has been running
47 "time"; -- Let others know the time here on this server
48 "ping"; -- Replies to XMPP pings with pongs
49 "pep"; -- Enables users to publish their mood, activity, playing music and more
50 "register"; -- Allow users to register on this server using a client and change passwords
53 "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
54 --"admin_telnet"; -- Opens telnet console interface on localhost port 5582
57 --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
58 --"http_files"; -- Serve static files from a directory over HTTP
60 -- Other specific functionality
61 "posix"; -- POSIX functionality, sends server to background, enables syslog, etc. (Keep enabled for Gentoo.)
62 --"groups"; -- Shared roster support
63 "announce"; -- Send announcement to all online users
64 --"welcome"; -- Welcome users who register accounts
65 --"watchregistrations"; -- Alert admins of registrations
66 --"motd"; -- Send a message to users when they log in
67 --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
70 -- Settings for Gentoo init script and net-im/jabber-base permissions system:
72 prosody_user = "jabber";
73 prosody_group = "jabber";
74 pidfile = "/var/run/jabber/prosody.pid";
76 -- These modules are auto-loaded, but should you want
77 -- to disable them then uncomment them here:
79 -- "offline"; -- Store offline messages
80 -- "c2s"; -- Handle client connections
81 -- "s2s"; -- Handle server-to-server connections
84 -- Disable account creation by default, for security
85 -- For more information see http://prosody.im/doc/creating_accounts
86 allow_registration = false;
88 -- These are the SSL/TLS-related settings. If you don't want
89 -- to use SSL/TLS, you may comment or remove this
91 key = "/etc/ssl/jabber/privkey.pem";
92 certificate = "/etc/ssl/jabber/root.crt";
93 dhparam = "/etc/ssl/jabber/dhparam.pem";
94 options = {"no_sslv2", "no_sslv3" };
95 ciphers = "EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA";
100 -- Force clients to use encrypted connections? This option will
101 -- prevent clients from authenticating unless they are using encryption.
103 c2s_require_encryption = true
104 s2s_require_encryption = true
106 -- Force certificate authentication for server-to-server connections?
107 -- This provides ideal security, but requires servers you communicate
108 -- with to support encryption AND present valid, trusted certificates.
109 -- NOTE: Your version of LuaSec must support certificate verification!
110 -- For more information see http://prosody.im/doc/s2s#security
112 --s2s_secure_auth = true
114 -- Many servers don't support encryption or have invalid or self-signed
115 -- certificates. You can list domains here that will not be required to
116 -- authenticate using certificates. They will be authenticated using DNS.
118 --s2s_insecure_domains = { "gmail.com" }
120 -- Even if you leave s2s_secure_auth disabled, you can still require valid
121 -- certificates for some domains by specifying a list here.
123 --s2s_secure_domains = { "jabber.org" }
125 -- Select the authentication backend to use. The 'internal' providers
126 -- use Prosody's configured data storage to store the authentication data.
127 -- To allow Prosody to offer secure authentication mechanisms to clients, the
128 -- default provider stores passwords in plaintext. If you do not trust your
129 -- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed
130 -- for information about using the hashed backend.
132 authentication = "internal_plain"
134 -- Select the storage backend to use. By default Prosody uses flat files
135 -- in its configured data directory, but it also supports more backends
136 -- through modules. An "sql" backend is included by default, but requires
137 -- additional dependencies. See http://prosody.im/doc/storage for more info.
139 --storage = "sql" -- Default is "internal"
141 -- For the "sql" backend, you can uncomment *one* of the below to configure:
142 --sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
143 --sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
144 --sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
146 -- Logging configuration
147 -- For advanced logging see http://prosody.im/doc/logging
149 info = "/var/log/jabber/prosody.log"; -- Change 'info' to 'debug' for verbose logging
150 error = "/var/log/jabber/prosody.err";
151 -- "*syslog"; -- Uncomment this for logging to syslog
152 -- "*console"; -- Log to the console, useful for debugging with daemonize=false
155 ----------- Virtual hosts -----------
156 -- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
157 -- Settings under each VirtualHost entry apply *only* to that host.
159 VirtualHost "localhost"
161 VirtualHost "example.org"
162 enabled = true -- Remove this line to enable this host
164 -- Assign this host a certificate for TLS, otherwise it would use the one
165 -- set in the global section (if any).
166 -- Note that old-style SSL on port 5223 only supports one certificate, and will always
167 -- use the global one.
169 -- key = "/etc/ssl/ejabberd/privkey.pem";
170 -- certificate = "/etc/ssl/ejabberd/root.crt";
171 -- options = {"no_sslv2", "no_sslv3" };
172 -- dhparam = "/etc/jabber/cert/dhparam.pem";
176 ------ Components ------
177 -- You can specify components to add hosts that provide special services,
178 -- like multi-user conferences, and transports.
179 -- For more information on components, see http://prosody.im/doc/components
181 ---Set up a MUC (multi-user chat) room server on conference.example.com:
182 --Component "conference.example.com" "muc"
184 -- Set up a SOCKS5 bytestream proxy for server-proxied file transfers:
185 --Component "proxy.example.com" "proxy65"
187 ---Set up an external component (default component port is 5347)
189 -- External components allow adding various services, such as gateways/
190 -- transports to other networks like ICQ, MSN and Yahoo. For more info
191 -- see: http://prosody.im/doc/components#adding_an_external_component
193 --Component "gateway.example.com"
194 -- component_secret = "password"