Homarr•10mo ago

Can't log in using my password when connecting through Nginx Proxy Manager

I have setup Homarr through docker on my machine. I have another VM on the network with full access to the containers ip. I've setup NPM, with and without https. When I open the homarr link it shows me the login page for Homarr but when I type the password it states that either the credentials are incorrect or the user doesn't exist. When I do the same throught the direct ip/port address it works fine. Also, I notice in the docker logs that when I log in directly, I get a message in the logs that username "XXX" has attampted login and user was authroized. When I do the same through NPM there are no logs at all. it's like the web UI is responding without actually running anything. Any ideas? here's my docker compose:

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.     #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: always
    environment:
      - NODE_TLS_REJECT_UNAUTHORIZED=0
      - BASE_URL=homarr.xxx.org
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/configs:/app/data/configs
      - ./homarr/icons:/app/public/icons
      - ./homarr/data:/data
    ports:
      - '7575:7575'

version: '3'
#---------------------------------------------------------------------#
#     Homarr - A simple, yet powerful dashboard for your server.     #
#---------------------------------------------------------------------#
services:
  homarr:
    container_name: homarr
    image: ghcr.io/ajnart/homarr:latest
    restart: always
    environment:
      - NODE_TLS_REJECT_UNAUTHORIZED=0
      - BASE_URL=homarr.xxx.org
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock # Optional, only if you want docker integration
      - ./homarr/configs:/app/data/configs
      - ./homarr/icons:/app/public/icons
      - ./homarr/data:/data
    ports:
      - '7575:7575'

Solution:

I finally solved it by regenerating the docker container on another machine and pointing the NPM to it. I have no idea what caused the issue but it's good enough for me.

Jump to solution

12 Replies

Cakey Bot•10mo ago

Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.

⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)

❓ Frequently Asked Questions | Homarr documentation

Can I install Homarr on a Raspberry Pi?

NighTimeOP•10mo ago

Logs:

Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.18s.
Starting production server...
Listening on port 7575 url: http://a7a18d3e7b80:7575
ℹ Local icons repository directory exists and contains 0 icons
(node:55) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
ℹ Local icons repository directory exists and contains 0 icons
user nigthtime is trying to log in. checking password...
user nigthtime successfully authorized
ℹ Local icons repository directory exists and contains 0 icons
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.16s.
Starting production server...
Listening on port 7575 url: http://a7a18d3e7b80:7575
(node:56) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
ℹ Local icons repository directory exists and contains 0 icons
ℹ Local icons repository directory exists and contains 0 icons

Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.18s.
Starting production server...
Listening on port 7575 url: http://a7a18d3e7b80:7575
ℹ Local icons repository directory exists and contains 0 icons
(node:55) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
ℹ Local icons repository directory exists and contains 0 icons
user nigthtime is trying to log in. checking password...
user nigthtime successfully authorized
ℹ Local icons repository directory exists and contains 0 icons
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.16s.
Starting production server...
Listening on port 7575 url: http://a7a18d3e7b80:7575
(node:56) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
ℹ Local icons repository directory exists and contains 0 icons
ℹ Local icons repository directory exists and contains 0 icons

NighTimeOP•10mo ago

NighTimeOP•10mo ago

As you can see, there is nothing in the logs even though I entered my username and password.

Serenaphic•10mo ago

You tried all that was suggested by the AI in that discussion you messaged on earlier? https://discord.com/channels/972958686051962910/1205280246706995251 Beginning with nextauth_url that I see you don't have in your environment

NighTimeOP•10mo ago

I added it, but it made no difference. it's like the login request isn't even propogating to Homarr. like it's not listening to it or something. As I mentioned, I don't see anything in the logs regarding a login attempt at all. is there something list a trusted_proxies or listen on interface environment command I should try?

Serenaphic•10mo ago

Since it's not going to homarr's check the logs in your browser's console

NighTimeOP•10mo ago

I'm now seeing that trying to access using my phone to the direct ip is having the same problem. apparently I can only seem to login using my pc (different pc from the VM) using the direct ip. is it possible there is agent filtering going on? all i'm seeing in the response log on the browser is 401 Unauthorized response to my POST

Serenaphic•10mo ago

The 401 comes from nginx most probably, so there might be something in the way that nginx is setup that blocks the request Maybe it's not allowing for you to post, only get

NighTimeOP•10mo ago

Given that it is used with the exact same configuration with 40 other servers, I doubt it's an inherent problem with the NPM, if there is any thing I can share that would help debug this, please don't hasitate to let me know. I can run custom code or run the log with added verbosity if that help you.

Solution

NighTime•10mo ago

I finally solved it by regenerating the docker container on another machine and pointing the NPM to it. I have no idea what caused the issue but it's good enough for me.

Serenaphic•10mo ago

Frankly, no idea either. That's the problem when there's so many redirects and elements in the chain. Glad you solved it somehow and the solution is good for you. It's not a realy answer but it might give a hint for the next one with a similar problem. My guess would be the VM/bridge layer somehow.

Gaming

Programming

Can't log in using my password when connecting through Nginx Proxy Manager