June 18, 20206 yr 8 hours ago, alturismo said: just use the ip instead dockername as hostname, also the correct port, thats it. Is this all I need to do? My plex server is running on 192.168.0.9:32400. I have also added the custom server access url in plex. As far as I can tell, it's working okey now. When I first connect to https://plex.mydomain.com I get a warning that tells me that this application isn't hosted by plex, and I need to sign in again. This is fine. When I do this, everything works. Is there anything else I need to, or should configure before using this? And also in the spaceinvaderone video, he adds a custom network to his proxycontainers. I haven't done this with plex as it is on another server. Plex is just running in hostmode. Should I do something about that? Should I create a custom network profile on that server as well? Sorry for all the n00b questions. I am fairly new to this. server { listen 443 ssl; listen [::]:443 ssl; server_name plex.*; include /config/nginx/ssl.conf; client_max_body_size 0; proxy_redirect off; proxy_buffering off; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.0.9; set $upstream_port 32400; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier; proxy_set_header X-Plex-Device $http_x_plex_device; proxy_set_header X-Plex-Device-Name $http_x_plex_device_name; proxy_set_header X-Plex-Platform $http_x_plex_platform; proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version; proxy_set_header X-Plex-Product $http_x_plex_product; proxy_set_header X-Plex-Token $http_x_plex_token; proxy_set_header X-Plex-Version $http_x_plex_version; proxy_set_header X-Plex-Nocache $http_x_plex_nocache; proxy_set_header X-Plex-Provides $http_x_plex_provides; proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor; proxy_set_header X-Plex-Model $http_x_plex_model; } }
June 18, 20206 yr @TrondHjertager thats all, custom network is only when its on the same server locally so traffic is local only. and u also should be able to connect via plex.yourdomain.com which would be direct connected then.
June 19, 20206 yr I've been having an issue the last couple of weeks where LetsEncrypt stops responding around every 12-14 hours-ish. No errors in the the logs, nothing looks out of place. I haven't made changes to the container in over a year with the exception of updates. A simple restart of the container and all is back to normal for another 14 hours. Any tips on where to start looking?
June 21, 20206 yr On 6/19/2020 at 11:06 AM, SeveredDime said: I've been having an issue the last couple of weeks where LetsEncrypt stops responding around every 12-14 hours-ish. No errors in the the logs, nothing looks out of place. I haven't made changes to the container in over a year with the exception of updates. A simple restart of the container and all is back to normal for another 14 hours. Any tips on where to start looking? I'm having the same issue. I've been trying to figure it out but it's getting annoying.
June 22, 20206 yr On 6/21/2020 at 7:28 AM, Jerky_san said: I'm having the same issue. I've been trying to figure it out but it's getting annoying. At least I'm not alone in this. Anyone able to provide some insight?
June 22, 20206 yr 3 minutes ago, SeveredDime said: At least I'm not alone in this. Anyone able to provide some insight? Happened to me again this morning.. something seems to happen around 2 am CST
June 22, 20206 yr 3 hours ago, Jerky_san said: Happened to me again this morning.. something seems to happen around 2 am CST I completely forgot I had an Uptime Robot pointed at my domain. It goes down around 2/2:30 am every day. 2:34 am 2:23 am 2:23 am 2:23 am 2:17 am 2:15 am 2:21 am
June 23, 20206 yr I'm also having the same issue, there's nothing in the logs to suggest why, i've just set up an uptime robot also to see when it goes down also
June 23, 20206 yr The Cron job to renew the certs are run at 02:08, so check if there are any errors for certbot. Might be that you guys have a network issue and something in the process is locked up.
June 23, 20206 yr Hi, I'm hoping I can get some assistance. I'm following spaceinvaders instructions on How to Setup and Configure a Reverse Proxy on unRAID with LetsEncrypt & NGINX. The problem I'm having is with letsencrypt. It keeps coming up with Performing the following challenges: http-01 challenge for okavangonextcloud.duckdns.org http-01 challenge for okavangoserver.duckdns.org Waiting for verification... Challenge failed for domain okavangonextcloud.duckdns.org Challenge failed for domain okavangoserver.duckdns.org I'm pretty sure it's my something to do with my port forwarding. Problem is I don't know what. Is there anyone here familiar with a linksys router? I can't quite figure out how to forward port 80 to 180 and 443 to 1443. I tried a few diff things but none seem to work.
June 23, 20206 yr 5 hours ago, saarg said: The Cron job to renew the certs are run at 02:08, so check if there are any errors for certbot. Might be that you guys have a network issue and something in the process is locked up. o-o welp that helped.. was trying to renew my domain that is behind cloudflare so it was failing.. Danke Danke Edited June 23, 20206 yr by Jerky_san
June 23, 20206 yr 1 hour ago, DigitalDivide said: Hi, I'm hoping I can get some assistance. I'm following spaceinvaders instructions on How to Setup and Configure a Reverse Proxy on unRAID with LetsEncrypt & NGINX. The problem I'm having is with letsencrypt. It keeps coming up with Performing the following challenges: http-01 challenge for okavangonextcloud.duckdns.org http-01 challenge for okavangoserver.duckdns.org Waiting for verification... Challenge failed for domain okavangonextcloud.duckdns.org Challenge failed for domain okavangoserver.duckdns.org I'm pretty sure it's my something to do with my port forwarding. Problem is I don't know what. Is there anyone here familiar with a linksys router? I can't quite figure out how to forward port 80 to 180 and 443 to 1443. I tried a few diff things but none seem to work. Use 80 and 443 as external and 180 and 1443 as internal. Then use the IP of unraid. Of course you have to add two entries. Is your subdomain of duckdns okavangonextcloud and okavangoserver or just okavango?
June 23, 20206 yr Hmmm at duckdns I have created the following okavangonextcloud pointing to my wan IP okavangoserver point to my wan ip
June 23, 20206 yr Didn't work, Waiting for verification... Challenge failed for domain okavangonextcloud.duckdns.org Challenge failed for domain okavangoserver.duckdns.org http-01 challenge for okavangonextcloud.duckdns.org http-01 challenge for okavangoserver.duckdns.org Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: okavangonextcloud.duckdns.org Type: connection Detail: Fetching http://okavangonextcloud.duckdns.org/.well-known/acme-challenge/aujXkgpsq114zWvcYW3AjEYCbqpoExXkV1GKpqFxawk: Timeout during connect (likely firewall problem) Domain: okavangoserver.duckdns.org Type: connection Detail: Fetching http://okavangoserver.duckdns.org/.well-known/acme-challenge/7omhOmbExgOh2o8fh7snrX6uzBcILok1p-kP6AEDk_8: Timeout during connect (likely firewall problem)
June 23, 20206 yr If I go to http://okavangoserver.duckdns.org it goes to my webgui login of my modem.
June 23, 20206 yr 55 minutes ago, DigitalDivide said: If I go to http://okavangoserver.duckdns.org it goes to my webgui login of my modem. Then your port 80 is blocked and you can't use http verification. Try using DNS.
June 23, 20206 yr 3 hours ago, DigitalDivide said: Not sure how to use dns...any guidance? There is info in the readme on github.
June 24, 20206 yr Actually I figured it out. I had to login to my modem and do a forward on port 80 and 443 to my router. Then I did as you suggested for the external and internal port forward. That did the trick
June 24, 20206 yr So I checked again this morning. It succeeded in renewing but letsencrypt still died and can't access any websites hosted behind it so it's not that.
June 24, 20206 yr 1 hour ago, Jerky_san said: So I checked again this morning. It succeeded in renewing but letsencrypt still died and can't access any websites hosted behind it so it's not that. Anything in the docker log?
June 24, 20206 yr 10 minutes ago, aptalca said: Anything in the docker log? That I see no.. just says "server ready" until I restart it. Ports go completely down but the docker itself is still running. Error logs do not show anything either but it was able to renew the cert last night so it must of went down after that happened.
June 24, 20206 yr 1 hour ago, Jerky_san said: That I see no.. just says "server ready" until I restart it. Ports go completely down but the docker itself is still running. Error logs do not show anything either but it was able to renew the cert last night so it must of went down after that happened. Can you post the output of ”ps -ef" from inside the container when that happens?
June 24, 20206 yr Am I doing this wrong or what don't I understand here.... ? (which is a lot) I'm playing with a Gotify docker container for push notifications. I'm playing with this letsencrypt docker for SSL certificates. Is it possible/how do I use the SSL certs from the letscrypt container in the Gotify container? The Gotify config file has an area for SSL ssl: enabled: false # if https should be enabled redirecttohttps: true # redirect to https if site is accessed by http listenaddr: "" # the address to bind on, leave empty to bind on all addresses port: 443 # the https port certfile: # the cert file (leave empty when using letsencrypt) certkey: # the cert key (leave empty when using letsencrypt) letsencrypt: enabled: false # if the certificate should be requested from letsencrypt accepttos: false # if you accept the tos from letsencrypt cache: data/certs # the directory of the cache from letsencrypt But this seems to require that letsencrypt is running within the same docker container? I've tried just copying the files from appdata/letsencrypt to a folder in appdata/gotify but the files "weren't found", so not sure where gotify was looking for them. The main config file is found in appdata/gotify/config, tried the certs there also. Gotify doesn't have a support thread here so I'll try in the letsencrypt thread, since I need letsencrypt files Thanks for any assistance.
June 24, 20206 yr Success I modified all the lines from okavangonextcloud to okavangonextcloud.duckdns.org and that did the trick. Not usre if they should all be like that but it worked. I was able to login via internal webguie and externally array ( 0 => '192.168.1.138:444', 1 => 'okavangonextcloud.duckdns.org', ), 'dbtype' => 'mysql', 'version' => '19.0.0.12', 'overwrite.cli.url' => 'https://okavangonextcloud.duckdns.org', 'overwritehost' => 'okavangonextcloud.duckdns.org',
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.