[Support] Djoss - Nginx Proxy Manager


Djoss

Recommended Posts

7 hours ago, thunderclap said:

Accessing via IP+port does work albeit site site is broken; several images won't display.

For sure you first need to make sure the site works as expected in this scenario, since you will have the same issues behind a reverse proxy.

7 hours ago, thunderclap said:

Network tab doesn't show anything questionable, at least to my layman eyes.

You should see the multiple redirections, or at least a request returning an error.

Link to comment

Guys, i need some help, npm have been working fine for me for quite some time, suddenly today it stopped working.

below is are some entires from the log.

nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[10/26/2020] [10:51:54 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[10/26/2020] [10:51:54 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[10/26/2020] [10:51:54 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[10/26/2020] [10:51:54 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[10/26/2020] [10:51:54 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[10/26/2020] [10:51:54 PM] [Global ] › ℹ info Backend PID 5616 listening on port 3000 ...
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258

 

on inspection on the following line 

 

Capture.PNG

Link to comment
44 minutes ago, huangtf said:

Guys, i need some help, npm have been working fine for me for quite some time, suddenly today it stopped working.

below is are some entires from the log.

nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[10/26/2020] [10:51:54 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[10/26/2020] [10:51:54 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[10/26/2020] [10:51:54 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[10/26/2020] [10:51:54 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[10/26/2020] [10:51:54 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[10/26/2020] [10:51:54 PM] [Global ] › ℹ info Backend PID 5616 listening on port 3000 ...
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258
[nginx] starting...
nginx: [emerg] invalid number of arguments in "set_real_ip_from" directive in /etc/nginx/conf.d/include/ip_ranges.conf:258

 

on inspection on the following line 

 

Capture.PNG

What the following commands are returning ?

curl https://www.cloudflare.com/ips-v4

 

curl https://www.cloudflare.com/ips-v6

 

Link to comment
11 hours ago, Djoss said:

To be execute in unRAID terminal, not from the container itself.

If you want to run from container, do "add-pkg curl" before.

root@Tower:~# curl https://www.cloudflare.com/ips-v6
2400:cb00::/32
2606:4700::/32
2803:f800::/32
2405:b500::/32
2405:8100::/32
2a06:98c0::/29
2c0f:f248::/32
root@Tower:~# curl https://www.cloudflare.com/ips-v4
173.245.48.0/20
103.21.244.0/22
103.22.200.0/22
103.31.4.0/22
141.101.64.0/18
108.162.192.0/18
190.93.240.0/20
188.114.96.0/20
197.234.240.0/22
198.41.128.0/17
162.158.0.0/15
104.16.0.0/12
172.64.0.0/13
131.0.72.0/22
root@Tower:~# 

 

looks normal to me

Link to comment
1 hour ago, HellraiserOSU said:

I was able to login last week, but with the last two updates I'm now getting no relevant user found when trying to login. Can someone help me with this issue please?

 

I also tried [email protected] and changeme  and it still says no relevant user found.

Do you want to try and fix your current installation or just start over? For the last one you can remove the container, then remove /mnt/user/AppData/ngnx-proxy-manager and then reacreate it for a clean start.

Link to comment
On 10/26/2020 at 6:21 AM, Djoss said:

For sure you first need to make sure the site works as expected in this scenario, since you will have the same issues behind a reverse proxy.

You should see the multiple redirections, or at least a request returning an error.

If you'd like to see what I'm seeing the URL is here. I do see quite a few 301 in the Network list under Developer Tools, not sure how to read it though. Right now I have it pointing from NginxProxyManager to my Ubuntu VM which has VestaCP installed.

Link to comment
2 hours ago, mattie112 said:

Do you want to try and fix your current installation or just start over? For the last one you can remove the container, then remove /mnt/user/AppData/ngnx-proxy-manager and then reacreate it for a clean start.

I'd like to fix it if I can.. I have like 10 reverse proxies while not too many, just be annoying to redo :)

Link to comment
15 minutes ago, HellraiserOSU said:

I'd like to fix it if I can.. I have like 10 reverse proxies while not too many, just be annoying to redo :)

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)

Link to comment
7 hours ago, HellraiserOSU said:

I was able to login last week, but with the last two updates I'm now getting no relevant user found when trying to login. Can someone help me with this issue please?

 

I also tried [email protected] and changeme  and it still says no relevant user found.

Are you using the correct user ?  You can list users with the following command:

docker exec NginxProxyManager sqlite3 -cmd 'SELECT * from user;' /config/database.sqlite

 

Link to comment
6 hours ago, huangtf said:

root@Tower:~# curl https://www.cloudflare.com/ips-v6
2400:cb00::/32
2606:4700::/32
2803:f800::/32
2405:b500::/32
2405:8100::/32
2a06:98c0::/29
2c0f:f248::/32
root@Tower:~# curl https://www.cloudflare.com/ips-v4
173.245.48.0/20
103.21.244.0/22
103.22.200.0/22
103.31.4.0/22
141.101.64.0/18
108.162.192.0/18
190.93.240.0/20
188.114.96.0/20
197.234.240.0/22
198.41.128.0/17
162.158.0.0/15
104.16.0.0/12
172.64.0.0/13
131.0.72.0/22
root@Tower:~# 

 

looks normal to me

Yes, this is the expected output.  Not sure what happened.  Let me know if the problem comes back.

Link to comment
2 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)

The latest image now uses sqlite instead of mariadb.  See my previous command for the SQL command to run.

 

If password needs to ne be reset:

docker run NginxProxyManager /opt/nginx-proxy-manager/bin/reset-password <user> <password>

 

Link to comment
3 hours ago, thunderclap said:

If you'd like to see what I'm seeing the URL is here. I do see quite a few 301 in the Network list under Developer Tools, not sure how to read it though. Right now I have it pointing from NginxProxyManager to my Ubuntu VM which has VestaCP installed.

Using curl, we see that a redirect to the same URL is returned:

curl -v https://marcbuhmann.com/
*   Trying 76.243.195.200:443...
* TCP_NODELAY set
* Connected to marcbuhmann.com (76.243.195.200) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /usr/share/curl/ca-bundle.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=marcbuhmann.com
*  start date: Oct 23 20:33:34 2020 GMT
*  expire date: Jan 21 20:33:34 2021 GMT
*  subjectAltName: host "marcbuhmann.com" matched cert's "marcbuhmann.com"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x47c570)
> GET / HTTP/2
> Host: marcbuhmann.com
> user-agent: curl/7.67.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 301
< server: openresty
< date: Tue, 27 Oct 2020 17:51:07 GMT
< content-type: text/html; charset=UTF-8
< content-length: 0
< location: https://marcbuhmann.com/
< x-ua-compatible: IE=edge
< x-redirect-by: WordPress
< x-served-by: marcbuhmann.com
<

Can you share the config of your proxy host ?

Link to comment
42 minutes ago, Djoss said:

Using curl, we see that a redirect to the same URL is returned:


curl -v https://marcbuhmann.com/
*   Trying 76.243.195.200:443...
* TCP_NODELAY set
* Connected to marcbuhmann.com (76.243.195.200) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /usr/share/curl/ca-bundle.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=marcbuhmann.com
*  start date: Oct 23 20:33:34 2020 GMT
*  expire date: Jan 21 20:33:34 2021 GMT
*  subjectAltName: host "marcbuhmann.com" matched cert's "marcbuhmann.com"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x47c570)
> GET / HTTP/2
> Host: marcbuhmann.com
> user-agent: curl/7.67.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 301
< server: openresty
< date: Tue, 27 Oct 2020 17:51:07 GMT
< content-type: text/html; charset=UTF-8
< content-length: 0
< location: https://marcbuhmann.com/
< x-ua-compatible: IE=edge
< x-redirect-by: WordPress
< x-served-by: marcbuhmann.com
<

Can you share the config of your proxy host ?

I've attached what I think you're looking for.

 

Edited by thunderclap
Removed config
Link to comment
4 hours ago, Djoss said:

Are you using the correct user ?  You can list users with the following command:


docker exec NginxProxyManager sqlite3 -cmd 'SELECT * from user;' /config/database.sqlite

 

I ran that command it it's the same user. I use a pasword manager to login and it's definitely the same.

 

here's what it shows

image.thumb.png.87742887da311530d9ee379a6556096e.png

Edited by HellraiserOSU
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.