MrMoosieMan

Is the drive bad or was there some sort of corruption? Why would that just happen? Is it possible to fix the issue and recover my old "appdata" directory?

I have not made any changes in a while. tower-diagnostics-20230910-1206.zip

No, it does not appear that it is. What could have caused the data to be deleted?

What do you mean "it will show as new"?

Hello! Rebooted and when I clicked on the "Docker" tab I was met with "No Docker containers installed". I reinstalled the containers via "Apps tab/Previous Apps". Once I install and launched the apps, it appears I need to reconfigure the application from scratch. I thought that once you installed the apps using a previously used template, you would NOT need to reconfigure them. What am I missing? Thank you in advance!

Screenshot from Glances and Diagnostics are attached. I'm having an issue with slow performance with applications. I've noticed I continue to receive "CPU_IOWAIT" alerts within Glances. Any idea what can cause it and how to resolve it? Thank you! tower-diagnostics-20191202-1323.zip

I just answered my own question. Not sure why but my API key had changed with Cloudflare. Replaced the key and BAM, it renewed without issue.

I was alerted via email that my LetsEncrypt cert was expiring soon. I decided to run "certbot renew" from the CLI but received the below error. After much troubleshooting I am unable to determine what could be causing the issue. The logs do not give much info other than what is below. Any thoughts? root@f74f982f283f:/# certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/mydomain.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert is due for renewal, auto-renewing... Plugins selected: Authenticator dns-cloudflare, Installer None Renewing an existing certificate Performing the following challenges: dns-01 challenge for mydomain.com Unsafe permissions on credentials configuration file: /config/dns-conf/cloudflare.ini Cleaning up challenges Attempting to renew cert (mydomain.com) from /etc/letsencrypt/renewal/mydomain.com.conf produced an unexpected error: Error determining zone_id: 9103 Unknown X-Auth-Key or X-Auth-Email. Please confirm that you have supplied valid Cloudflare API credentials. (Did you enter the correct email address?). Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/mydomain.com/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/mydomain.com/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 renew failure(s), 0 parse failure(s)

Thank you!

Two questions: 1) Any idea why am I getting this error when trying to install? Unable to find image 'metmma/metamma:latest' locally /usr/bin/docker: Error response from daemon: pull access denied for metmma/metamma, repository does not exist or may require 'docker login'. See '/usr/bin/docker run --help'. The command failed. 2) Once installed, how to I use it? Thanks in advance!

I'm very new to setting up LetsEncrypt. I'm having an issue with obtaining my cert. FYI...I am a routing and security engineer and feel confident my network is configured properly. I'm only tell you this so that you will feel somewhat confident in my network. Certainly not telling you this to sound like a know-it-all/jackass. Also, just to add, I have verified two-way communication between the container and LetsEncrypt using the ports I specified via packet-captures. When I start the container I can see it communicating with devices on the internet but I'm still getting the below error. I have verified that "MyNon-DDNSdomainName.com" and "plex.MyNon-DDNSdomainName.com" resolves correctly to my public IP. I'm stumped - DNS forwarding and port-forwarding appears to be working yet I'm getting "connection refused" Variables set: PUID=99 PGID=100 TZ=America/New_York URL=MyNon-DDNSdomainName.com SUBDOMAINS=plex EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= [email protected] STAGING= Created donoteditthisfile.conf Creating DH parameters for additional security. This may take a very long time. There will be another message once this process is completed Generating DH parameters, 2048 bit long safe prime, generator 2 This is going to take a long time ...................................................................................+..................................................................................................+...............................................................................................................................................................................................................................................................................................................................................+.....................................................................+............................................................................................................++*++*++*++* DH parameters successfully created - 2048 bits SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d plex.MyNon-DDNSdomainName.com 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 plex.MyNon-DDNSdomainName.com Waiting for verification... Challenge failed for domain plex.MyNon-DDNSdomainName.com http-01 challenge for plex.MyNon-DDNSdomainName.com Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: plex.MyNon-DDNSdomainName.com Type: connection Detail: Fetching http://plex.MyNon-DDNSdomainName.com/.well-known/acme-challenge/WZ75elsNMJQFuroOl-8itA8JOfBER7fnN9emxDcn4Ys: Connection refused To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - 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. 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

Hello! I was having issues with my unRAID box not responding so I rebooted it from the CLI. Once it came back up, I was unable to access the GUI. I am able to SSH to it. Do you mind taking a look at my diagnostics file and giving me you're thoughts? Also, I should add that I received the below errors when creating the diagnostics file. When I KVM into the server I can see its stuck and will not move beyond a certain point (see attached picture) root@Tower:~# diagnostics Starting diagnostics collection... Warning: file_get_contents(/var/local/emhttp/cpuload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 88 Warning: file(/var/local/emhttp/diskload.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 89 Warning: parse_ini_file(/var/local/emhttp/disks.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 90 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 91 Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 100 done. ZIP file '/boot/logs/tower-diagnostics-20190716-1021.zip' created. Thanks in advance! tower-diagnostics-20190716-1021.zip

I have the same issues and am unable to locate a solution.

I see no way of doing this. I would think you would spin up another instance of the Docker container for the 2nd network. I have a few instances of Plex running on different networks using this method.