3 hours ago, Kopernikus said:

If I look into the log I get this error:

 

Please execute the following to check all permissions:

ls -la /mnt/user/appdata/Nginx-Proxy-Manager-Official /mnt/user/appdata/Nginx-Proxy-Manager-Official/*
ls -la /tmp/nginx-proxy-manager /tmp/nginx-proxy-manager/*

 

Did you restore in the past a backup of your appdata directory and/or NPM directory?

3 minutes ago, mgutt said:

Please execute the following to check all permissions:

ls -la /mnt/user/appdata/Nginx-Proxy-Manager-Official /mnt/user/appdata/Nginx-Proxy-Manager-Official/*
ls -la /tmp/nginx-proxy-manager /tmp/nginx-proxy-manager/*

 

Did you restore in the past a backup of your appdata directory and/or NPM directory?

 

Hi,

 

I got:

 

/mnt/user/appdata/Nginx-Proxy-Manager-Official:
total 0
drwxrwxrwx 1 root   root   37 Sep  8 11:46 ./
drwxrwxrwx 1 nobody users  42 Sep  8 11:46 ../
drwxrwxrwx 1 nobody users 120 Sep  8 15:11 data/
drwxrwxrwx 1 nobody users  27 Sep  8 15:11 letsencrypt/

/mnt/user/appdata/Nginx-Proxy-Manager-Official/data:
total 104
drwxrwxrwx 1 nobody users    120 Sep  8 15:11 ./
drwxrwxrwx 1 root   root      37 Sep  8 11:46 ../
drwxr-xr-x 1 root   root       6 Sep  8 11:47 access/
drwxr-xr-x 1 root   root      19 Sep  8 13:07 custom_ssl/
-rw-r--r-- 1 root   root  106496 Sep  8 15:11 database.sqlite
drwxr-xr-x 1 root   root       6 Sep  8 11:47 letsencrypt-acme-challenge/
drwxr-xr-x 1 root   root       6 Sep  8 11:47 logs/
drwxr-xr-x 1 root   root     171 Sep  8 11:47 nginx/

/mnt/user/appdata/Nginx-Proxy-Manager-Official/letsencrypt:
total 0
drwxrwxrwx 1 nobody users 27 Sep  8 15:11 ./
drwxrwxrwx 1 root   root  37 Sep  8 11:46 ../
drwxr-xr-x 1 root   root  43 Sep  8 11:47 renewal-hooks/

 and:
 

total 0
drwxrwxrwx  4 root root  80 Sep  3 16:55 ./
drwxrwxrwt 16 root root 340 Sep  8 12:07 ../
drwxrwxrwx  3 root root  60 Sep  3 16:55 data/
drwxrwxrwx  3 root root  60 Sep  3 16:55 var/

/tmp/nginx-proxy-manager/data:
total 0
drwxrwxrwx 3 root root  60 Sep  3 16:55 ./
drwxrwxrwx 4 root root  80 Sep  3 16:55 ../
drwxrwxrwx 2 root root 300 Sep  8 08:59 logs/

/tmp/nginx-proxy-manager/var:
total 0
drwxrwxrwx 3 root   root  60 Sep  3 16:55 ./
drwxrwxrwx 4 root   root  80 Sep  3 16:55 ../
drwxrwxrwx 4 nobody users 80 Sep  3 16:56 log/

 

I haven't restored any backups, it's on a fresh install.

34 minutes ago, Kopernikus said:

it's on a fresh install.

Ok, I found the bug and updated the container template. Please uninstall NPM and delete the NPM files through the Appdata Cleanup Plugin. You can re-install NPM in ~20 minutes (CA is only updated every 2 hours).

Ok, thx 🙂

 

Btw, one more question, I would like to use the Krusader docker on NPM, the proxy should forwared to:

 

http://10.10.100.10:6080/vnc.html?resize=remote&host=10.10.100.10&port=6080&autoconnect=1

 

Can you help me set this up in NPM?

 

 

13 minutes ago, Kopernikus said:

http://10.10.100.10:6080/vnc.html?resize=remote&host=10.10.100.10&port=6080&autoconnect=1

 

What happens if you open http://10.10.100.10:6080/. Does it forward to the full url? If yes, you could try to add a proxy host with your domain which targets 10.10.100.10 and the port 6080. It then should forward from "yourdomain.com" to "yourdomain.com/vnc.html....". 

 

If this does not work, you could try to add an advanced config rule in the proxy host like this:

location = / {
  return 301 $scheme://yourdomain.com/vnc.html?resize=remote&host=10.10.100.10&port=6080&autoconnect=1
}

 

But I'm unsure regarding the URL parameters. Maybe host and port in the URL needs to be changed as well?! Needs testing.

23 hours ago, mgutt said:

What happens if you open http://10.10.100.10:6080/. Does it forward to the full url? If yes, you could try to add a proxy host with your domain which targets 10.10.100.10 and the port 6080. It then should forward from "yourdomain.com" to "yourdomain.com/vnc.html....". 

 

If this does not work, you could try to add an advanced config rule in the proxy host like this:

location = / {
  return 301 $scheme://yourdomain.com/vnc.html?resize=remote&host=10.10.100.10&port=6080&autoconnect=1
}

 

But I'm unsure regarding the URL parameters. Maybe host and port in the URL needs to be changed as well?! Needs testing.

 

Got it working just by adding /vnc.html to custom locations.

Also got a few questions about some settings:

 

Cache Assets --> can I turn this on for all my proxy hostst? or are there any exceptions?

Block Common Exploits --> switched on for all my proxy host 

Websockets Support --> only turned on when needed?

 

Force SSL/HTTP/2/HSTS enable --> switched on for all my proxy hosts or are there any drawbacks?

HSTS subdomain ---> on or off?

 

And in the access list there an option "pass auth to Host", what's this?

 

Thx!

 

 

Starting last night, when I try going to NginxProxyManager it just does not want to load anymore.

 

Here is a quick video showing what I mean: https://youtu.be/x3jTCwPrHPM

 

Here is an image of the container's configuration page: https://i.imgur.com/ZsUsBrl.png

 

Could I get some assistance please? Because of this my users can't access Nextcloud so I'd like to get this back up and running.

Edited September 9, 20214 yr by jeremytodd1

1 minute ago, jeremytodd1 said:

Starting last night, when I try going to NginxProxyManager it just does not want to load anymore.

You are not using NPM Official. Please ask here:

https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/

 

 

22 minutes ago, Kopernikus said:

Got it working just by adding /vnc.html to custom locations.

And now you open yourdomain.com or yourdomain.com/vnc.html?

 

29 minutes ago, Kopernikus said:

Cache Assets --> can I turn this on for all my proxy hostst? or are there any exceptions?

 

By enabling this option, these rules are added to the nginx config:

cat /etc/nginx/conf.d/include/assets.conf
location ~* ^.*\.(css|js|jpe?g|gif|png|woff|eot|ttf|svg|ico|css\.map|js\.map)$ {
        if_modified_since off;

        # use the public cache
        proxy_cache public-cache;
        proxy_cache_key $host$request_uri;

        # ignore these headers for media
        proxy_ignore_headers Set-Cookie Cache-Control Expires X-Accel-Expires;

        # cache 200s and also 404s (not ideal but there are a few 404 images for some reason)
        proxy_cache_valid any 30m;
        proxy_cache_valid 404 1m;

        # strip this header to avoid If-Modified-Since requests
        proxy_hide_header Last-Modified;
        proxy_hide_header Cache-Control;
        proxy_hide_header Vary;

        proxy_cache_bypass 0;
        proxy_no_cache 0;

        proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504 http_404;
        proxy_connect_timeout 5s;
        proxy_read_timeout 45s;

        expires @30m;
        access_log  off;

        include conf.d/include/proxy.conf;
}

 

As you can see many files depending on their extension are cached by the proxy itself. By that your proxy "guards" your target container as those requests are not forwarded anymore. It simply means, that the file is copied to the nginx container. This can be useful as nginx is very fast in serving static files, but it can result in a high disk usage. For example if you use Nextcloud with huge files, this could fully utilize your SSD.

 

34 minutes ago, Kopernikus said:

Websockets Support --> only turned on when needed?

Yes. Some containers like Plex or Unifi need it. By that the container is able to send requests/data to the user while the website stays open. Shouldn' t be a downside to allow it by default, but not necessary of course.

 

37 minutes ago, Kopernikus said:

Force SSL

Force SSL forwards all "http" requests to "https"

 

45 minutes ago, Kopernikus said:

HTTP/2

I was not able to find a difference?!

 

46 minutes ago, Kopernikus said:

HSTS

With HSTS the (compatible) browser automatically overwrites "http" to "https" which the user types in to the address bar. So the user is not able to open your website through "http". A drawback could be, that if your SSL certificate does not work anymore, nobody is able to reach your website (until the TTL of HSTS expired).

 

47 minutes ago, Kopernikus said:

HSTS subdomain ---> on or off?

Same as HSTS, but this time for all subdomains of your domain, too.

 

48 minutes ago, Kopernikus said:

"pass auth to Host"

I would say it passes Basic Auth to the target container, so Nginx asks for the password and passes it to the target container, so if the target container has Basic Auth as well (with the same credentials), the user does not need to re-enter it.

 

49 minutes ago, Kopernikus said:

Block Common Exploits --> switched on for all my proxy host 

This adds these rules:

cat /etc/nginx/conf.d/include/block-exploits.conf
## Block SQL injections
set $block_sql_injections 0;

if ($query_string ~ "union.*select.*\(") {
        set $block_sql_injections 1;
}

if ($query_string ~ "union.*all.*select.*") {
        set $block_sql_injections 1;
}

if ($query_string ~ "concat.*\(") {
        set $block_sql_injections 1;
}

if ($block_sql_injections = 1) {
        return 403;
}

## Block file injections
set $block_file_injections 0;

if ($query_string ~ "[a-zA-Z0-9_]=http://") {
        set $block_file_injections 1;
}

if ($query_string ~ "[a-zA-Z0-9_]=(\.\.//?)+") {
        set $block_file_injections 1;
}

if ($query_string ~ "[a-zA-Z0-9_]=/([a-z0-9_.]//?)+") {
        set $block_file_injections 1;
}

if ($block_file_injections = 1) {
        return 403;
}

## Block common exploits
set $block_common_exploits 0;

if ($query_string ~ "(<|%3C).*script.*(>|%3E)") {
        set $block_common_exploits 1;
}

if ($query_string ~ "GLOBALS(=|\[|\%[0-9A-Z]{0,2})") {
        set $block_common_exploits 1;
}

if ($query_string ~ "_REQUEST(=|\[|\%[0-9A-Z]{0,2})") {
        set $block_common_exploits 1;
}

if ($query_string ~ "proc/self/environ") {
        set $block_common_exploits 1;
}

if ($query_string ~ "mosConfig_[a-zA-Z_]{1,21}(=|\%3D)") {
        set $block_common_exploits 1;
}

if ($query_string ~ "base64_(en|de)code\(.*\)") {
        set $block_common_exploits 1;
}

if ($block_common_exploits = 1) {
        return 403;
}

## Block spam
set $block_spam 0;

if ($query_string ~ "\b(ultram|unicauca|valium|viagra|vicodin|xanax|ypxaieo)\b") {
        set $block_spam 1;
}

if ($query_string ~ "\b(erections|hoodia|huronriveracres|impotence|levitra|libido)\b") {
        set $block_spam 1;
}

if ($query_string ~ "\b(ambien|blue\spill|cialis|cocaine|ejaculation|erectile)\b") {
        set $block_spam 1;
}

if ($query_string ~ "\b(lipitor|phentermin|pro[sz]ac|sandyauer|tramadol|troyhamby)\b") {
        set $block_spam 1;
}

if ($block_spam = 1) {
        return 403;
}

## Block user agents
set $block_user_agents 0;

# Disable Akeeba Remote Control 2.5 and earlier
if ($http_user_agent ~ "Indy Library") {
        set $block_user_agents 1;
}

# Common bandwidth hoggers and hacking tools.
if ($http_user_agent ~ "libwww-perl") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "GetRight") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "GetWeb!") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "Go!Zilla") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "Download Demon") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "Go-Ahead-Got-It") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "TurnitinBot") {
        set $block_user_agents 1;
}

if ($http_user_agent ~ "GrabNet") {
        set $block_user_agents 1;
}

if ($block_user_agents = 1) {
        return 403;
}

 

18 hours ago, mgutt said:

And now you open yourdomain.com or yourdomain.com/vnc.html?

 

 

 

I open youdomain.com and it forwards to yourdomain.com/vnc.html

17 minutes ago, Kopernikus said:

I open youdomain.com and it forwards to yourdomain.com/vnc.html

And you are sure you needed a custom location for this? A location isn't usually a redirect. It only means that /vnc.html should open a different target than the general rule. This means you could add the location /bla.html and let it show the content of /vnc.html.

On 9/8/2021 at 9:48 AM, mgutt said:

Ok, I found the bug and updated the container template. Please uninstall NPM and delete the NPM files through the Appdata Cleanup Plugin. You can re-install NPM in ~20 minutes (CA is only updated every 2 hours).

Is this true for everyone? or only @Kopernikus?

18 hours ago, Kewjoe said:

Is this true for everyone?

As long you don't have the errors in the logs, you don't need to change anything. 

Hello , I am having this issue after install. Is there anything that i have done wrong in my setting? or is it due to files or folder left behind when i did uninstall previously? 

 

I am missing "include" folder during installation as well . (as shown in my attachment)

5 hours ago, spacezmonkey said:

or is it due to files or folder left behind when i did uninstall previously? 

Maybe. Do a simple test. Change the name of your installed container. Then go to the apps and install it a second time, but this time you change all three paths, so the second installation uses different folders. Example:

Hello Sir,

 

I am getting the same error with a new folder. i have added "-1" to all the 3 link. Is it something to do with my wrong configuration at port forwarding?

 

10 minutes ago, mgutt said:

Maybe. Do a simple test. Change the name of your installed container. Then go to the apps and install it a second time, but this time you change all three paths, so the second installation uses different folders. Example:

10 minutes ago, mgutt said:

 

 

Hmm. Strange. I did the same and it was installed successfully. 🤔

 

8 hours ago, spacezmonkey said:

I am missing "include" folder during installation as well . (as shown in my attachment)

 

Found a mistake in your checks. You used Unraid's webterminal to find the include folder. But you need to use the console of the container:

 

 

Then check the content of the file with the following command:

cat /etc/nginx/conf.d/include/ip_ranges.conf

 

For me it's:

set_real_ip_from 120.52.22.96/27;

set_real_ip_from 205.251.249.0/24;

set_real_ip_from 180.163.57.128/26;

set_real_ip_from 204.246.168.0/22;

set_real_ip_from 205.251.252.0/23;

set_real_ip_from 54.192.0.0/16;

set_real_ip_from 204.246.173.0/24;

set_real_ip_from 54.230.200.0/21;

set_real_ip_from 120.253.240.192/26;

set_real_ip_from 116.129.226.128/26;

set_real_ip_from 130.176.0.0/17;

set_real_ip_from 108.156.0.0/14;

set_real_ip_from 99.86.0.0/16;

set_real_ip_from 205.251.200.0/21;

set_real_ip_from 223.71.71.128/25;

set_real_ip_from 13.32.0.0/15;

set_real_ip_from 120.253.245.128/26;

set_real_ip_from 13.224.0.0/14;

set_real_ip_from 70.132.0.0/18;

set_real_ip_from 15.158.0.0/16;

set_real_ip_from 13.249.0.0/16;

set_real_ip_from 205.251.208.0/20;

set_real_ip_from 65.9.128.0/18;

set_real_ip_from 130.176.128.0/18;

set_real_ip_from 58.254.138.0/25;

set_real_ip_from 54.230.208.0/20;

set_real_ip_from 116.129.226.0/25;

set_real_ip_from 52.222.128.0/17;

set_real_ip_from 64.252.128.0/18;

set_real_ip_from 205.251.254.0/24;

set_real_ip_from 54.230.224.0/19;

set_real_ip_from 71.152.0.0/17;

set_real_ip_from 216.137.32.0/19;

set_real_ip_from 204.246.172.0/24;

set_real_ip_from 120.52.39.128/27;

set_real_ip_from 118.193.97.64/26;

set_real_ip_from 223.71.71.96/27;

set_real_ip_from 54.240.128.0/18;

set_real_ip_from 205.251.250.0/23;

set_real_ip_from 180.163.57.0/25;

set_real_ip_from 52.46.0.0/18;

set_real_ip_from 223.71.11.0/27;

set_real_ip_from 52.82.128.0/19;

set_real_ip_from 54.230.0.0/17;

set_real_ip_from 54.230.128.0/18;

set_real_ip_from 54.239.128.0/18;

set_real_ip_from 130.176.224.0/20;

set_real_ip_from 36.103.232.128/26;

set_real_ip_from 52.84.0.0/15;

set_real_ip_from 143.204.0.0/16;

set_real_ip_from 144.220.0.0/16;

set_real_ip_from 120.52.153.192/26;

set_real_ip_from 119.147.182.0/25;

set_real_ip_from 120.232.236.0/25;

set_real_ip_from 54.182.0.0/16;

set_real_ip_from 58.254.138.128/26;

set_real_ip_from 120.253.245.192/27;

set_real_ip_from 54.239.192.0/19;

set_real_ip_from 18.64.0.0/14;

set_real_ip_from 120.52.12.64/26;

set_real_ip_from 99.84.0.0/16;

set_real_ip_from 130.176.192.0/19;

set_real_ip_from 52.124.128.0/17;

set_real_ip_from 204.246.164.0/22;

set_real_ip_from 13.35.0.0/16;

set_real_ip_from 204.246.174.0/23;

set_real_ip_from 36.103.232.0/25;

set_real_ip_from 119.147.182.128/26;

set_real_ip_from 118.193.97.128/25;

set_real_ip_from 120.232.236.128/26;

set_real_ip_from 204.246.176.0/20;

set_real_ip_from 65.8.0.0/16;

set_real_ip_from 65.9.0.0/17;

set_real_ip_from 108.138.0.0/15;

set_real_ip_from 120.253.241.160/27;

set_real_ip_from 64.252.64.0/18;

set_real_ip_from 13.113.196.64/26;

set_real_ip_from 13.113.203.0/24;

set_real_ip_from 52.199.127.192/26;

set_real_ip_from 13.124.199.0/24;

set_real_ip_from 3.35.130.128/25;

set_real_ip_from 52.78.247.128/26;

set_real_ip_from 13.233.177.192/26;

set_real_ip_from 15.207.13.128/25;

set_real_ip_from 15.207.213.128/25;

set_real_ip_from 52.66.194.128/26;

set_real_ip_from 13.228.69.0/24;

set_real_ip_from 52.220.191.0/26;

set_real_ip_from 13.210.67.128/26;

set_real_ip_from 13.54.63.128/26;

set_real_ip_from 99.79.169.0/24;

set_real_ip_from 18.192.142.0/23;

set_real_ip_from 35.158.136.0/24;

set_real_ip_from 52.57.254.0/24;

set_real_ip_from 13.48.32.0/24;

set_real_ip_from 18.200.212.0/23;

set_real_ip_from 52.212.248.0/26;

set_real_ip_from 3.10.17.128/25;

set_real_ip_from 3.11.53.0/24;

set_real_ip_from 52.56.127.0/25;

set_real_ip_from 15.188.184.0/24;

set_real_ip_from 52.47.139.0/24;

set_real_ip_from 18.229.220.192/26;

set_real_ip_from 54.233.255.128/26;

set_real_ip_from 3.231.2.0/25;

set_real_ip_from 3.234.232.224/27;

set_real_ip_from 3.236.169.192/26;

set_real_ip_from 3.236.48.0/23;

set_real_ip_from 34.195.252.0/24;

set_real_ip_from 34.226.14.0/24;

set_real_ip_from 13.59.250.0/26;

set_real_ip_from 18.216.170.128/25;

set_real_ip_from 3.128.93.0/24;

set_real_ip_from 3.134.215.0/24;

set_real_ip_from 52.15.127.128/26;

set_real_ip_from 3.101.158.0/23;

set_real_ip_from 52.52.191.128/26;

set_real_ip_from 34.216.51.0/25;

set_real_ip_from 34.223.12.224/27;

set_real_ip_from 34.223.80.192/26;

set_real_ip_from 35.162.63.192/26;

set_real_ip_from 35.167.191.128/26;

set_real_ip_from 44.227.178.0/24;

set_real_ip_from 44.234.108.128/25;

set_real_ip_from 44.234.90.252/30;

set_real_ip_from 2600:9000:3000::/36;

set_real_ip_from 2600:9000:ddd::/48;

set_real_ip_from 2600:9000:5300::/40;

set_real_ip_from 2600:9000:1000::/36;

set_real_ip_from 2600:9000:2000::/36;

set_real_ip_from 2400:7fc0:500::/40;

set_real_ip_from 2600:9000:4000::/36;

set_real_ip_from 2600:9000:fff::/48;

set_real_ip_from 2404:c2c0:500::/40;

set_real_ip_from 2600:9000:f000::/36;

set_real_ip_from 2600:9000:eee::/48;

set_real_ip_from 173.245.48.0/20;

set_real_ip_from 103.21.244.0/22;

set_real_ip_from 103.22.200.0/22;

set_real_ip_from 103.31.4.0/22;

set_real_ip_from 141.101.64.0/18;

set_real_ip_from 108.162.192.0/18;

set_real_ip_from 190.93.240.0/20;

set_real_ip_from 188.114.96.0/20;

set_real_ip_from 197.234.240.0/22;

set_real_ip_from 198.41.128.0/17;

set_real_ip_from 162.158.0.0/15;

set_real_ip_from 104.16.0.0/13;

set_real_ip_from 104.24.0.0/14;

set_real_ip_from 172.64.0.0/13;

set_real_ip_from 131.0.72.0/22;

set_real_ip_from 2400:cb00::/32;

set_real_ip_from 2606:4700::/32;

set_real_ip_from 2803:f800::/32;

set_real_ip_from 2405:b500::/32;

set_real_ip_from 2405:8100::/32;

set_real_ip_from 2a06:98c0::/29;

set_real_ip_from 2c0f:f248::/32

 

Hello, this docker has been working fine for the last months, but since i updated it today it has now crashed, and i get this message when trying to create it again..

Error response from daemon: conflicting options: port publishing and the container type network mode

 

I am running it through a VPN Docker, and this has been working fine before, but from today it won't anymore.. 

There are no ports in the config, they are in the VPN docker, as they should.

 

Please help  

Edited September 13, 20214 yr by DjJoakim

Thank you very much for helping me..i found my ip_ranges.conf file...but when i perform cat /etc/nginx/conf.d/includ/ip_ranges.conf

 

it show a list if ip address until a point , it changes to text.. 

 

i am able to log into webui for setup, but i am unable save the setting. It show "internal error" and status is not shown "online".

 

 

 

 

 

 

2 hours ago, mgutt said:

 

Then check the content of the file with the following command:

cat /etc/nginx/conf.d/include/ip_ranges.conf

 

 

 

 

59 minutes ago, spacezmonkey said:

 

Ok, you found a Bug in the NPM. This HTML code should not be part of this file.

 

As long this bug is present, please execute this, to remove the HTML code:

 sed -i '/DOCTYPE/Q' /etc/nginx/conf.d/include/ip_ranges.conf

 

Please verify with "cat" if it worked.

2 hours ago, DjJoakim said:

Error response from daemon: conflicting options: port publishing and the container type network mode

This usually means that NPM's ports are used by different container. Check if other containers use the same IP-address and on which ports they listen. NPM needs 80, 81, 443 and 3000.

Hello ,

 

it works....😀 and setting are saving now... and status changed to online...

 

however, when i restart the docker container, the html code reappear and i have re execute below code. Is there a way to make it permanent? 

 

Anyway i am very happy that docker container is working well now.. 😄

 

6 minutes ago, mgutt said:

Ok, you found a Bug in the NPM container. This HTML code should not be part of this file.

 

As long this bug is present, please execute this, to remove the HTML code:

 sed -i '/DOCTYPE/Q' /etc/nginx/conf.d/include/ip_ranges.conf

 

Please verify with "cat" if it worked.

 

 

22 minutes ago, spacezmonkey said:

however, when i restart the docker container, the html code reappear and i have re execute below code. Is there a way to make it permanent? 

That happens, because NPM talks to an online API to get the recent list of this IP addresses. As you can see here, it tries to access three different URLs:

https://github.com/jc21/nginx-proxy-manager/blob/b39a59ce72eb032d5b725dce90dd6f3cf08b7d29/backend/internal/ip_ranges.js

 

And this is done every 6 hours, so it will happen again even if you don't restart the container😒

 

Maybe you should try to open all three URLs through your PC and solve the captcha (if it hopefully will be shown) to "unlock" your public ip address for accessing them:

https://ip-ranges.amazonaws.com/ip-ranges.json
https://www.cloudflare.com/ips-v4
https://www.cloudflare.com/ips-v6

 

Or try to lock the file with the following command:

su
chattr +i /etc/nginx/conf.d/include/ip_ranges.conf

 

A file with the "i" flag can't be modified or deleted.

 

Optional: If you need to make it editable again:

chattr -i /etc/nginx/conf.d/include/ip_ranges.conf

 

 

40 minutes ago, mgutt said:

This usually means that NPM's ports are used by different container. Check if other containers use the same IP-address and on which ports they listen. NPM needs 80, 81, 443 and 3000.

 

Yeah no other docker uses this ports.. i have the ports lined up in the vpn docker since it's "running through" the docker, and then i remove the ports from the nginx docker, but since the update today i get this error message..

 

When using the command "--net=container:openvpnpublic" it works, but if i change it to "custom container:openvpnpublic" network, i get this error message.. 

Edited September 13, 20214 yr by DjJoakim