Greygoose

I found this post, I havent time to try tonight, hopefully someone here can and post exact instructions for unraid setup Solution: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA https://community.letsencrypt.org/t/solution-client-with-the-currently-selected-authenticator-does-not-support-any-combination-of-challenges-that-will-satisfy-the-ca/49983

just installed letsencrypt after 1 week to try again ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.website.com -d nextcloud.website.com E-mail address entered: [email protected] Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. IMPORTANT NOTES: - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. /var/run/s6/etc/cont-init.d/50-config: line 134: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

I am trying this again the weekend, as I had my DNS certificates REJECTED as i kept trying too many times and had to wait 7 days to issue new cert. Whats the most simple docker to get working with letsencrypt docker, raddarr or something?

I am trying to sync a 50gb locally on the same nextwork as my nextcloud server. is this possible, as when i check the nextcloud folder i get the file name.part several times?

How do i change the maximim upload file size please ? EDIT: I changed this in webui, /additional settings - file handling It takes 5 minutes or so to activate but my 60gb file is now uploading.

Please advise, i have no hair remaining. Im following this guide https://linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/ Prior to editing the nextcloud config.php and creating the nextcloud file nextcloud worked fine.... lets encrypt looked to be doing its thing (docker stayed open) and when I entered nextcloud.mywebsite.com it would ask to accept certifate then show the letsencrypt page. I also pinged my nextcloud.website.com and it come back with my static ip address. When i goto webbrowser and try https://nextcloud.mywebsite.com i get 502 bad gateway CONFIG.PHP root@unraid:/mnt/cache/appdata/nextcloud/www/nextcloud/config# <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => '254v24v42', 'passwordsalt' => '425v24v42v', 'secret' => '324rt23gwevewg45v', 'trusted_domains' => array ( 0 => '192.168.1.200:446', 1 => 'nextcloud.mywebsite.com', ), 'overwrite.cli.url' => 'https://nextcloud.mywebsite.com', 'overwritehost' => 'nextcloud.mywebsite', 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '12.0.4.3', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.200:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'Bond', 'dbpassword' => 'SECRETPASSWORD', 'installed' => true, ); --------------------------------------------------------------------------------------- nextcloud root@unraidserver:/mnt/cache/appdata/letsencrypt/nginx/site-confs# server { listen 443 ssl; server_name nextcloud.mywebsite.com; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE$ ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://192.168.1.200:444/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } } ---------------------------------------------------------------------------------------------------------------------------- EDIT: this is my nextcloud/nginx/site-confs/ default upstream php-handler { server 127.0.0.1:9000; # server unix:/var/run/php/php7.0-fpm.sock; } server { listen 80; server_name _; # enforce https return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name _; ssl_certificate /config/keys/cert.crt; ssl_certificate_key /config/keys/cert.key; # Add headers to serve security related headers add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Content-Type-Options nosniff; # add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; # Path to the root of your installation root /config/www/nextcloud/; # set max upload size client_max_body_size 10G; fastcgi_buffers 64 4K; # Disable gzip to avoid the removal of the ETag header gzip off; # Uncomment if your server is build with the ngx_pagespeed module # This module is currently not supported. #pagespeed off; index index.php; error_page 403 /core/templates/403.php; error_page 404 /core/templates/404.php; rewrite ^/.well-known/carddav /remote.php/dav/ permanent; rewrite ^/.well-known/caldav /remote.php/dav/ permanent; # The following 2 rules are only needed for the user_webfinger app. # Uncomment it if you're planning to use this app. #rewrite ^/.well-known/host-meta /public.php?service=host-meta last; #rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json last; location = /robots.txt { allow all; log_not_found off; access_log off; } location ~ ^/(build|tests|config|lib|3rdparty|templates|data)/ { deny all; } ^G Get Help ^O Write Out ^W Where Is ^K Cut Text ^J Justify ^C Cur Pos M-U Undo M-A Mark Text M-] To Bracket M-↑ Previous ^B Back ^← Prev Word ^A Home ^P Prev Line ^X Exit ^R Read File ^\ Replace ^U Uncut Text ^T To Spell -------------------------------------------------------------------------- This is my namecheap dns

I am now going to follow this guide https://linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/

im on 6.4 rb17 I hve changed port to 444 I got this response _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d www.mydomain.com -d nextcloud.mydomain.com E-mail address entered: [email protected] Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the cert. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for www.mydomain.com tls-sni-01 challenge for nextcloud.mydomain.com Waiting for verification... Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for www.mydomain.com tls-sni-01 challenge for nextcloud.mydomain.com Waiting for verification... Cleaning up challenges IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/www.mydomain.com/fullchain.pem. Your cert will expire on 2018-03-31. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/www.mydomain.com/fullchain.pem. Your cert will expire on 2018-03-31. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server ready

im still trying, im about 10hrs invested and i cant get it to work I am starting from scratch, removed each dockers and doing each step, id be gratful for guidance 1. install lets encrypt docker 2. register namecheap domain and point back to my static IP address 3. ping domain name and i get a ping back from my static IP address 4. I try to start lets encrypt docker and i get Error (port 443 in use)

Ive changed this many times. When I run my sub domain from my webbrowser it takes me to my router page that gives me pfsense error screen (which is my router) I have port 443 forwarding to my Unraid ip.

Lets encypt Log

EDIT: under advance DNS i have pointed my Domain to my ip address, took me hours to understand this now i am sorting the letsencrypt code.

I'm out my depth a little here, not sure where to proceed once i have purchased a domain name

I have purchased my domain at name cheap. Unsure what to change in the Namecheap config.

Hi CHBMB, Thanks for the reply. I'm going to set this up tomorrow, if I purchase a domain where is best place to buy.

I have a static IP address, do i still need to purchase a domain?

im getting this error, im using autoprocesstv.cfg, its working but i still this this error from Sab Unable to open URL: <urlopen error [Errno 110] Connection timed out>

Just want to say thanks for this docker, my most reliable and used docker on Unraid. Thanks binhex

Sounds great, less for plonkers like me to setup incorrectly. Altho I don't see much for me to get wrong now that you have helped me with most of the possibilities.

Oh my, sorry to waste your time and Thank you for pointing this out, I am a plonker...

Thanks Binhex supervisord.log

SabVPN has stopped working since i upgraded my cache. it works when i turn VPN to NO... but the settings are the same as before

There are two ports, Container port and host port. The container port is "in grey" and shouldn't be changed, the host port can be changed. This means that say two dockers run on 8080, you can have two containers use that port but buts use different host ports.... ie Container A on 80/8080 Container B on 81/8080. both dockers using 8080

is this a problem, i get it when i open Sabvpn Traceback (most recent call last): File "/opt/sabnzbd/cherrypy/wsgiserver/__init__.py", line 2024, in start self.tick() File "/opt/sabnzbd/cherrypy/wsgiserver/__init__.py", line 2091, in tick s, ssl_env = self.ssl_adapter.wrap(s) File "/opt/sabnzbd/cherrypy/wsgiserver/ssl_builtin.py", line 67, in wrap server_side=True) File "/usr/lib/python2.7/ssl.py", line 363, in wrap_socket _context=self) File "/usr/lib/python2.7/ssl.py", line 611, in __init__ self.do_handshake() File "/usr/lib/python2.7/ssl.py", line 840, in do_handshake self._sslobj.do_handshake()error: [Errno 0] Error

I understand now, i don;t know how the container port was changed. I was only changing the host port (at least i thought). I spent hours changing stuff so somehow it happened.