October 27, 20205 yr 6 hours ago, mattie112 said: You can try something like this: docker exec -it NginxProxyManager sh # you are now in the container mysql # you are now connected to the internal mysql shell select * from user; select * from user_permission; select * from auth; You can check IF there is an user (that is not disabled/deleted) and if you are using the correct username. If not you can update the password or insert a new user. I am guessing the standard mysql/mariadb encryption is used to in order to change the password: update user set secred=PASSWORD('yourpasshere') where id = <id_from_your_user>; But perhaps @Djoss can confirm if this is the correct hasing/method. (you could also create a new instance of NPM and check the tables for the default user and then copy that over to your existing instance) I was able to do the docker exec -it NginxProxyManager sh command When i type mysql I get sh: mysql: not found When i run docker exec NginxProxyManager sqlite3 -cmd 'SELECT * from user;' /config/database.sqlite i do see my login user email
October 28, 20205 yr Author 3 hours ago, thunderclap said: Here are the three tabs I've filled stuff out in, nothing in Advanced Not sure what you are trying to do with the custom location, but it doesn't look right. Can you try to remove it to see if it fixes the issue ?
October 28, 20205 yr Author 1 hour ago, HellraiserOSU said: I was able to do the docker exec -it NginxProxyManager sh command When i type mysql I get sh: mysql: not found When i run docker exec NginxProxyManager sqlite3 -cmd 'SELECT * from user;' /config/database.sqlite i do see my login user email Did you try to reset you password ?
October 28, 20205 yr 12 minutes ago, Djoss said: Not sure what you are trying to do with the custom location, but it doesn't look right. Can you try to remove it to see if it fixes the issue ? Removed but I'm still getting the too many redirects error.
October 28, 20205 yr 1 hour ago, Djoss said: Did you try to reset you password ? I take it that was it?
October 28, 20205 yr It seems to be yeah: #!/bin/sh usage() { echo "usage: $(basename "$0") USER_EMAIL [PASSWORD] Reset password of a Nginx Proxy Manager user. Arguments: USER_EMAIL Email address of the user to reset the password. PASSWORD Optional new password of the user. If not set, password is set to 'changeme'. " exit 1 }
October 28, 20205 yr 2 hours ago, mattie112 said: It seems to be yeah: #!/bin/sh usage() { echo "usage: $(basename "$0") USER_EMAIL [PASSWORD] Reset password of a Nginx Proxy Manager user. Arguments: USER_EMAIL Email address of the user to reset the password. PASSWORD Optional new password of the user. If not set, password is set to 'changeme'. " exit 1 } Tried it without a password and with a password. Still says no relevant user found I'm getting close to just blowing it away, but I would like to see if i can fix this so if it happens again in the future i don't have to redo it all. The reverse proxies are still working at least. Edited October 28, 20205 yr by HellraiserOSU
October 28, 20205 yr Author 13 hours ago, thunderclap said: Removed but I'm still getting the too many redirects error. And what the following command is returning: curl -v http://192.168.50.108
October 28, 20205 yr Author 2 hours ago, HellraiserOSU said: Tried it without a password and with a password. Still says no relevant user found I'm getting close to just blowing it away, but I would like to see if i can fix this so if it happens again in the future i don't have to redo it all. The reverse proxies are still working at least. The error you get is really because the email entered in the login page is not found in the database. Do you see any spaces around the email address in the db ? Did you try to manually type the email address in the login page (no copy/paste, no automatic filling)?
October 28, 20205 yr 29 minutes ago, Djoss said: The error you get is really because the email entered in the login page is not found in the database. Do you see any spaces around the email address in the db ? Did you try to manually type the email address in the login page (no copy/paste, no automatic filling)? Yup. So I use firefox and up until a week ago it was working. I'd double click and have it auto fill and it worked. I just put in a reverse proxy for AutoMute. And now I've tried typing it in manually. Still no joy.. I did the same steps my QA would have me do at my dev job
October 28, 20205 yr Hmmm that is really strange.... Perhaps just for funs: stop your container. Rename the appdata/npm folder. Start the container (you should now have a fresh instance. Can you login now? Then change the user/password to what it should be. Can you login now? Then try the reset password option. If everything works I have no idea. If that doesn't work either there is something strange with your browser (adding a space or something) or there is something horrible broken. And just to confirm: are you 100% sure you try to login into the correct NPM instance? So is there only 1 container running?
October 28, 20205 yr 2 hours ago, mattie112 said: Hmmm that is really strange.... Perhaps just for funs: stop your container. Rename the appdata/npm folder. Start the container (you should now have a fresh instance. Can you login now? Then change the user/password to what it should be. Can you login now? Then try the reset password option. If everything works I have no idea. If that doesn't work either there is something strange with your browser (adding a space or something) or there is something horrible broken. And just to confirm: are you 100% sure you try to login into the correct NPM instance? So is there only 1 container running? Yup 100% sure. So I backed up app data to my backup folder. Changed the name of the app data directory so i have two copies. Started the container I was able to login as [email protected] and changeme as password It asked me to create a user. I did.. Then I went and changed the password.. copy and pasted the password into a notepad and used it to change. Logged out.. Now I can't login .. It says no relevant user found. -Update- And I just tried again blowing away the appdata and changing it with a very simple abcd.1234 password.. same issue.. no relavant user found Edited October 28, 20205 yr by HellraiserOSU
October 28, 20205 yr Author 2 hours ago, HellraiserOSU said: Yup 100% sure. So I backed up app data to my backup folder. Changed the name of the app data directory so i have two copies. Started the container I was able to login as [email protected] and changeme as password It asked me to create a user. I did.. Then I went and changed the password.. copy and pasted the password into a notepad and used it to change. Logged out.. Now I can't login .. It says no relevant user found. -Update- And I just tried again blowing away the appdata and changing it with a very simple abcd.1234 password.. same issue.. no relavant user found I just tried the same steps and it worked for me... Is it possible for you to share your appdata folder of your "test" instance? I can try to see if I can reproduce using your data.
October 28, 20205 yr 49 minutes ago, Djoss said: I just tried the same steps and it worked for me... Is it possible for you to share your appdata folder of your "test" instance? I can try to see if I can reproduce using your data. I think I found the issue. It's the email I use.. I tried like [email protected] and many variants and I was able to login fine.. but once I use my email .. it says no relevant user.. I'll DM you the email I use as it's a personal one
October 28, 20205 yr I figured it out My email has capital letters. Up until the last two releases, I was able to login as [email protected] for example. But now I see that it turns it into [email protected] so all lower case. I reinstalled my appdata and used all lower case for the email and I was able to login.. Sorry about that!
October 28, 20205 yr 1 hour ago, HellraiserOSU said: My email has capital letters. You may prefer to use capital letters as a style, and when you use it as an email it doesn't matter, but no, your email doesn't have capital letters. It doesn't have lower case either, it just has letters, numbers, and possibly symbols. https://www.mailigen.com/blog/does-capitalization-matter-in-email-addresses/ There are exceptions to this, but the practical application means that all alphabet characters in an email address are treated as lowercase for processing.
October 29, 20205 yr 12 hours ago, Djoss said: And what the following command is returning: curl -v http://192.168.50.108 From the VM I get: * Rebuilt URL to: http://192.168.50.108/ * Trying 192.168.50.108... * TCP_NODELAY set * Connected to 192.168.50.108 (192.168.50.108) port 80 (#0) > GET / HTTP/1.1 > Host: 192.168.50.108 > User-Agent: curl/7.58.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Thu, 29 Oct 2020 01:25:31 GMT < Content-Type: text/html; charset=UTF-8 < Content-Length: 0 < Connection: keep-alive < X-UA-Compatible: IE=edge < X-Redirect-By: WordPress < Location: https://marcbuhmann.com/ < * Connection #0 to host 192.168.50.108 left intact From my Unraid server I get: * Trying 192.168.50.108:80... * TCP_NODELAY set * Connected to 192.168.50.108 (192.168.50.108) port 80 (#0) > GET / HTTP/1.1 > Host: 192.168.50.108 > User-Agent: curl/7.67.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Thu, 29 Oct 2020 01:27:35 GMT < Content-Type: text/html; charset=UTF-8 < Content-Length: 0 < Connection: keep-alive < X-UA-Compatible: IE=edge < X-Redirect-By: WordPress < Location: https://marcbuhmann.com/ < * Connection #0 to host 192.168.50.108 left intact Edited October 29, 20205 yr by thunderclap
October 29, 20205 yr Author 14 hours ago, HellraiserOSU said: I figured it out My email has capital letters. Up until the last two releases, I was able to login as [email protected] for example. But now I see that it turns it into [email protected] so all lower case. I reinstalled my appdata and used all lower case for the email and I was able to login.. Sorry about that! Good catch. I will try to find what changed and how this can be fixed. Edited October 29, 20205 yr by Djoss
October 29, 20205 yr Nice one, I can understand that that is really confusing (imo when checking an email adres casing should not matter, so strlower in the DB and strlower the user input and then check )
October 29, 20205 yr Author 11 hours ago, thunderclap said: From the VM I get: * Rebuilt URL to: http://192.168.50.108/ * Trying 192.168.50.108... * TCP_NODELAY set * Connected to 192.168.50.108 (192.168.50.108) port 80 (#0) > GET / HTTP/1.1 > Host: 192.168.50.108 > User-Agent: curl/7.58.0 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Thu, 29 Oct 2020 01:25:31 GMT < Content-Type: text/html; charset=UTF-8 < Content-Length: 0 < Connection: keep-alive < X-UA-Compatible: IE=edge < X-Redirect-By: WordPress < Location: https://marcbuhmann.com/ < * Connection #0 to host 192.168.50.108 left intact From my Unraid server I get: * Trying 192.168.50.108:80... * TCP_NODELAY set * Connected to 192.168.50.108 (192.168.50.108) port 80 (#0) > GET / HTTP/1.1 > Host: 192.168.50.108 > User-Agent: curl/7.67.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Server: nginx < Date: Thu, 29 Oct 2020 01:27:35 GMT < Content-Type: text/html; charset=UTF-8 < Content-Length: 0 < Connection: keep-alive < X-UA-Compatible: IE=edge < X-Redirect-By: WordPress < Location: https://marcbuhmann.com/ < * Connection #0 to host 192.168.50.108 left intact Ok, so this confirms that your WP instance is doing a redirect...
October 29, 20205 yr 57 minutes ago, Djoss said: Ok, so this confirms that your WP instance is doing a redirect... Hmm... not sure where the problem is then. I've disabled all plugins and removed all custom code from .htaccess so it should be working. Thanks for helping narrow down the problem.
November 1, 20205 yr Hi, I'm trying to create a new proxy host but keep getting the error below. I've created the CNAME record already for my domain. I have created three other proxy hosts in the past, maybe about 6-9 months ago and this is the first new one since. [11/1/2020] [9:52:45 AM] [Nginx ] › ℹ info Reloading Nginx [11/1/2020] [9:52:45 AM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #28: recipes.customdomain.com [11/1/2020] [9:52:50 AM] [Nginx ] › ℹ info Reloading Nginx [11/1/2020] [9:52:50 AM] [Express ] › ⚠ warning Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-28" --agree-tos --email "[email protected]" --preferred-challenges "dns,http" --domains "recipes.customdomain.com" Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for recipes.customdomain.com Using the webroot path /config/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Challenge failed for domain recipes.customdomain.com http-01 challenge for recipes.customdomain.com Cleaning up challenges Some challenges have failed.
November 2, 20205 yr Author 10 hours ago, itlists said: Hi, I'm trying to create a new proxy host but keep getting the error below. I've created the CNAME record already for my domain. I have created three other proxy hosts in the past, maybe about 6-9 months ago and this is the first new one since. [11/1/2020] [9:52:45 AM] [Nginx ] › ℹ info Reloading Nginx [11/1/2020] [9:52:45 AM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #28: recipes.customdomain.com [11/1/2020] [9:52:50 AM] [Nginx ] › ℹ info Reloading Nginx [11/1/2020] [9:52:50 AM] [Express ] › ⚠ warning Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-28" --agree-tos --email "[email protected]" --preferred-challenges "dns,http" --domains "recipes.customdomain.com" Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for recipes.customdomain.com Using the webroot path /config/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Challenge failed for domain recipes.customdomain.com http-01 challenge for recipes.customdomain.com Cleaning up challenges Some challenges have failed. Look at /mnt/user/appdata/NginxProxyManager/log/letsencrypt.log, you should have more details about the failure.
November 2, 20205 yr 1 hour ago, Djoss said: Look at /mnt/user/appdata/NginxProxyManager/log/letsencrypt.log, you should have more details about the failure. Here's the log file attached Seems to be an issue with how the proxy feature of cloudflare works. Need to disable that to get the LE challenge to complete. Once that's done, re-enabling the cloudflare proxy and all is good. Edited November 2, 20205 yr by itlists
November 2, 20205 yr Just keep in mind that if your certificate needs to be renewed it will most likely fail due to the same issue!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.