Portainer Templates logo

Portainer Templates

Fuuz Device Gateway Fuuz Device Gateway

Container

OpsMesWms

A secure gateway that connects on-premise devices, PLCs, and data sources to the Fuuz Cloud for seamless, real-time integration.

Configuration

Type
Container
Platform
linux
Image
public.ecr.aws/n9a9v7z5/mfgx-native-app-device-gateway-server:latest
Command
/fuuzdevicegateway/fuuzdevicegateway
Ports
5500:5500/tcp5501:5501/tcp
Volumes
/root/.fuuzdevicegateway//fuuzdevicegateway/drivers/
Env vars
FUUZ_API_KEY=''FUUZ_GATEWAY_AUTO_UPDATE=trueFUUZ_GATEWAY_LOG_LEVEL=infoFUUZ_GATEWAY_LOG_RETENTION_DAYS=30FUUZ_GATEWAY_PORT=5500FUUZ_GATEWAY_LISTEN_ADDRESS=0.0.0.0

Template by portainer

Notes

Fill out the configuration below, by default this will be accessible at http://{IP_Address}:5500. If you have questions or issues with setup, review our documentation at support.fuuz.com or contact support at support@fuuz.com

Standalone Install

Select an install method, to see config/commands for deploying Fuuz Device Gateway

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 Fuuz Device Gateway, 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 Fuuz Device Gateway 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 fuuz-device-gateway.example.com to http://fuuz-device-gateway:5500

Add this to your Caddyfile

fuuz-device-gateway.example.com {
	reverse_proxy http://fuuz-device-gateway:5500
}

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

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

Image won't pull

Test the pull directly on the host: docker pull public.ecr.aws/n9a9v7z5/mfgx-native-app-device-gateway-server:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "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.

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

Required settings are blank

FUUZ_API_KEY has no default value, and the app may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

Raise an issue

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

A single container

Fuuz Device Gateway runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Fuuz Device Gateway needs bundled into one download. This template pulls public.ecr.aws/n9a9v7z5/mfgx-native-app-device-gateway-server:latest, which Docker fetches once and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Fuuz Device Gateway's comes from Amazon's public registry, published by n9a9v7z5.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.

Ports

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

  • 5500:5500
  • 5501:5501

Volumes

A volume is where Fuuz Device Gateway 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:

  • /root/.fuuzdevicegateway/ as a volume Docker manages for you
  • /fuuzdevicegateway/drivers/ as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Fuuz Device Gateway takes 6 of them, and one needs a value before it'll start properly:

  • FUUZ_API_KEY, needs a value. When the Fuuz API key is provided, the gateway will connect to the cloud on startup and not require the API Key to be created at first launch.
  • FUUZ_GATEWAY_AUTO_UPDATE, pick one of true, false. Enable Auto Update
  • FUUZ_GATEWAY_LOG_LEVEL, pick one of error, warn, info, debug, verbose. Log Level
  • FUUZ_GATEWAY_LOG_RETENTION_DAYS, defaults to 30. Log Retention Days
  • FUUZ_GATEWAY_PORT, defaults to 5500. Gateway Port
  • FUUZ_GATEWAY_LISTEN_ADDRESS, defaults to 0.0.0.0. Listen Address

Networking

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

Startup command

The command is what runs the moment the container starts. This template sets its own, /fuuzdevicegateway/fuuzdevicegateway, in place of the image's default.

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