stlrox

Suddenly MQTT container stopped working. There is no information in the logs. This container worked without any issues for the last two years. Recently I upgraded to OS 6.10.3. I verified directory path and there is no issue with the permissions. I tried to restart this several times but didn't produce any helpful information in the logs. I appreciate any tips for solving this issue.

I have Dell T30 Server with default config (1 TB) which I use for Home Assistant and other containers. I bought a new 4 TB Western Digital Red Plus SSD drive which I would like to add to the array. I didn't install any parity drives. I don't have that much data. Few questions. 1. How do I transfer contents of 1 TB to 4 TB drive? 2. If the above is possible, how do I setup 1 TB drive as parity drive for now (later I will buy another 4 TB drive to upgrade that). Thank you

Thank you. I cleared cache and was able to access Nextcloud UI via subdomain1.duckdns.org When I am at home why can't I access Nextcloud UI using the IP address? Just curious.

Nice. Thank you for the tip. I did that and default file appeared back. I left that default file as it is and made changes 'nextcloud.subdomain.conf' file. Could someone confirm these entries in this file. As of now when I browse to 'WebUI' from NextCloud container, am getting 'Welcome to our server' message. This setup worked before and don't know what changes I made to make this break. server { listen 443 ssl; server_name subdomain1.*; root /config/www; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nextcloud nextcloud; proxy_max_temp_file_size 2048m; proxy_pass https://$upstream_nextcloud:443; } }

After setting up port forwarding everything worked correctly with Nextcloud container. I was able to access Nextcloud using duckdns domain. But in the excitement of that working correctly then I tried to set up for Home Assistant duckdns external access. But I messed up with Nginx configuration files and screwed up both Nextcloud and Home Assistant setup. Could someone point out from where I can grab the original nginx\site-confs\default file. Thank you

You, sir, deserve an award. I corrected port forwarding in Google Wifi and bingo! 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d subdomain1.duckdns.org -d subdomain2.duckdns.org E-mail address entered: [email protected] http validation is selected 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: http-01 challenge for subdomain1.duckdns.org http-01 challenge for subdomain2.duckdns.org Waiting for verification... Cleaning up challenges IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/subdomain1.duckdns.org/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/subdomain1.duckdns.org/privkey.pem Your cert will expire on 2019-04-09. 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 renew" - 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 New certificate generated; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. New certificate generated; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server ready

Yes, I tried but that didn't work. Here are the screenshots. Let me know if I entered the wrong information here. Isn't this applies to all devices to connect to ATT router (and Google Wifi)?

I verified both IP addresses and they match. Here is Google Wifi router port forwarding settings and these settings worked before. I deleted these and added them again but still the same issue. My setup is --> ATT Uverse router --> Google Wifi router --> ethernet --> unraid server I ran port scanner tool and found both 80 and 443 ports were timed out (Connection timed out). But when I connected to a VPN service then same ports were open. I checked with my ISP (AT&T) and they do not block 80 and 443 ports. I watched SpaceInvader video again and modified LE docker settings but still the same error. Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=duckdns.org SUBDOMAINS=subdomain1,subdomain2 EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= [email protected] STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d subdomain1.duckdns.org -d subdomain2.duckdns.org E-mail address entered: [email protected] http validation is selected 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: http-01 challenge for subdomain1.duckdns.org http-01 challenge for subdomain2.duckdns.org Waiting for verification... Cleaning up challenges Here is the error message: - The following errors were reported by the server: Domain: subdomain1.duckdns.org Type: connection Detail: Fetching http://subdomain1.duckdns.org/.well-known/acme-challenge/token: Timeout during connect (likely firewall problem) Domain: subdomain2.duckdns.org Type: connection Detail: Fetching http://subdomain2.duckdns.org/.well-known/acme-challenge/token2: Timeout during connect (likely firewall problem) ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container I am running out of ideas, to fix this issue.

I verified my IP address and that was not changed. Looks like this issue started from last week change to LetsEncrypt docker. As of now, there is a new update for this container. How do we know what changes were made in the new update? "Jan 5 04:40:03 Tower root: Fix Common Problems: Warning: Docker Application letsencrypt has an update available for it" No idea. I used SpaceInvaderOne video for reference and kept same settings. Please if I need to change any setting related to this. Thank you

My Letsencrypt docker container stopped working. It was working fine till last week and suddenly I couldn't browse to my Home Assistant duckdns (subdomain1.mydomainname.duckdns.org) and NextCloud duckdns (subdomain2.mydomainname.duckdns.org) sites. Based on the log file, it was not an issue related to cert renewal. There were no errors in letsencrypt.log file and don't know where to start looking to fix this issue. I appreciate your help. ------------------------------------- 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... Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=mydomainname.duckdns.org SUBDOMAINS=subdomain1,subdomain2 EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= [email protected] STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d subdomain1.mydomainname.duckdns.org -d subdomain2.mydomainname.duckdns.org E-mail address entered: [email protected] http validation is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server ready I get the following page when I browse to those sites. This site can’t be reached subdomain2.mydomainname.duckdns.org took too long to respond. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_TIMED_OUT