[feature Request] - An ARM64 build would be nice.

[gavinbaker999]

An ARM64 build would be nice to run on Raspberry Pi 5.

[ilgrank]

The project is not actively developed anymore, and the original DEV is searching for someone who's willing to maintain it.

Should you be able to help, or know someone who could, or you're just willing to spread the word about this... any help would be very appreciated!

[thomasnordquist]

@gavinbaker999 would you be willing to test if I provided a build?

[orb71]

Hello @thomasnordquist

I managed to run it your ARM64 in docker on armbian. I had only to figure out you need to expose behind a reverse proxy unless you get a white page at login.

[gavinbaker999]

@gavinbaker999 would you be willing to test if I provided a build?

I would be glad to test the Raspberry Pi build.

[orb71]

@gavinbaker999 , The build is already available , just follow the Docker recipe and you’re good to go!

[thomasnordquist]

@orb71 can you add some details what you needed to do? Just to improve the docs or the docker image.

[orb71]

Hi @thomasnordquist

The documentation is generally clear and follows standard Docker deployment practices. However, it’s currently missing an explicit statement that an HTTPS reverse proxy is required for browser access.

With this minimal setup

docker run -p 8000:3000 \
  -e MQTT_EXPLORER_SKIP_AUTH=true \
  ghcr.io/thomasnordquist/mqtt-explorer:latest

Accessing the UI via a browser will result in a blank page.

Looking at the browser console, the following errors appear:

Content-Security-Policy warnings 4
Content-Security-Policy: Upgrading insecure request 'http://<host>:8000/bugtracking.bundle.js' to use 'https'
Content-Security-Policy: Upgrading insecure request 'http://<host>:8000/app.bundle.js' to use 'https'
Content-Security-Policy: Upgrading insecure request 'http://<host>:8000/bugtracking.bundle.js' to use 'https'
Content-Security-Policy: Upgrading insecure request 'http://<host>:8000/favicon.ico' to use 'https'
Loading failed for the <script> with source “http://<host>:8000/bugtracking.bundle.js”. 
Loading failed for the <script> with source “http://<host>:8000/app.bundle.js”.
Loading failed for the <script> with source “http://<host>:8000/bugtracking.bundle.js”

Documenting this explicitly would help avoid confusion for new users.

Here is my current Docker Compose setup using Traefik for internal-only access.

services:
  mqtt-explorer:
    container_name: mqtt-explorer
    image: ghcr.io/thomasnordquist/mqtt-explorer:latest
    environment:
      - MQTT_EXPLORER_USERNAME=${MQTT_EXPLORER_USERNAME}
      - MQTT_EXPLORER_PASSWORD=${MQTT_EXPLORER_PASSWORD}
    volumes:
      - /path/to/data:/app/data
    labels:
      - traefik.enable=true
      - traefik.http.services.mqtt-explorer.loadbalancer.server.port=3000
      - traefik.http.routers.mqtt-explorer.rule=Host(`mqtt-explorer.example.com`)
      - traefik.http.routers.mqtt-explorer.entryPoints=websecure
      - traefik.http.routers.mqtt-explorer.tls=true
      - traefik.http.routers.mqtt-explorer.tls.certresolver=<your_certresolver>
    networks:
      - proxy
networks:
  proxy:
    external: true