# Use another port for Zigbee2MQTT dashboard? **URL:** \ **Category:** Configuration\ **Tags:** zigbee2mqtt\ **Created:** [December 10, 2025, 2:50pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860 "2025-12-10T14:50:21Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 2:50pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/1 "2025-12-10T14:50:21Z")
I would like to use another port for Zigbee2MQTT in stead of 8080. So I can use that for another Docker container. How can I safely do that? ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [December 10, 2025, 3:21pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/2 "2025-12-10T15:21:40Z")
Hi, In the integration page, go to ZigBee2MQTT’s configuration and click the second ‘modify’ button ![1000011513](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/3/e/3eea814e7e43614e9b402d4d095e42e6b7a09cc2.jpeg) Then you can select the used port ! ![1000011514](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/8/88c6d49bc5fb84755e6ec7dcbe02063276830965.jpeg) ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 3:53pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/3 "2025-12-10T15:53:22Z")
Thank you! ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 4:14pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/4 "2025-12-10T16:14:17Z")
Sadly it didn’t work. ☹ Tried it both in Opera and Chrome on Win11. I can’t change it to another port, it won’t change. The only thing that works is making the field empty. It then selected port 12000. I also couldn’t change it back to 8080 After that the services couldn’t talk to each other and there are errors in the log. Couldn’t open the Z2M dashboard either. ![{F89F5D54-285F-4A78-A50F-192ECFAD7AE2}](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/a/f/aff1bfeaaa622b9e25b0250d3e0f86e94229eced.png) Errors: ```auto 2025-12-10T17:08:16+0100 installZ2mContainer.js:90 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started 2025-12-10T17:08:16+0100 connect.js:17 (Zigbee2mqttManager.connect) Disconnecting existing MQTT client... 2025-12-10T17:08:16+0100 connect.js:25 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker... 2025-12-10T17:08:16+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:16+0100 connect.js:53 (MqttClient.) Disconnected from MQTT server 2025-12-10T17:08:17+0100 system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker. 2025-12-10T17:08:21+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:26+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:31+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:36+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:41+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:46+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:51+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:08:56+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized 2025-12-10T17:09:01+0100 connect.js:46 (MqttClient.) Error while connecting to MQTT - Error: Connection refused: Not authorized ``` ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [December 10, 2025, 4:16pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/5 "2025-12-10T16:16:23Z")
Ils the z2m interface accessible on port 12000? ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 4:17pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/6 "2025-12-10T16:17:19Z")
No. ERR\_CONNECTION\_REFUSED ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [December 10, 2025, 4:19pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/7 "2025-12-10T16:19:54Z")
Try stopping the service using activate/deactivate toggle then restart it. Wait until all containers are good as they will be re-downloaded then re-created (a few mins) ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 4:24pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/8 "2025-12-10T16:24:40Z")
They are both running OK now. But I still can’t reach the Z2M dashboard. No errors in the logs. ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [December 10, 2025, 5:18pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/9 "2025-12-10T17:18:06Z")
What says the `docker ps -a` command ? (We’re looking at the used ports) ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 5:24pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/10 "2025-12-10T17:24:40Z")
```auto CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a32acb4039e9 koenkk/zigbee2mqtt:2.6.1 « docker-entrypoint.s… » About an hour ago Up About an hour gladys-z2m-zigbee2mqtt f7482e46285f eclipse-mosquitto:2.0.15 « /docker-entrypoint.… » About an hour ago Up About an hour gladys-z2m-mqtt 085b6f213e91 gladysassistant/gladys:latest « docker-entrypoint.s… » About an hour ago Up About an hour gladys ``` Running this: ```auto sudo docker run -d \ --log-driver json-file \ --log-opt max-size=10m \ --cgroupns=host \ --restart=always \ --privileged \ --network=host \ --name gladys \ -e NODE_ENV=production \ -e SERVER_PORT=8001 \ -e TZ=Europe/Amsterdam \ -e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /var/lib/gladysassistant:/var/lib/gladysassistant \ -v /dev:/dev \ -v /run/udev:/run/udev:ro \ gladysassistant/gladys:latest ``` ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [December 10, 2025, 5:38pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/11 "2025-12-10T17:38:55Z")
Try this one to see what front-end port is configured: ```auto sudo nano /var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml ``` ---
**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\ **Post date:** [December 10, 2025, 5:48pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/12 "2025-12-10T17:48:40Z")
@NoiZe if I’m not mistaken and if you’re using Gladys’ MQTT and zigbee2mqtt services (so internal services) then you should have: **Gladys** : port 8001 (according to your docker command line) > [@NoiZe](#): > > `-e SERVER_PORT=8001 \\` **MQTT** : 1884 (that’s what your log says and Gladys can’t connect to it because maybe a login and/or password error) > [@NoiZe](#): > > ```auto > 2025-12-10T17:08:16+0100 \\u003cinfo\\u003e connect.js:25 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker... > 2025-12-10T17:08:16+0100 \\u003cwarn\\u003e connect.js:46 (MqttClient.\\u003canonymous\\u003e) Error while connecting to MQTT - Error: Connection refused: Not authorized > > ``` **Zigbee2mqtt** : port 12000 Small note: you have zigbee2mqtt version 2.6.1, which means either you don’t have the Gladys update that now uses 2.7.1, or you have an external zigbee2mqtt. Another point, I believe you had a connection issue with your zigbee dongle. Did you change ZBDongle-P to ZBDongle-E to test? As long as zigbee2mqtt can’t connect to the dongle, it will restart endlessly and the system won’t work. In short, with all that, none of these services use port 8080, so I think you have something else on your machine using that port and it’s not Gladys Assistant and its services. ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 8:06pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/13 "2025-12-10T20:06:12Z")
I’m running MQTT and Z2M inside Gladys. Tried a manual update from cli, it updated to the latest version, also z2m to 2.7.1. Everything is connected and working, except the z2m management page. /var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml: Front-end port: 12000 Changed it to 8080 in the file and still get **connection refused** somehow. In the GUI it changed into 8080. **Still cannot change the port in the GUI itself.** 😑 P.s. I had problems with a zigbee dongle, but bought this new one that works fine. Log after reboot and docker purge (nevermind the Hue error): ```auto 2025-12-10T21:01:04+0100 index.js:149 (Object.duckDbShowVersion) DuckDB version = v1.4.1 2025-12-10T21:01:04+0100 index.js:98 (Object.duckDbCreateTableIfNotExist) DuckDB - Creating database table if not exist 2025-12-10T21:01:04+0100 job.purge.js:17 (Job.purge) Deleting all background jobs created before = Wed Dec 03 2025 21:01:04 GMT+0100 (Central European Standard Time) 2025-12-10T21:01:04+0100 system.setDuckDbTimezone.js:14 (System.setDuckDbTimezone) Setting DuckDB timezone to Europe/Amsterdam 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service alexa was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service caldav was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service openweather was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service ecowatt was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service enedis was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service rtsp-camera was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service telegram was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service usb was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service xiaomi was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service bluetooth was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service ewelink was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service tp-link was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service google-actions was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service homekit was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service broadlink was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service lan-manager was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service nextcloud-talk was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service tuya was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service melcloud was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service node-red was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service netatmo was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service sonos was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service zwavejs-ui was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service google-cast was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service airplay was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service free-mobile was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service edf-tempo was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service mqtt was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 service.startAll.js:30 () Service example was manually stopped, so it is ignored at startup 2025-12-10T21:01:10+0100 index.js:15 (Object.start) Starting energy monitoring service 2025-12-10T21:01:10+0100 index.js:29 (Object.start) Starting MCP service 2025-12-10T21:01:11+0100 index.js:18 (Object.start) Starting Matter service 2025-12-10T21:01:11+0100 index.js:21 (Object.start) Matter is not enabled 2025-12-10T21:01:11+0100 system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker. 2025-12-10T21:01:11+0100 init.js:63 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0 2025-12-10T21:01:11+0100 checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates... 2025-12-10T21:01:11+0100 installMqttContainer.js:114 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started 2025-12-10T21:01:11+0100 configureContainer.js:23 (Zigbee2mqttManager.configureContainer) Z2M Docker container is being configured... 2025-12-10T21:01:11+0100 configureContainer.js:36 (Zigbee2mqttManager.configureContainer) Z2M configuration file already exists. 2025-12-10T21:01:11+0100 installZ2mContainer.js:90 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started 2025-12-10T21:01:11+0100 connect.js:25 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker... 2025-12-10T21:01:11+0100 connect.js:35 (MqttClient.) Connected to MQTT container mqtt://localhost:1884 2025-12-10T21:01:11+0100 subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/# 2025-12-10T21:01:11+0100 index.js:15 (Object.start) Starting Tasmota service 2025-12-10T21:01:11+0100 index.js:18 (Object.start) Starting Philips Hue service 2025-12-10T21:01:11+0100 index.js:14 (Object.start) Starting CallMeBot service 2025-12-10T21:01:12+0100 scene.dailyUpdate.js:58 () Sunrise today is at 8:37 today, in your timezone = Europe/Amsterdam 2025-12-10T21:01:12+0100 scene.dailyUpdate.js:59 () Sunset today is at 16:28 today, in your timezone = Europe/Amsterdam 2025-12-10T21:01:12+0100 scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today. 2025-12-10T21:01:12+0100 scene.dailyUpdate.js:84 () The sun has already set. Not scheduling for today. 2025-12-10T21:01:12+0100 light.init.js:29 () Unable to connect to Philips Hue bridge "Hue Bridge" 2025-12-10T21:01:12+0100 device.migrateFromSQLiteToDuckDb.js:36 (DeviceManager.migrateFromSQLiteToDuckDb) DuckDB : Already migrated from SQLite. Not migrating. 2025-12-10T21:01:12+0100 system.checkIfGladysUpgraded.js:17 (System.checkIfGladysUpgraded) Gladys just upgraded from null to v4.66.1 2025-12-10T21:01:12+0100 system.checkIfGladysUpgraded.js:44 (System.checkIfGladysUpgraded) ServiceNotConfiguredError: Telegram not configured at MessageHandler.send (/src/server/services/telegram/lib/message.send.js:17:11) at MessageHandler.sendToUser (/src/server/lib/message/message.sendToUser.js:38:35) at /src/server/lib/system/system.checkIfGladysUpgraded.js:26:9 2025-12-10T21:01:12+0100 index.js:64 (Server.) Server listening on port 8001 ``` ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 8:32pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/14 "2025-12-10T20:32:58Z")
If I do a `sudo ss -tunlp` I can see there are no processes using port 8080. I do see the 8001 (Gladys) and 1884 (MQTT) ones. I did a `curl ``http://localhost:8080` on the Pi and inside the containers and got this response: `curl: (7) Failed to connect to localhost port 8080 after 0 ms: Could not connect to server` Also checked inside the containers for open ports and did not see the 8080 one. Since it was working fine on port 8080, before I changed it in the GUI to something else, could it be something that went wrong there? ---
**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\ **Post date:** [December 10, 2025, 8:35pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/15 "2025-12-10T20:35:45Z")
According to your logs, everything is ok now for Z2M and MQTT! However I’m stumped about the port 🙄 On my end I connect to `http://ip-de-gladys:12000` and Z2M appears. ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 10, 2025, 8:53pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/16 "2025-12-10T20:53:07Z")
Is there on your system an open port 12000 (or 8080) inside or outside the containers? ---
**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\ **Post date:** [December 10, 2025, 9:22pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/17 "2025-12-10T21:22:49Z")
No, I don’t have ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 11, 2025, 7:59am UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/18 "2025-12-11T07:59:29Z")
> [@mutmut](#): > > I think a part of your message is missing. Translation errors, apparently — I fixed them by hand! ---
**Author:** ![NoiZe](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/noize/32/19491_2.png) [@NoiZe](https://community.gladysassistant.com/u/NoiZe)\ **Post date:** [December 11, 2025, 3:26pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/19 "2025-12-11T15:26:23Z")
Found some mentions of it on the Z2M Github. Maybe the port isn’t binding. > My solution was this > > frontend: enabled: true port: 8080 host: 0.0.0.0 > > seems like the newest update isn’t automatically binding the container port to 0.0.0.0:8080 … annoying but whatever. Add that to your configuration.yaml and it works. [Check comment](https://github.com/Koenkk/zigbee2mqtt/issues/23134#issuecomment-2591425033) Maybe that’s the case with the configuration.yaml that Gladys uses? ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 11, 2025, 8:43pm UTC](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860/20 "2025-12-11T20:43:00Z")
My `configuration.yaml` contains only : ```auto frontend: enabled: true port: 8080 ``` And it works fine I’m not sure it’s the issue here! [Next page](https://community.gladysassistant.com/t/use-another-port-for-zigbee2mqtt-dashboard/9860.md?page=2)