[Support] Djoss - Nginx Proxy Manager

[Hawkins12]

15 minutes ago, mattie112 said:

Can you chech the certificate view in NPM? Perhaps it did made one and you can just use it. Or chech the drop down where it says 'request new' 

So the dropdown shows:  Note that what I highlighted out was my attemp to manually add my Certs from Cloudflare to NPM. It does not related to my nextcloud proxy.

 

In my SSL Certs, I only have this manually added Cert from Cloudflare.  Note I only added this cert because of the issues I was having trying to get nextcloud to work here.  It didn't work prior to this (or after the fact).

[mattie112]

Ik strange. You could check in the docker container itself on the filesystem (or in the app data) and manually remove any files that are certificates for your host. Or if you have not a lot of config yet just clear and restart. 

[Hawkins12]

11 minutes ago, mattie112 said:

Ik strange. You could check in the docker container itself on the filesystem (or in the app data) and manually remove any files that are certificates for your host. Or if you have not a lot of config yet just clear and restart. 

I'll clear and restart.  My only other guess is I am not setting up the Proxy Host right.    NNote I have tried EVERY combination in port  (ie. I've tried http/https for 443, 444, 1443, etc).  Here is how I have it set up.  What do you think I should be using?

 

 

And my SWAG config file looks like this:

[Hawkins12]

33 minutes ago, mattie112 said:

Ik strange. You could check in the docker container itself on the filesystem (or in the app data) and manually remove any files that are certificates for your host. Or if you have not a lot of config yet just clear and restart. 

I might have more information.  I checked logs when trying to pull a certificate and got this:

"Timeout during connect (likely firewall problem)"

 

My NGINX is setup exactly the same as SWAG (and I know i did port forwarding for SWAG).  Here is my NGINX PM:

and note I also have this on the "Custom: Proxynet" network type as my SWAG is on that too.

 

Here is my SWAG:

[mattie112]

You could try two things. With your phone on 4G try to access both 80 and 443. Are both not working or just one of them? Just to make sure we are looking in the right direction. 

[Braulio Dias Ribeiro]

My docker network configuration is:
- Docker custom network type: ipvlan
- Host access to custom networks: Disabled

 I have this problem:
 
1) npm is configured on the "br0" network with a fixed ip (192.168.10.238). But I can't access the panel because when i try to do login , shows the error “Bad Gateway". All the other containers are on a single network (bdrtec), only npm is on “br0”.