Portainer Templates logo

Portainer Templates

Nexterm Nexterm

Stack

Remote Control

The open source server management software for SSH, VNC & RDP

Image details

Pulls: 1.5M
Architecture: amd64, arm64, arm/v7
Image size: 245 MB
Latest: 1.0.9-OPEN-PREVIEW
User: germannewsmaker
Created: Aug 21, 2024
Updated: 5 months ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
germannewsmaker/nexterm:1.0.2-OPEN-PREVIEW
Ports
6989:6989
Volumes
/app/data : /portainer/Files/AppData/Config/nexterm
Restart
always
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Nexterm

Installation method

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 Nexterm, fill in any config options, and hit Deploy

Template Import URL

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

The compose file this template deploys, straight from its repo:

services:
  nexterm:
    ports:
      - "6989:6989"
    restart: always
    volumes:
      - /portainer/Files/AppData/Config/nexterm:/app/data
    image: germannewsmaker/nexterm:1.0.2-OPEN-PREVIEW
volumes:
  nexterm:

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/nexterm.yml up -d

More install options in our documentation.

Serve Nexterm 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 nexterm.example.com to http://nexterm:6989

Add this to your Caddyfile

nexterm.example.com {
	reverse_proxy http://nexterm:6989
}

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:6989 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :6989
  • Stop the other service, or pick a different host port. In 6989:6989 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:6989. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, nexterm can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 6989

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/nexterm

Image won't pull

Test the pull directly on the host: docker pull germannewsmaker/nexterm:1.0.2-OPEN-PREVIEW

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

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

Nexterm 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.

The app image

An image is the app packed up ready to go, everything Nexterm needs bundled into one download. This template pulls germannewsmaker/nexterm:1.0.2-OPEN-PREVIEW, which Docker fetches once (about 245 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Nexterm's comes from Docker Hub, published by germannewsmaker.

Version tags

The bit after the colon in the image name is the version tag. This one pins 1.0.2-OPEN-PREVIEW, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 6989:6989 means it's reachable on port 6989 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 6989:6989

Volumes

A volume is where Nexterm keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /app/data from /portainer/Files/AppData/Config/nexterm on the host

Restart policy

The restart policy here is always, so Docker brings Nexterm 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 Nexterm 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 nexterm. That's what you'll spot in the containers list and use in commands like docker logs nexterm.

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 Nexterm up. Add the template list to Portainer once, then deploying Nexterm is a click rather than a wall of config.