coltonc18 Posted February 14 Share Posted February 14 31 minutes ago, coltonc18 said: Good morning, I'm not sure what has happened....everything was working fine, but now all of a sudden, I'm getting 522 timeout errors. Everything was working, but now none of my proxies work. I have 11 setup and none work anymore. I've got nothing in the logs either. figured it out...damn Brightspeed changed my IP address, but not sure how to automatically detect that with cloudflare like I did with duckdns Quote Link to comment
Kilrah Posted February 14 Share Posted February 14 There are cloudflare ddns updater containers in Apps. Quote Link to comment
coltonc18 Posted February 14 Share Posted February 14 5 minutes ago, Kilrah said: There are cloudflare ddns updater containers in Apps. I'll look for one when I get home. Quote Link to comment
flosken Posted February 15 Share Posted February 15 17 hours ago, coltonc18 said: I'll look for one when I get home. I guess most routers have the option as well. I update my IP from OPNsense. Quote Link to comment
coltonc18 Posted February 16 Share Posted February 16 (edited) On 2/15/2024 at 5:45 AM, flosken said: I guess most routers have the option as well. I update my IP from OPNsense. I've got a containter setup for it now...I guess when I switched from duckdns to cloudflare I just never set it up, and forgot about that piece. Edited February 16 by coltonc18 Quote Link to comment
crusemm Posted March 2 Share Posted March 2 (edited) Server Error 502 Bad Gateway for Nextcloud Running Nextcloud and NGINX Proxy Manager on UnRaid. When attempting to access Nextcloud through reverse proxy, I get a 502 Bad Gateway error. Previously I had Nextcloud setup behind a reverse proxy administered by SWAG. After a server issue in which I had to delete and rebuild my docker image file, I was unable to get SWAG working. SWAG docker is still installed on the Unraid server but is not running. I have since setup NPM to handle the reverse proxy duties. I have my own domain administered by Gandi.net; and I am using Duckdns. I have NPM running successfully with Overseer and Bitwarden (Vaultwarden) dockers and BlueIris running in a Windows VM. I went through the steps in this post 1.) Does the NPM container work? Yes 2.) Is NPM online? "http://XX.XX.XX.XX". Results in the following: HTTPS gets: 3.) Does your target container work? https://192.168.1.220:8666/apps/dashboard/#/ However, http://192.168.1.220:8666 results in 4.) Does NPM reach your target container? However, using HTTPS All the dockers are running on the “Bridge” network. 5.) Another reason could be that you selected the wrong scheme. For example, you used "http", but your target container only supports incoming connections through the scheme "https". I have tried both http and https. I have tried with and without HSTS. 6.) Or you used the wrong ports. So double check your proxy host settings! I have checked the ports multiple times. A weird, maybe related, side note: I cannot enter http://nextcloud.xxxxxxx.xxx , it always gets changed to https://nextcloud.xxxxxxx.xxx Edited March 2 by crusemm additional information Quote Link to comment
Kilrah Posted March 2 Share Posted March 2 (edited) You need to use both the http port of the NC container and the http forwarding scheme. Seems you're using the https container port. Edited March 2 by Kilrah Quote Link to comment
crusemm Posted March 2 Share Posted March 2 6 hours ago, Kilrah said: You need to use both the http port of the NC container and the http forwarding scheme. Seems you're using the https container port. So how do I set that up? where is it and what changes do I need to make? Is it a NC setting, or something in NPM? Quote Link to comment
crusemm Posted March 2 Share Posted March 2 4 minutes ago, Kilrah said: All in NPM normally. Are you talking about this? or is there another place to make the change? Quote Link to comment
Kilrah Posted March 2 Share Posted March 2 That's it, but the whole point is to use the correct port. I don't know what your port maps for nextcloud are / whether 8666 is the correct http one and not https. Quote Link to comment
crusemm Posted March 2 Share Posted March 2 (edited) 5 minutes ago, Kilrah said: That's it, but the whole point is to use the correct port. I don't know what your port maps for nextcloud are / whether 8666 is the correct http one and not https. From the nextcloud docker From the NPM docker settings from the router Port Forwarding Edited March 2 by crusemm add information Quote Link to comment
Kilrah Posted March 2 Share Posted March 2 That maps to 443 so it is the https port. Quote Link to comment
crusemm Posted March 2 Share Posted March 2 8 hours ago, Kilrah said: That maps to 443 so it is the https port. So how do I get NPM to send the https://nextcloud.mydomain.com to my NC docker? Or how do I get my NC to allow the http to connect through? Quote Link to comment
Kilrah Posted March 3 Share Posted March 3 You've never shown the full template or mentioned which of the NC containers in CA you used, so maybe start with that. Quote Link to comment
jarkle Posted March 10 Share Posted March 10 Started seeing this on my container logs. Any ideas?: [3/9/2024] [8:51:02 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-7' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = E8ixmXcgsMcPrghtqaEzqD dns_godaddy_key = dKszgmKm6V5H_5UdqHPfw85JAEcekAwYmeV' > '/etc/letsencrypt/credentials/credentials-7' && chmod 600 '/etc/letsencrypt/credentials/credentials-7'; } [3/9/2024] [8:51:02 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-8' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = 8joRh5JhKckugx3Rj1SjBS dns_godaddy_key = dKszgmKm6V5H_S3kkuLzm23myxdecRv45V3' > '/etc/letsencrypt/credentials/credentials-8' && chmod 600 '/etc/letsencrypt/credentials/credentials-8'; } [3/9/2024] [8:51:02 PM] [Certbot ] › ▶ start Installing godaddy... [3/9/2024] [8:51:02 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-godaddy==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate [3/9/2024] [8:51:11 PM] [Certbot ] › ✖ error ERROR: Could not find a version that satisfies the requirement certbot-dns-godaddy==2.9.0 (from versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 2.6.0, 2.7.4, 2.8.0) ERROR: No matching distribution found for certbot-dns-godaddy==2.9.0 [3/9/2024] [8:51:11 PM] [Global ] › ✖ error Some plugins failed to install. Please check the logs above [3/9/2024] [8:51:12 PM] [Migrate ] › ℹ info Current database version: none [3/9/2024] [8:51:12 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-7' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = E8ixmXcgsMcPrghtqaEzqD dns_godaddy_key = dKszgmKm6V5H_5UdqHPfw85JAEcekAwYmeV' > '/etc/letsencrypt/credentials/credentials-7' && chmod 600 '/etc/letsencrypt/credentials/credentials-7'; } [3/9/2024] [8:51:12 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-8' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = 8joRh5JhKckugx3Rj1SjBS dns_godaddy_key = dKszgmKm6V5H_S3kkuLzm23myxdecRv45V3' > '/etc/letsencrypt/credentials/credentials-8' && chmod 600 '/etc/letsencrypt/credentials/credentials-8'; } [3/9/2024] [8:51:12 PM] [Certbot ] › ▶ start Installing godaddy... [3/9/2024] [8:51:12 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-godaddy==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate [3/9/2024] [8:51:21 PM] [Certbot ] › ✖ error ERROR: Could not find a version that satisfies the requirement certbot-dns-godaddy==2.9.0 (from versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 2.6.0, 2.7.4, 2.8.0) ERROR: No matching distribution found for certbot-dns-godaddy==2.9.0 [3/9/2024] [8:51:21 PM] [Global ] › ✖ error Some plugins failed to install. Please check the logs above [3/9/2024] [8:51:22 PM] [Migrate ] › ℹ info Current database version: none [3/9/2024] [8:51:22 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-7' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = E8ixmXcgsMcPrghtqaEzqD dns_godaddy_key = dKszgmKm6V5H_5UdqHPfw85JAEcekAwYmeV' > '/etc/letsencrypt/credentials/credentials-7' && chmod 600 '/etc/letsencrypt/credentials/credentials-7'; } [3/9/2024] [8:51:22 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-8' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = 8joRh5JhKckugx3Rj1SjBS dns_godaddy_key = dKszgmKm6V5H_S3kkuLzm23myxdecRv45V3' > '/etc/letsencrypt/credentials/credentials-8' && chmod 600 '/etc/letsencrypt/credentials/credentials-8'; } [3/9/2024] [8:51:22 PM] [Certbot ] › ▶ start Installing godaddy... [3/9/2024] [8:51:22 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-godaddy==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate I also am no longer able to login to the web UI.. Container: jc21/nginx-proxy-manager Quote Link to comment
crusemm Posted March 10 Share Posted March 10 I solved my Nextcloud issue. I had the wrong Ip address and port. I was using the Unraid IP and the NC port, when I needed to use the IP and port 443. Quote Link to comment
phyte22 Posted March 12 Share Posted March 12 Hi, if I have understood correctly, the GeoIP2 module is now supported with the latest release of NPM. I have seen a small config example here github issue. Unfortunately, I didn't quite understand how and where I have to enter my whitelisted countries. has anyone here already got the module to run successfully or can help me? Thank you! Quote Link to comment
jarkle Posted March 13 Share Posted March 13 (edited) On 3/9/2024 at 8:54 PM, jarkle said: Started seeing this on my container logs. Any ideas?: [3/9/2024] [8:51:02 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-7' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = E8ixmXcgsMcPrghtqaEzqD dns_godaddy_key = dKszgmKm6V5H_5UdqHPfw85JAEcekAwYmeV' > '/etc/letsencrypt/credentials/credentials-7' && chmod 600 '/etc/letsencrypt/credentials/credentials-7'; } [3/9/2024] [8:51:02 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-8' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = 8joRh5JhKckugx3Rj1SjBS dns_godaddy_key = dKszgmKm6V5H_S3kkuLzm23myxdecRv45V3' > '/etc/letsencrypt/credentials/credentials-8' && chmod 600 '/etc/letsencrypt/credentials/credentials-8'; } [3/9/2024] [8:51:02 PM] [Certbot ] › ▶ start Installing godaddy... [3/9/2024] [8:51:02 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-godaddy==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate [3/9/2024] [8:51:11 PM] [Certbot ] › ✖ error ERROR: Could not find a version that satisfies the requirement certbot-dns-godaddy==2.9.0 (from versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 2.6.0, 2.7.4, 2.8.0) ERROR: No matching distribution found for certbot-dns-godaddy==2.9.0 [3/9/2024] [8:51:11 PM] [Global ] › ✖ error Some plugins failed to install. Please check the logs above [3/9/2024] [8:51:12 PM] [Migrate ] › ℹ info Current database version: none [3/9/2024] [8:51:12 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-7' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = E8ixmXcgsMcPrghtqaEzqD dns_godaddy_key = dKszgmKm6V5H_5UdqHPfw85JAEcekAwYmeV' > '/etc/letsencrypt/credentials/credentials-7' && chmod 600 '/etc/letsencrypt/credentials/credentials-7'; } [3/9/2024] [8:51:12 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-8' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = 8joRh5JhKckugx3Rj1SjBS dns_godaddy_key = dKszgmKm6V5H_S3kkuLzm23myxdecRv45V3' > '/etc/letsencrypt/credentials/credentials-8' && chmod 600 '/etc/letsencrypt/credentials/credentials-8'; } [3/9/2024] [8:51:12 PM] [Certbot ] › ▶ start Installing godaddy... [3/9/2024] [8:51:12 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-godaddy==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate [3/9/2024] [8:51:21 PM] [Certbot ] › ✖ error ERROR: Could not find a version that satisfies the requirement certbot-dns-godaddy==2.9.0 (from versions: 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 2.6.0, 2.7.4, 2.8.0) ERROR: No matching distribution found for certbot-dns-godaddy==2.9.0 [3/9/2024] [8:51:21 PM] [Global ] › ✖ error Some plugins failed to install. Please check the logs above [3/9/2024] [8:51:22 PM] [Migrate ] › ℹ info Current database version: none [3/9/2024] [8:51:22 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-7' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = E8ixmXcgsMcPrghtqaEzqD dns_godaddy_key = dKszgmKm6V5H_5UdqHPfw85JAEcekAwYmeV' > '/etc/letsencrypt/credentials/credentials-7' && chmod 600 '/etc/letsencrypt/credentials/credentials-7'; } [3/9/2024] [8:51:22 PM] [Global ] › ⬤ debug CMD: [ -f '/etc/letsencrypt/credentials/credentials-8' ] || { mkdir -p /etc/letsencrypt/credentials 2> /dev/null; echo 'dns_godaddy_secret = 8joRh5JhKckugx3Rj1SjBS dns_godaddy_key = dKszgmKm6V5H_S3kkuLzm23myxdecRv45V3' > '/etc/letsencrypt/credentials/credentials-8' && chmod 600 '/etc/letsencrypt/credentials/credentials-8'; } [3/9/2024] [8:51:22 PM] [Certbot ] › ▶ start Installing godaddy... [3/9/2024] [8:51:22 PM] [Global ] › ⬤ debug CMD: . /opt/certbot/bin/activate && pip install --no-cache-dir certbot-dns-godaddy==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') && deactivate I also am no longer able to login to the web UI.. Container: jc21/nginx-proxy-manager Fixed it with this: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3592 Edited March 13 by jarkle Quote Link to comment
DevanteWeary Posted March 13 Share Posted March 13 Hey guys. I use NPM to direct to two different hosted sites access via completely different external domains. I use two separate NGINX containers - one for each site. I'm wondering if I can combine those into one container. Like instead of having /appdata/nginx/www/index.html for one site and /appdata/nginxphp8/www/index.html for the other site (two different container appdata folders). I want something like /appdata/nginx/www/site1/index.html /appdata/nginx/www/site2/index.html Is this possible using NPM? I see a Custom Location tab in Edit Proxy Host but not sure that does what I want it do to. I tried to enter the correct folder in the location but I have a feeling this isn't exactly what I think it is. Thanks for any info/advice! Quote Link to comment
Avenga Posted March 13 Share Posted March 13 Hi, aren't the certificates automatically renewed by NPM ? I got an e-mail from let´s encrypt: Quote Your certificate (or certificates) for the names listed below will expire in 19 days (on 2024-04-01). Please make sure to renew your certificate before then, or visitors to your web site will encounter errors. We recommend renewing certificates automatically when they have a third of their total lifetime left. For Let's Encrypt's current 90-day certificates, that means renewing 30 days before expiration Quote Link to comment
Kilrah Posted March 13 Share Posted March 13 They are unless there's an error, such as a domain you removed but kept the cerificate for. Quote Link to comment
Avenga Posted March 13 Share Posted March 13 I tried to manually renew: Quote Internal Error I'm running another Nginx as a web server on port 80/443 on a VM, with certbot. NPM (proxy) runs on port 40xxx - is that the reason ?? same domain for all Quote Link to comment
Mattti1912 Posted March 14 Share Posted March 14 Hello People:) I've installed nginx proxy manager on my unraid server.. The problem is that i now cant access my jellyfin from my local lan.. I've googled this error and some say that it could be a let's encrypt error?? Anyone who have an idea, on how to solve this?? Thank you. regards:) Quote Link to comment
JonathanM Posted March 14 Share Posted March 14 3 hours ago, Mattti1912 said: The problem is that i now cant access my jellyfin from my local lan.. That statement implies you can reach it from a WAN connection, which would mean a hairpin / loopback configuration error in your router. 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.