# Hivemq edge 2025.1 - Unable to login to console **URL:** \ **Category:** Uncategorized\ **Created:** [February 5, 2025, 7:41pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546 "2025-02-05T19:41:39Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![PrairieSnpr](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@PrairieSnpr](https://community.hivemq.com/u/PrairieSnpr)\ **Post date:** [February 5, 2025, 7:41pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/1 "2025-02-05T19:41:39Z")
I’m no longer able to login to the Hivemq edge admin console after upgrading from 2024.9 to 2025.2. Hivemq edge is running in a docker container, no errors are logged, however chrome debug console reports `GET http://127.0.0.1:8080/api/v1/frontend/configuration net::ERR_CONNECTION_REFUSED index-C4zGATjt.js:441`. This error is repeated multiple times and `Network Error We cannot load your default credentials. Please try again later` is displayed above the user name text box. Hivemq edge is running and data bridges are working as expected, I’m just unable to login to the admin. I tried adding the URL to /etc/hosts in the docker container without success. This is hosted behind a nginx reveres proxy, so the api calls should be to `https://hivemq-edge.domain.com`. I’m assuming something in the config changed? The release notes on github take me to a 404 page, so maybe I’m missing a breaking change? ---
**Author:** ![Daria\_H](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@Daria\_H](https://community.hivemq.com/u/Daria_H)\ **Post date:** [February 6, 2025, 9:39am UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/2 "2025-02-06T09:39:02Z")
Hi @PrairieSnpr It looks like there might be a port conflict between HiveMQ Edge and Nginx. Could you try stopping Nginx temporarily and then accessing the HiveMQ Edge admin console directly at `http://127.0.0.1:8080`? This will help determine if Nginx is interfering with the connection or if the issue lies elsewhere. Let us know what you find Best, Dasha from The HiveMQ Team ---
**Author:** ![PrairieSnpr](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@PrairieSnpr](https://community.hivemq.com/u/PrairieSnpr)\ **Post date:** [February 6, 2025, 12:11pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/3 "2025-02-06T12:11:13Z")
Thanks @Daria_H, we can rule out an Nginx conflict, the web ui is visible, so that portion is working. I can’t really test as you asked since this is a headless server, but the web ui shows as expected. The issue is, that Nginx correctly proxies [https://hivemq-edge.domain.com](https://hivemq-edge.domain.com) to the docker container on port 8080, but the script that runs in the browser is still trying to reach localhost on port 8080. I assume that some logic was moved from the server to the client and I need to set the base url, but I have yet to find a setting for that. ---
**Author:** ![PrairieSnpr](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@PrairieSnpr](https://community.hivemq.com/u/PrairieSnpr)\ **Post date:** [February 6, 2025, 12:32pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/4 "2025-02-06T12:32:38Z")
Another note, reverting to `2025.1` fixes this, the issue is isolated to `2025.1-k8s`. ---
**Author:** ![Daria\_H](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@Daria\_H](https://community.hivemq.com/u/Daria_H)\ **Post date:** [February 6, 2025, 4:36pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/5 "2025-02-06T16:36:42Z")
Hi PrairieSnpr, It sounds like you’re not encountering issues with the `hivemq-edge:2025.1` Docker image, but you’re having trouble with the `hivemq-edge:2025.1-k8s` image. You mentioned that the image is running in a Docker container, but the `-k8s` tag is typically meant for Kubernetes environments. Could you clarify why you’re running the Kubernetes-specific image in a Docker container? Looking forward to your response! Best, Dasha from The HiveMQ Team ---
**Author:** ![PrairieSnpr](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@PrairieSnpr](https://community.hivemq.com/u/PrairieSnpr)\ **Post date:** [February 6, 2025, 5:09pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/6 "2025-02-06T17:09:00Z")
I actually was using the `latest` tag. Looking at [https://hub.docker.com/r/hivemq/hivemq-edge/tags](https://hub.docker.com/r/hivemq/hivemq-edge/tags), the sha256 hash is the same for `latest` and `2025.1-k8s`. ---
**Author:** ![PrairieSnpr](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@PrairieSnpr](https://community.hivemq.com/u/PrairieSnpr)\ **Post date:** [February 7, 2025, 2:25pm UTC](https://community.hivemq.com/t/hivemq-edge-2025-1-unable-to-login-to-console/3546/7 "2025-02-07T14:25:02Z")
This is resolved in `2025.2`.