Portainer Templates logo

Portainer Templates

Servas Servas

Stack

Tools

A self-hosted bookmark management tool.

Configuration

Type
Compose
Platform
linux
Ports
8456:80/tcp
Restart
always
Source
Repo

Template by xneo1·Source

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Servas, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

Serve Servas on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying servas.example.com to http://Servas:80

Add this to your Caddyfile

servas.example.com {
	reverse_proxy http://Servas:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8456 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8456
  • Stop the other service, or pick a different host port. In 8456:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8456. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Servas can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8456

Container keeps restarting

The always restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Servas is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

Ports

A port is the door the app answers on. A mapping like 8456:80 means it's reachable on port 8456 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8456 in a browser. It opens:

  • 8456:80, likely the web interface

Restart policy

The restart policy here is always, so Docker brings Servas back up after a crash and again when the server reboots. Good for anything you want running around the clock. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Servas sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container Servas. That's what you'll spot in the containers list and use in commands like docker logs Servas.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Servas up. Add the template list to Portainer once, then deploying Servas is a click rather than a wall of config.