Hawkins12 Posted September 6 Share Posted September 6 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). Quote Link to comment
mattie112 Posted September 6 Share Posted September 6 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. Quote Link to comment
Hawkins12 Posted September 6 Share Posted September 6 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: Quote Link to comment
Hawkins12 Posted September 6 Share Posted September 6 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: Quote Link to comment
mattie112 Posted September 7 Share Posted September 7 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. Quote Link to comment
Braulio Dias Ribeiro Posted September 12 Share Posted September 12 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”. Quote Link to comment
rbrowning85 Posted Tuesday at 03:04 AM Share Posted Tuesday at 03:04 AM I have my Cloudflare Tunnel pointed to NPM and a wildcard cert setup. However, when I enable Force SSL, I get an error stating "too many redirects." Any idea why I am getting this error? NPM perfectly redirects my app.example.com to the correct docker container with this turned off. I just don't understand what is a causing the error. Quote Link to comment
Braulio Dias Ribeiro Posted Tuesday at 03:33 PM Share Posted Tuesday at 03:33 PM 12 hours ago, rbrowning85 said: I have my Cloudflare Tunnel pointed to NPM and a wildcard cert setup. However, when I enable Force SSL, I get an error stating "too many redirects." Any idea why I am getting this error? NPM perfectly redirects my app.example.com to the correct docker container with this turned off. I just don't understand what is a causing the error. I didn't point my cloudflare directly at NPM..... I pointed my router to the AdGuard IP. AdGuard points to NPM. NPM points to the domains. Quote Link to comment
rbrowning85 Posted Tuesday at 04:36 PM Share Posted Tuesday at 04:36 PM 1 hour ago, Braulio Dias Ribeiro said: I didn't point my cloudflare directly at NPM..... I pointed my router to the AdGuard IP. AdGuard points to NPM. NPM points to the domains. Interesting. So you are pointing your Cloudflare Tunnel to your router's IP address? Then using an Adguard DNS rewrite, you are then forwarding that to NPM, which then proxies it to the correct docker container? app.example.com --> Cloudflare Tunnel --> home router --> AdGuard DNS rewrite --> NPM --> docker container Does this require you to open ports 80 and 443 on your router? Quote Link to comment
Braulio Dias Ribeiro Posted Tuesday at 05:07 PM Share Posted Tuesday at 05:07 PM (edited) 32 minutes ago, rbrowning85 said: Interesting. So you are pointing your Cloudflare Tunnel to your router's IP address? Then using an Adguard DNS rewrite, you are then forwarding that to NPM, which then proxies it to the correct docker container? app.example.com --> Cloudflare Tunnel --> home router --> AdGuard DNS rewrite --> NPM --> docker container Does this require you to open ports 80 and 443 on your router? My redirect sub domains are internal...... Some are external Cloudflare Tunnel Site --> Cloudflare Tunnel Docker Unraid Router --> AdGuard DNS rewrite --> NPM --> docker container Edited Tuesday at 05:11 PM by Braulio Dias Ribeiro Quote Link to comment
Recommended Posts
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.