jlesage / docker-nginx-proxy-manager

Docker container for Nginx Proxy Manager
MIT License
785 stars 178 forks source link

Not possible to log in since last upgrade #225

Closed Flyingfufu closed 2 years ago

Flyingfufu commented 2 years ago

Hello,

First thanks for your hard work ! Using few of your container and love it.

Now, my issue. Since the last update done today to the latest version, the proxy seems still to be working fine, but I cannot log in anymore. Looking the container log, I can see the following error coming up endlessly:

[2022-1-2] [21:23:56] [Global ] › ✖ error certificate.meta.dns_provider_credentials.replaceAll is not a function [2022-1-2] [21:23:57] [Global ] › ℹ info Manual db configuration already exists, skipping config creation from environment variables [2022-1-2] [21:23:57] [Migrate ] › ℹ info Current database version: none

Any idea how to fix it ?

Best regards,

ch4ox commented 2 years ago

I have the same issue. There's also some problems with the reverse proxy feature itself, can't access some of my machines anymore.

There's a similar issue in the official NPM repository: https://github.com/jc21/nginx-proxy-manager/issues/1717

I think I'll rollback to the previous version for the time being.

jlesage commented 2 years ago

Thanks for reporting, I'm looking at this.

jlesage commented 2 years ago

Please try the latest Docker image and let met know you still have problems.

Flyingfufu commented 2 years ago

Thanks Jocelyn, the install with the latest image go through correctly to the end !

Thanks again for your prompt support.

ch4ox commented 2 years ago

Wow, that was fast. Working perfectly, thx again!

stavros-k commented 2 years ago

Hey, I'm still having the same problem with jlesage/nginx-proxy-manager:v1.24.1 Exact same log output as the reported issue.

jlesage commented 2 years ago

Humm the exact same error should not be possible with the latest version. Can you share the output of docker inspect <container name> command?

stavros-k commented 2 years ago

Hmm, it seems it was a weird caching issue on docker. Removed :v1.23.1 tag and let it start, and I got the mentioned errors. Did a forced update through Unraid's GUI. And started without errors.

Sorry to keep you waiting and thanks! :)

swoop124 commented 2 years ago

hello,

i have installed it just jet, on alpine and have the same issue. all sites sime to work fine but i can not login. (Bad Gateway) grafik

swoop124 commented 2 years ago

oh, i used this commandline to install it: wget --no-cache -qO - https://raw.githubusercontent.com/ej52/proxmox/main/lxc/nginx-proxy-manager/setup.sh | sh

regards

jlesage commented 2 years ago

Looks like you are not using the latest Docker image version?

swoop124 commented 2 years ago

hello,

thanks for the answer. I now installed version 2.9.15. as i mentioned, not in docker. And the result is the same but errormessages are little different. grafik

The messages occur every second. So i desidet do tested npm version 2.9.15 on docker. But the result is the same, i can't login to web-ui --> Bad Gateway grafik

I'am sorry, this is not the answer to the problem. But thanks

regards

swoop124 commented 2 years ago

hey,

i just looked into docker logs and found this from my nowly updated npm (v2.9.15) docker image: grafik

swoop124 commented 2 years ago

i have installed npm like this:

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      - 80:80
      - 443:443
      - 81:81
    network_mode: "bridge"
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "password"
      DB_MYSQL_NAME: "npm"
    volumes:
      - /opt/npm/data:/data
      - /opt/npm/letsencrypt:/etc/letsencrypt
    depends_on:
      - db
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: always
    network_mode: "bridge"
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'password'
    volumes:
      - /opt/npm/data/mysql:/var/lib/mysql
jlesage commented 2 years ago

Ah you are using the jc21 image. For this image, you should report your issue there: https://github.com/NginxProxyManager/nginx-proxy-manager/issues

swoop124 commented 2 years ago

hello,

so, i figured: When i run npm in the stardard docker-network (npm_default), it is working. But i need to use ipv6, for accesslist, so i have to do something. But i don't know what. In the moment i run npm in a seperate alpine-VM, there ipv6 is working just fine.