ok the first problem.. i easaly cann access http://192.168.170.63:8080/ut3/1.jpg   but i cannot access it throug NPM via xx.xxx.de/ut3/1.jpg

 

nee SSL needed

15 hours ago, lsymfr said:

I have usernames and password set up, no IPs and yes I enabled satisfy any

Can you try to run "tail -f /mnt/user/appdata/NginxProxyManager/log/proxy_host-XX.log", on the log file for your proxy host?  Then access the site and see what is being logged.

16 minutes ago, Gee1 said:

ok the first problem.. i easaly cann access http://192.168.170.63:8080/ut3/1.jpg   but i cannot access it throug NPM via xx.xxx.de/ut3/1.jpg

 

nee SSL needed

Which error are you getting exactly ?  Are you accessing your site locally or remotely ?

16 minutes ago, Djoss said:

Which error are you getting exactly ?  Are you accessing your site locally or remotely ?

Which error are you getting exactly ? -> 502 Bad Gateway

Are you accessing your site locally or remotely ? localy it works, and remote over proxy it dosnt. (192.168.170.63 is a normal nginx webserver)

5 minutes ago, Gee1 said:

Which error are you getting exactly ? -> 502 Bad Gateway

Are you accessing your site locally or remotely ? localy it works, and remote over proxy it dosnt. (192.168.170.63 is a normal nginx webserver)

For some reason NPM is not able to access 170.63.  Is NPM using the default bridge network ?   What about 170.63 ?

33 minutes ago, Djoss said:

For some reason NPM is not able to access 170.63.  Is NPM using the default bridge network ?   What about 170.63 ?

NPM is 170.55    its on the same bridge / network  btw... NPM is Host (170.55) and 170.63 wehre the webserver is, is br0

 

and i have another problem: no matter what i try i cant change nginx port 8080 in unraid

Edited November 9, 20205 yr by Gee1

NPM is 170.55    its on the same bridge / network  btw... NPM is Host (170.55) and 170.63 wehre the webserver is, is br0
 
and i have another problem: no matter what i try i cant change nginx port 8080 in unraid

So if I understand correctly, the “Network Type” is not set to “Bridge”, but to “Custom : br0”? If this is the case, you are correct in saying that port 8080 can’t be changed. Container’s ports can be mapped to something else only with a “Bridge” network type.

You can try to login to the container (docker exec -ti NginxProxyManager sh) and see if you can ping your other container from there.

ok i will test it - cool it works But i dont understand it.. the only reason i use custom br is that i can assign my own ip

Edited November 14, 20205 yr by Gee1

has anyone been successful to edit the log_format?

I wanted to customize my logs for better readability.

I’ve read the nginx documentation and added some lines to the Advanced tab in the edit proxy host window.

 

 

while i’ve been able to write a log file to a custom location with the template called „proxy“, i haven’t been able to create a template called „main“.

 

The status indicator in the proxy hosts section in npm toggles from online to offline when i uncomment the log_format line.

Has anyone been able to create a logfile-template in the GUI or the CLI?

I'm having issues with nextcloud complaining about the x-frame-options not being set to SAMEORIGIN.

I've added the following line to the advanced settings for my proxy host config in nginx:

add_header X-Frame-Options  "SAMEORIGIN"  always;

But doesn't work. Found this topic, seen some mentions about the same issue but couldn't find any solution other than the above line?

What am i missing?

Fresh install of NPM and I tried to set up ssl on proxy and get the following errors.

 

Set up is as follows:

 

 I got SWAg setup and its says server ready at the bottom of log. 

 

 Thanks for any help you folks can offer.

4 hours ago, jowi said:

I'm having issues with nextcloud complaining about the x-frame-options not being set to SAMEORIGIN.

I've added the following line to the advanced settings for my proxy host config in nginx:

 

add_header X-Frame-Options  "SAMEORIGIN"  always;

 

But doesn't work. Found this topic, seen some mentions about the same issue but couldn't find any solution other than the above line?

What am i missing?

Found it; maybe others can be helped with this as well. Had to add the line

add_header X-Frame-Options "SAMEORIGIN";

to the "default" config file in /appdata/nextcloud/nginx/site-confs folder. So had nothing to do with nginx proxy manager as it seems

On 11/14/2020 at 10:50 AM, Dati said:

has anyone been successful to edit the log_format?

I wanted to customize my logs for better readability.

I’ve read the nginx documentation and added some lines to the Advanced tab in the edit proxy host window.

 

 

while i’ve been able to write a log file to a custom location with the template called „proxy“, i haven’t been able to create a template called „main“.

 

The status indicator in the proxy hosts section in npm toggles from online to offline when i uncomment the log_format line.

Has anyone been able to create a logfile-template in the GUI or the CLI?

The custom config you put there is inserted under the "server" context.  The "log_format" statement is not allowed to be defined there.

 

You could try to add "log_format" to /mnt/user/appdata/NginxProxyManager/nginx/http.conf.  However, I'm not sure if it will work well since the log format is already defined somewhere else.

3 hours ago, Korky said:

Fresh install of NPM and I tried to set up ssl on proxy and get the following errors.

 

Set up is as follows:

 

 I got SWAg setup and its says server ready at the bottom of log. 

 

 Thanks for any help you folks can offer.

Look at /mnt/user/appdata/NginxProxyManager/log/letsencrypt/letsencrypt.log for more details about the challenge failure.  Probably that NginxProxyManager is not reachable from the Internet ?

Is this still maintained ? 

 

Apparently I have some issues on the docker container I cannot make the servers to be accessible via https, once I enable the certificate all dies. if I set https off on the ssl side it works perfectly . 

 

Thanks. 

 

 

And what exactly "dies" ?

Has anyone been succesfull in adding Deluge (binhex-delugevpn) to NPM?

I have all dockers working except this one. It's setup the same as the others.

 

I get the following:

 

No Such Resource

No such child resource.

 

Adding the slashes / behind location and port gives me a blank page. But I can see on the tabname Deluge WebUI.

Edited November 17, 20205 yr by Ericsson
Screenshot

Hi,

 

can somebody help me with error, I can't open NginxProxyManager.

How can solve this?

 

Best regards

Mladen

5 hours ago, mattie112 said:

And what exactly "dies" ?

the subdomains, they work perfectly while ssl lets encrypt is off but once I put it on no more websites 

11 hours ago, AurelianRQ said:

the subdomains, they work perfectly while ssl lets encrypt is off but once I put it on no more websites 

Again: what exactly is the problem? "Dies" is not something we can help you with. What does work and what not? What HTTP status codes are displayed. What do the logs say?

 

12 hours ago, Rejserr said:

Hi,

 

can somebody help me with error, I can't open NginxProxyManager.

How can solve this?

 

Best regards

Mladen

Can you confirm your SSL settings? It seems it is trying to load a certificate that either does not exist on the filesystem or there is no permission. You can also check the filesystem yourself to make sure this file exists.

3 hours ago, mattie112 said:

Can you confirm your SSL settings? It seems it is trying to load a certificate that either does not exist on the filesystem or there is no permission. You can also check the filesystem yourself to make sure this file exists.

I was check, file is exists, but I can't access.

How solve this ?

Edited November 18, 20205 yr by Rejserr

You could try logging in with ssh as root and then access the file.

 

Or from the webinterface go to SSL Certificates and then renew it to see if that fixes the problem.

I log with ssh as root. find folder and access, now I see what is the problem.

It's missing one cert, npm-9/fullchain.pem like in error report.

 

How can I create new certificates ? Pls give me some directions for nobie 

If you go to yourip:8181/nginx/certificates you can 'renew' the certificate. This should generate a new one and store it to your disk. I'm not really sure if you can see what site "9" is so I guess the first one on that page? Or perhaps an error is already displayed there?

 

edit:

You can see it in the config files /mnt/user/appdata/NginxProxyManager/nginx/proxy_host and then look into (`cat`) the 9.conf file

Edited November 18, 20205 yr by mattie112

I can't open yourip:8181/nginx/certificates to renew 'certificate' . 

 

I found what is missing certificate, it for my unraid server.

So, is it some another way to create new?