A simple XMPP upload server (tested with Prosody only so far) that relies on S3 API compatible storage (tested against my own Ceph and Scaleway (free 75GB)) instead of local disk, so that you can run it without local state on Kubernetes/Docker.
Like the original version, it aims to be thin and simple. It streams PUT operations directly to S3, and fetch operations will by default redirect to a signed request to S3, instead of sitting in between as an unnecessary bottleneck. (If you do prefer proxying, it can be enabled using the ProxyMode setting.)
If you want automatic purging, just set lifecycle policies on your S3 bucket.
### IP address and port to listen to, e.g. "[::]:5050"
ListenPort = "0.0.0.0:5280"
### Secret (must match the one in prosody.conf.lua!)
Secret =
### Subdirectory for HTTP upload / download requests (usually "upload/",
### NO to LEADING slash, YES to trailing!)
UploadSubDir = "upload/"
### Hostname of S3 compatible endpoint
S3Endpoint = "xmpp-filer.s3.nl-ams.scw.cloud"
### HTTPS. True by default obviously, set to false if you must.
S3TLS = true
### Credentials. Use AWS_ACCESS_KEY_ID environment variable if you prefer.
S3AccessKey = "..."
### Or AWS_SECRET_ACCESS_KEY environment variable.
S3Secret = "..."
### Our S3 bucket name.
S3Bucket = "xmpp-filer"
### If your client doesn't deal well with the 302 redirects or signed URLs,
### enable this setting so Filer will proxy the data for you.
ProxyMode = falseThe rest of this manual covers the local-storage original Filer. The majority of it (except for Prosody/Ejabberd configuration) shouldn't apply to you if you're planning to run this Filer on k8s.
A simple file server for handling XMPP http_upload requests. This server is meant to be used with the Prosody mod_http_upload_external module.
Despite the name, this server is also compatible with Ejabberd and Ejabberd's http_upload module!
- Prosody developers recommend using http_upload_external instead of http_upload (Matthew Wild on the question if http_upload is memory leaking):
"BTW, I am not aware of any memory leaks in the HTTP upload code. However it is known to be very inefficient. That's why it has a very low upload limit, and we encourage people to use mod_http_upload_external instead. We set out to write a good XMPP server, not HTTP server (of which many good ones already exist), so our HTTP server is optimised for small bits of data, like BOSH and websocket. Handling large uploads and downloads was not a goal (and implementing a great HTTP server is not a high priority for the project compared to other things). Our HTTP code buffers the entire upload into memory. More, it does it in an inefficient way that can use up to 4x the actual size of the data (if the data is large). So uploading a 10MB file can in theory use 40MB RAM. But it's not a leak, the RAM is later cleared and reused. [...] The GC will free the memory at some point, but the OS may still report that Prosody is using that memory due to the way the libc allocator works. Most long lived processes behave this way (only increasing RAM, rarely decreasing)."
- This server works without any script interpreters or additional dependencies. It is delivered as a binary.
- Go is very good at serving HTTP requests and "made for this task".
If you are using regular x86_64 Linux, you can download a finished binary for your system on the release page. No need to compile this application yourself.
If you're using something different than a x64 Linux, you need to compile this application yourself.
To compile the server, you need a full Golang development environment. This can be set up quickly: https://golang.org/doc/install#install
Then checkout this repo:
go get github.com/ThomasLeister/prosody-filerand switch to the new directory:
cd $GOPATH/src/github.com/ThomasLeister/prosody-filerThe application can now be build:
### Build static binary
./build.sh
### OR regular Go build
go build main.goCreate a new user for Prosody Filer to run as:
adduser --disabled-login --disabled-password prosody-filerSwitch to the new user:
su - prosody-filerCopy
- the binary
prosody-filerand - config
config.example.toml
to /home/prosody-filer/. Rename the configuration to config.toml.
Make sure the prosody-filer binary is executable:
chmod u+x prosody-filer
Back in your root shell make sure mod_http_upload is disabled and mod_http_upload_external is enabled! Then configure the external upload module:
http_upload_external_base_url = "https://uploads.myserver.tld/upload/"
http_upload_external_secret = "mysecret"
http_upload_external_file_size_limit = 50000000 -- 50 MBRestart Prosody when you are finished:
systemctl restart prosody
Although this tool is named after Prosody, it can be used with Ejabberd, too! Make sure you have a Ejabberd configuration similar to this:
mod_http_upload:
put_url: "https://uploads.@HOST@/upload"
external_secret: "mysecret"
max_size: 52428800Prosody Filer configuration is done via the config.toml file in TOML syntax. There's not much to be configured:
### IP address and port to listen to, e.g. "[::]:5050"
listenport = "[::1]:5050"
### Secret (must match the one in prosody.conf.lua!)
secret = "mysecret"
### Where to store the uploaded files
storeDir = "./upload/"
### Subdirectory for HTTP upload / download requests (usually "upload/")
uploadSubDir = "upload/"Make sure mysecret matches the secret defined in your mod_http_upload_external settings!
In addition to that, make sure that the nginx user or group can read the files uploaded via prosody-filer if you want to have them served by nginx directly.
Create a new Systemd service file: /etc/systemd/system/prosody-filer.service
[Unit]
Description=Prosody file upload server
[Service]
Type=simple
ExecStart=/home/prosody-filer/prosody-filer
Restart=always
WorkingDirectory=/home/prosody-filer
User=prosody-filer
Group=prosody-filer
# Group=nginx # if the files should get served by nginx directly:
[Install]
WantedBy=multi-user.target
Reload the service definitions, enable the service and start it:
systemctl daemon-reload
systemctl enable prosody-filer
systemctl start prosody-filer
Done! Prosody Filer is now listening on the specified port and waiting for requests.
Create a new config file /etc/nginx/sites-available/uploads.myserver.tld:
server {
listen 80;
listen [::]:80;
listen 443 ssl;
listen [::]:443 ssl;
server_name uploads.myserver.tld;
ssl_certificate /etc/letsencrypt/live/uploads.myserver.tld/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/uploads.myserver.tld/privkey.pem;
client_max_body_size 50m;
location /upload/ {
if ( $request_method = OPTIONS ) {
add_header Access-Control-Allow-Origin '*';
add_header Access-Control-Allow-Methods 'PUT, GET, OPTIONS, HEAD';
add_header Access-Control-Allow-Headers 'Authorization, Content-Type';
add_header Access-Control-Allow-Credentials 'true';
add_header Content-Length 0;
add_header Content-Type text/plain;
return 200;
}
proxy_pass http://[::]:5050/upload/;
proxy_request_buffering off;
}
}Enable the new config:
ln -s /etc/nginx/sites-available/uploads.myserver.tld /etc/nginx/sites-enabled/
Check Nginx config:
nginx -t
Reload Nginx:
systemctl reload nginx
(not officially supported - user contribution!)
server {
listen 80;
listen [::]:80;
listen 443 ssl;
listen [::]:443 ssl;
server_name uploads.myserver.tld;
ssl_certificate /etc/letsencrypt/live/uploads.myserver.tld/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/uploads.myserver.tld/privkey.pem;
location /upload/ {
if ( $request_method = OPTIONS ) {
add_header Access-Control-Allow-Origin '*';
add_header Access-Control-Allow-Methods 'PUT, GET, OPTIONS, HEAD';
add_header Access-Control-Allow-Headers 'Authorization, Content-Type';
add_header Access-Control-Allow-Credentials 'true';
add_header Content-Length 0;
add_header Content-Type text/plain;
return 200;
}
root /home/prosody-filer;
autoindex off;
client_max_body_size 51m;
client_body_buffer_size 51m;
try_files $uri $uri/ @prosodyfiler;
}
location @prosodyfiler {
proxy_pass http://[::1]:5050;
proxy_buffering off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host:$server_port;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
}(This configuration was provided by a user and has never been tested by the author of Prosody Filer. It might be outdated and might not work anymore)
<VirtualHost *:80>
ServerName upload.example.eu
RedirectPermanent / https://upload.example.eu/
</VirtualHost>
<VirtualHost *:443>
ServerName upload.example.eu
SSLEngine on
SSLCertificateFile "Path to the ca file"
SSLCertificateKeyFile "Path to the key file"
Header always set Public-Key-Pins: ''
Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"
H2Direct on
<Location /upload>
Header always set Access-Control-Allow-Origin "*"
Header always set Access-Control-Allow-Headers "Content-Type"
Header always set Access-Control-Allow-Methods "OPTIONS, PUT, GET"
RewriteEngine On
RewriteCond %{REQUEST_METHOD} OPTIONS
RewriteRule ^(.*)$ $1 [R=200,L]
</Location>
SSLProxyEngine on
ProxyPreserveHost On
ProxyRequests Off
ProxyPass / http://localhost:5050/
ProxyPassReverse / http://localhost:5050/
</VirtualHost>
Prosody Filer has no immediate knowlegde over all the stored files and the time they were uploaded, since no database exists for that. Also Prosody is not capable to do auto deletion if mod_http_upload_external is used. Therefore the suggested way of purging the uploads directory is to execute a purge command via a cron job:
@daily find /home/prosody-filer/upload/ -mindepth 1 -type d -mtime +28 -print0 | xargs -0 -- rm -rf
This will delete uploads older than 28 days.
Get the log via
journalctl -f -u prosody-filer
If your XMPP clients uploads or downloads any file, there should be some log messages on the screen.