The main MMMSG configuration file is located at
It contains the following configuration options
<listen address="0.0.0.0" port="8920" />
This option tells MMMSG service on which address and port it should listen. Changes of this item may require changes in you TLS proxy (nginx, stunnel) configuration.
<files path="/var/lib/mmmsg/files" />
Indicates a path where the transfered files are stored. The directory has to be writable by user running MMMSG service (usually named mmmsg).
<log level="info" />
Logging level of the MMMSG service. Acceptable values are
<base url="https://mmmsg.example.com" />
urlattribute is used as a prefix for urls in MMMSG replies. You should change the hostname to one of your MMMSG server.
<cors enabled="true" origin="*" />
Controls CORS headers that must be sent if MMMSG service is to be used from WebRTC. You may replace
originattribute with location of your WebRTC installations (for example
https://webrtc.example.com). If you do not use WebRTC, you can disable CORS headers. If you experience problems with WebRTC and MMMSG, try using star (
*) as the origin.
If the node
corsis not present, CORS headers are disabled. If you are upgrading from an old version of MMMSG and want to use it with MMMSG, you should add this node to your XML file.
<mimetypes> <mime type="default" maxLength="32" unit="MB"/> </mimetypes>
This section limits the size of uploaded files. You can configure size limit for any mimetype separately. Use
defaultfor catchall mimetype.