Run your own copy of Element, the polished Matrix messaging client, on a web server using Docker. No coding required — just a few commands and a config file.
Before anything else, make sure Docker is installed and running. This single command prints the version if Docker is ready. If you get an error, install Docker first via https://docs.docker.com/engine/install/ubuntu/.
Permission denied when running docker
Run: sudo usermod -aG docker $USER — then log out and back in.
Make a dedicated folder to keep your Element config files tidy. All the next steps happen inside this folder.
Element needs a small JSON config file to know which Matrix homeserver to point at by default. The command below creates a minimal working config that points to matrix.org. If you run your own homeserver, replace 'matrix.org' with your homeserver domain in both places. The file must be named config.json.
You want to use your own homeserver instead of matrix.org
Open config.json with: nano config.json — and replace both occurrences of 'matrix.org' with your homeserver's domain, then save with Ctrl+O, Enter, Ctrl+X.
This command downloads the official Element Web Docker image and starts it on port 8080 of your server. It also mounts your config.json so Element uses your settings. The container restarts automatically if your server reboots.
Port 8080 is already in use
Change -p 8080:80 to -p 8888:80 (or any free port) and access Element on that port instead.
Check that the container started without errors. You should see it listed with a status of 'Up'.
Status shows 'Exited' instead of 'Up'
Run: docker logs element-web — to see the error. Most often it is a malformed config.json. Validate your JSON at jsonlint.com, fix it, then run: docker restart element-web
Navigate to your server's IP address (or domain) on port 8080. You should see the Element login screen. Sign in with any Matrix account — including a free matrix.org account.
Page does not load / connection refused
Check your server's firewall allows port 8080: sudo ufw allow 8080/tcp — then try again.
A fully working Element Web chat client running in Docker on your server, accessible in a browser, connected to Matrix so you can send and receive messages.
This guide gives you a working HTTP instance on a plain port — fine for testing, not for production. For a real deployment you need a reverse proxy (like Nginx or Caddy) with an SSL certificate so the URL starts with https://. Without HTTPS, some Matrix features (like microphone access for calls) will not work, and browsers may warn users. Also, Element Web is just the client — you still need a Matrix homeserver (matrix.org is free) to actually send messages. Hosting your own homeserver (Synapse or Dendrite) is a separate, larger project.