starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #711] ER_ACCESS_DENIED_ERROR: Access denied for user 'npm'@'10.0.0.1' (using password: YES) #603

New issue

Closed

opened 2026-02-26 06:33:36 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 06:33:36 +03:00

Owner

Originally created by @ProductiveAsparagus56 on GitHub (Nov 11, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/711

I have been at this for over a week now, i have followed every guide there is and nothing seems to work. When i use:
docker-compose up -d
it starts up and everything, but then as soon as i wanna log in, it gives me a Bad Gateway error. Now i looked into the logs and saw that nproxy_app_1 was spitting out loads of errors, the error is in the title of this issue.

I have configured config.json and docker-compose.yml to the guides on the official website. I have tried changing passwords in mysql but it says it can't change them. I have deleted my whole database and images and tried all over again 2 times and it still doesn't work.

Could someone please help me with this? I have no idea what to do anymore since there aren't many guides online for this, and if there are, i've probably tried most of them by now.

Thanks in advance.

Originally created by @ProductiveAsparagus56 on GitHub (Nov 11, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/711 I have been at this for over a week now, i have followed every guide there is and nothing seems to work. When i use: `docker-compose up -d` it starts up and everything, but then as soon as i wanna log in, it gives me a `Bad Gateway` error. Now i looked into the logs and saw that nproxy_app_1 was spitting out loads of errors, the error is in the title of this issue. I have configured config.json and docker-compose.yml to the guides on the official website. I have tried changing passwords in mysql but it says it can't change them. I have deleted my whole database and images and tried all over again 2 times and it still doesn't work. Could someone please help me with this? I have no idea what to do anymore since there aren't many guides online for this, and if there are, i've probably tried most of them by now. Thanks in advance.

kerem

2026-02-26 06:33:36 +03:00

closed this issue
added the
product-support
label

kerem commented

2026-02-26 06:33:37 +03:00

Author

Owner

@chris1668 commented on GitHub (Nov 11, 2020):

I encountered this issue when npm updated recently and the config file
changed, with the update and I was being silly and changed the
authentication method back to the old version of the config which gave me
the same error.
Once I got rid of my old config and let the image pull the new one down it
worked for me, I can send what my config looks like later if that would
help.

On Wed, Nov 11, 2020, 5:17 AM Audition-CSBlock notifications@github.com
wrote:

I have been at this for over a week now, i have followed every guide there
is and nothing seems to work. When i use:
docker-compose up -d
it starts up and everything, but then as soon as i wanna log in, it gives
me a Bad Gateway error. Now i looked into the logs and saw that
nproxy_app_1 was spitting out loads of errors, the error is in the title of
this issue.

I have configured config.json and docker-compose.yml to the guides on the
official website. I have tried changing passwords in mysql but it says it
can't change them. I have deleted my whole database and images and tried
all over again 2 times and it still doesn't work.

Could someone please help me with this? I have no idea what to do anymore
since there aren't many guides online for this, and if there are, i've
probably tried most of them by now.

Thanks in advance.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jc21/nginx-proxy-manager/issues/711, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2OJUBIFDJ664IYG3G6HBDSPKFIDANCNFSM4TR7NCEA
.

@chris1668 commented on GitHub (Nov 11, 2020): I encountered this issue when npm updated recently and the config file changed, with the update and I was being silly and changed the authentication method back to the old version of the config which gave me the same error. Once I got rid of my old config and let the image pull the new one down it worked for me, I can send what my config looks like later if that would help. On Wed, Nov 11, 2020, 5:17 AM Audition-CSBlock <notifications@github.com> wrote: > I have been at this for over a week now, i have followed every guide there > is and nothing seems to work. When i use: > docker-compose up -d > it starts up and everything, but then as soon as i wanna log in, it gives > me a Bad Gateway error. Now i looked into the logs and saw that > nproxy_app_1 was spitting out loads of errors, the error is in the title of > this issue. > > I have configured config.json and docker-compose.yml to the guides on the > official website. I have tried changing passwords in mysql but it says it > can't change them. I have deleted my whole database and images and tried > all over again 2 times and it still doesn't work. > > Could someone please help me with this? I have no idea what to do anymore > since there aren't many guides online for this, and if there are, i've > probably tried most of them by now. > > Thanks in advance. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/jc21/nginx-proxy-manager/issues/711>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA2OJUBIFDJ664IYG3G6HBDSPKFIDANCNFSM4TR7NCEA> > . >

kerem commented

2026-02-26 06:33:37 +03:00

Author

Owner

@ProductiveAsparagus56 commented on GitHub (Nov 11, 2020):

@chris

I encountered this issue when npm updated recently and the config file changed, with the update and I was being silly and changed the authentication method back to the old version of the config which gave me the same error. Once I got rid of my old config and let the image pull the new one down it worked for me, I can send what my config looks like later if that would help.
…
On Wed, Nov 11, 2020, 5:17 AM Audition-CSBlock @.***> wrote: I have been at this for over a week now, i have followed every guide there is and nothing seems to work. When i use: docker-compose up -d it starts up and everything, but then as soon as i wanna log in, it gives me a Bad Gateway error. Now i looked into the logs and saw that nproxy_app_1 was spitting out loads of errors, the error is in the title of this issue. I have configured config.json and docker-compose.yml to the guides on the official website. I have tried changing passwords in mysql but it says it can't change them. I have deleted my whole database and images and tried all over again 2 times and it still doesn't work. Could someone please help me with this? I have no idea what to do anymore since there aren't many guides online for this, and if there are, i've probably tried most of them by now. Thanks in advance. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#711>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2OJUBIFDJ664IYG3G6HBDSPKFIDANCNFSM4TR7NCEA .

Any help is appreciated! So yes, please send over your config cause maybe it will work for me too.

@ProductiveAsparagus56 commented on GitHub (Nov 11, 2020): @chris > I encountered this issue when npm updated recently and the config file changed, with the update and I was being silly and changed the authentication method back to the old version of the config which gave me the same error. Once I got rid of my old config and let the image pull the new one down it worked for me, I can send what my config looks like later if that would help. > […](#) > On Wed, Nov 11, 2020, 5:17 AM Audition-CSBlock ***@***.***> wrote: I have been at this for over a week now, i have followed every guide there is and nothing seems to work. When i use: docker-compose up -d it starts up and everything, but then as soon as i wanna log in, it gives me a Bad Gateway error. Now i looked into the logs and saw that nproxy_app_1 was spitting out loads of errors, the error is in the title of this issue. I have configured config.json and docker-compose.yml to the guides on the official website. I have tried changing passwords in mysql but it says it can't change them. I have deleted my whole database and images and tried all over again 2 times and it still doesn't work. Could someone please help me with this? I have no idea what to do anymore since there aren't many guides online for this, and if there are, i've probably tried most of them by now. Thanks in advance. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#711>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2OJUBIFDJ664IYG3G6HBDSPKFIDANCNFSM4TR7NCEA> . Any help is appreciated! So yes, please send over your config cause maybe it will work for me too.

kerem commented

2026-02-26 06:33:37 +03:00

Author

Owner

@chris1668 commented on GitHub (Nov 11, 2020):

So my old production.json config looked something like this:
{
"database": {
"engine": "mysql",
"host": "127.0.0.1",
"name": "nginxproxymanager",
"user": "nginxproxymanager",
"password": "password123",
"port": 3306
},
"jwt": {
"key": "-----BEGIN RSA PRIVATE KEY-----END RSA PRIVATE KEY-----",
"pub": "-----BEGIN PUBLIC KEY----------END PUBLIC KEY-----"
}
}

My new production.json after the docker image updated to NPM v2.6 looks
like this:
{
"database": {
"engine": "knex-native",
"knex": {
"client": "sqlite3",
"connection": {
"filename": "/config/database.sqlite"
},
"useNullAsDefault": true
}
},
"jwt": {
"key": "-----BEGIN RSA PRIVATE KEY----------END RSA PRIVATE KEY-----",
"pub": "-----BEGIN PUBLIC KEY----------END PUBLIC KEY-----"
}
}

Adjusting that config in any way always leads me back to the bad gateway
error so Ive left it alone and only had one other issue that was with my
firefox browser cache and once that was cleared its been working as it
always has.
The difference seems to be that it handles an internal sqlitedb without
issues, but can no longer get it to talk to a separate DB container even if
it is on a custom docker network with it and the DB is working for
everything else.
Again I tried setting my MariaDBs authentication method to the legacy
method to see if NPM just couldnt match up to the auth method MariaDB was
expecting, but nothing I tried could resolve that error, so I stopped
torturing myself and accepted the config that works.

On Wed, Nov 11, 2020 at 7:42 AM Audition-CSBlock notifications@github.com
wrote:

@chris https://github.com/chris

I encountered this issue when npm updated recently and the config file
changed, with the update and I was being silly and changed the
authentication method back to the old version of the config which gave me
the same error. Once I got rid of my old config and let the image pull the
new one down it worked for me, I can send what my config looks like later
if that would help.
… <#m_7776666536255278512_>
On Wed, Nov 11, 2020, 5:17 AM Audition-CSBlock @.***> wrote: I have
been at this for over a week now, i have followed every guide there is and
nothing seems to work. When i use: docker-compose up -d it starts up and
everything, but then as soon as i wanna log in, it gives me a Bad Gateway
error. Now i looked into the logs and saw that nproxy_app_1 was spitting
out loads of errors, the error is in the title of this issue. I have
configured config.json and docker-compose.yml to the guides on the official
website. I have tried changing passwords in mysql but it says it can't
change them. I have deleted my whole database and images and tried all over
again 2 times and it still doesn't work. Could someone please help me with
this? I have no idea what to do anymore since there aren't many guides
online for this, and if there are, i've probably tried most of them by now.
Thanks in advance. — You are receiving this because you are subscribed to
this thread. Reply to this email directly, view it on GitHub <#711
https://github.com/jc21/nginx-proxy-manager/issues/711>, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2OJUBIFDJ664IYG3G6HBDSPKFIDANCNFSM4TR7NCEA
.

Any help is appreciated! So yes, please send over your config cause maybe
it will work for me too.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jc21/nginx-proxy-manager/issues/711#issuecomment-725495940,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2OJUGMLVWZBDZQTYGDEF3SPKWH5ANCNFSM4TR7NCEA
.

@chris1668 commented on GitHub (Nov 11, 2020): So my old production.json config looked something like this: { "database": { "engine": "mysql", "host": "127.0.0.1", "name": "nginxproxymanager", "user": "nginxproxymanager", "password": "password123", "port": 3306 }, "jwt": { "key": "-----BEGIN RSA PRIVATE KEY-----END RSA PRIVATE KEY-----", "pub": "-----BEGIN PUBLIC KEY----------END PUBLIC KEY-----" } } My new production.json after the docker image updated to NPM v2.6 looks like this: { "database": { "engine": "knex-native", "knex": { "client": "sqlite3", "connection": { "filename": "/config/database.sqlite" }, "useNullAsDefault": true } }, "jwt": { "key": "-----BEGIN RSA PRIVATE KEY----------END RSA PRIVATE KEY-----", "pub": "-----BEGIN PUBLIC KEY----------END PUBLIC KEY-----" } } Adjusting that config in any way always leads me back to the bad gateway error so Ive left it alone and only had one other issue that was with my firefox browser cache and once that was cleared its been working as it always has. The difference seems to be that it handles an internal sqlitedb without issues, but can no longer get it to talk to a separate DB container even if it is on a custom docker network with it and the DB is working for everything else. Again I tried setting my MariaDBs authentication method to the legacy method to see if NPM just couldnt match up to the auth method MariaDB was expecting, but nothing I tried could resolve that error, so I stopped torturing myself and accepted the config that works. On Wed, Nov 11, 2020 at 7:42 AM Audition-CSBlock <notifications@github.com> wrote: > @chris <https://github.com/chris> > > I encountered this issue when npm updated recently and the config file > changed, with the update and I was being silly and changed the > authentication method back to the old version of the config which gave me > the same error. Once I got rid of my old config and let the image pull the > new one down it worked for me, I can send what my config looks like later > if that would help. > … <#m_7776666536255278512_> > On Wed, Nov 11, 2020, 5:17 AM Audition-CSBlock *@*.***> wrote: I have > been at this for over a week now, i have followed every guide there is and > nothing seems to work. When i use: docker-compose up -d it starts up and > everything, but then as soon as i wanna log in, it gives me a Bad Gateway > error. Now i looked into the logs and saw that nproxy_app_1 was spitting > out loads of errors, the error is in the title of this issue. I have > configured config.json and docker-compose.yml to the guides on the official > website. I have tried changing passwords in mysql but it says it can't > change them. I have deleted my whole database and images and tried all over > again 2 times and it still doesn't work. Could someone please help me with > this? I have no idea what to do anymore since there aren't many guides > online for this, and if there are, i've probably tried most of them by now. > Thanks in advance. — You are receiving this because you are subscribed to > this thread. Reply to this email directly, view it on GitHub <#711 > <https://github.com/jc21/nginx-proxy-manager/issues/711>>, or unsubscribe > https://github.com/notifications/unsubscribe-auth/AA2OJUBIFDJ664IYG3G6HBDSPKFIDANCNFSM4TR7NCEA > . > > Any help is appreciated! So yes, please send over your config cause maybe > it will work for me too. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/jc21/nginx-proxy-manager/issues/711#issuecomment-725495940>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA2OJUGMLVWZBDZQTYGDEF3SPKWH5ANCNFSM4TR7NCEA> > . >

kerem commented

2026-02-26 06:33:37 +03:00

Author

Owner

@ProductiveAsparagus56 commented on GitHub (Nov 11, 2020):

@chris1668 Haha! Just when you posted that i figured that out on my own! Thank you so much for the help though and this should really be looked into cause i heard that a lot of people are having problems with this.

@ProductiveAsparagus56 commented on GitHub (Nov 11, 2020): @chris1668 Haha! Just when you posted that i figured that out on my own! Thank you so much for the help though and this should really be looked into cause i heard that a lot of people are having problems with this.

kerem commented

2026-02-26 06:33:37 +03:00

Author

Owner

@lockheed commented on GitHub (Feb 10, 2022):

I am having the same issue since about a week. Only 1 out of 5 login attempts succeeds.

Where is this .jason file located? I was unable to find it.

@lockheed commented on GitHub (Feb 10, 2022): I am having the same issue since about a week. Only 1 out of 5 login attempts succeeds. Where is this .jason file located? I was unable to find it.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#603

No description provided.

Rows
Columns