Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About TexasDave

  • Rank
    Advanced Member


  • Gender
  • URL
  • Location
    Surrey, United Kingdom

Recent Profile Visitors

1113 profile views
  1. @Cpt. Chaz you say: Can you tell me where this is happening? Want to check (and clean) on my system as needed. Thanks!
  2. I used this handy site (check-your-website.server-daten.de) to check and yes, the certs were expiring. In the docker I deleted one of my domains, then added it back, and now I am back on the 90 day window (cheating, I know). I suspect that it relates to a restore I had to do a few months ago and it is now just manifesting itself. But now sorted... Two side questions - how do you access certbot or ssl-cert from the command line in unRAID? Or how can I check cert status directly from unRAID rather than using a 3rd party site? Just curious. Thanks!
  3. Log from starting earkier today....deleted email and domains. ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- 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=Europe/London URL=duckdns.org SUBDOMAINS=aaa,bbb,ccc EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=xxx@zzz.com STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d aaa -d bbbb -d cccc E-mail address entered: xxx@zzz.com http validation is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found: no field package.preload['resty.core'] no file './resty/core.lua' no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core.lua' no file '/usr/local/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/5.1/resty/core.lua' no file '/usr/share/lua/5.1/resty/core/init.lua' no file '/usr/share/lua/common/resty/core.lua' no file '/usr/share/lua/common/resty/core/init.lua' no file './resty/core.so' no file '/usr/local/lib/lua/5.1/resty/core.so' no file '/usr/lib/lua/5.1/resty/core.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './resty.so' no file '/usr/local/lib/lua/5.1/resty.so' no file '/usr/lib/lua/5.1/resty.so' no file '/usr/local/lib/lua/5.1/loadall.so') Server ready
  4. Getting "Let's Encrypt certificate expiration notice". I had thought, in the past, certs where automatically renewed? Or you could force renewal by stopping and starting LE? I can delete and start again but this just started happening in the past few weeks. All was good previously. Just wondering as in the notes above others are having some weirdness. I can submit logs if that helps?
  5. My current system information is below...all works fine for my needs. At the time, 4-5 years ago, this was a pretty solid system (I think) and still is working fine. But I really enjoy tweaking my system. I guess most of us do... 🙂 Been running my system for some time and wondering if it would make any sense to upgrade to a newer CPU and/or add a graphics card? It may not make a noticable difference but I am starting to do some more intense things (like Unmanic). My CPU is a Intel Xeon E3-1230 v3 @ 3.7GHz. MoB is SuperMicro X10SL7-F/ Or it may make more sense to leave things alone and when really needed, do a complete upgrade including MoB, CPU, adding a grpahics card.... I am itching to have a play but if I am going to see minor improvements, I will hold off. Thanks for any thoughts...
  6. So between my CA Backups, I am up and working. In fact, the one backup got Ubooquity working (again). I wonder if there is an issue in running CAbackups when Parity check is happening? No idea. But something weird happened. Not too bothered as I know how to deal with it now... Another thing that came from this is I am now running CAbackups once a week as I make frequent changes to Sonarr and Radarr. This is instead of once a month... While it was a (small) hassle - I now feel pretty good as I know CA Backup is there for me - super lucky to have been doing this.
  7. Making progress. I "pulled out" the Radarr backup from last night, restored it, and Radarr was back to normal. I then did a full restore and it seems most things are back (Thanks CABackup Team 🙂 ). Only issues are now Hydra and Mylar (both had been working) and Sonarr is still not working. Will pull an old backup to get those three items back (I hope). Still would like to understand why or what caused this? Thanks!
  8. To be clear, I was running a "backup", not a "restore" last night. So that is what is weird.... And not all my dockers were affected. Plex, Sonarr, Radarr, OpebVPN, CrashPlan affected Mylar, Hydra, NZBGet seem fine... Really, really strange....
  9. Attaching sonarr log from 2300 last night till now. Something happened between 2200 and 0800 today.... sonarr.txt
  10. @Squid Thanks. I do have some backups I can use but they are a few weeks old. So less than ideal.... I was hoping to understand why I lost things. I was running a CAbackup overnight and a parity check. Trying to understand what coud have caused my dockers and/or appdata to go into an "as new" state? Maybe it has nothing to do with CAbackup or the parity check? Just seems strange that this situation occurred and I am hoping to understand what happened. I can see the appdata is there so not sure why the dockers are not picking it up? I went into edit mode on sonarr, made no chnages but forced a rebuild and it still is not getting back to its previous state.... Just confused how this could happen...Thanks!
  11. Hi folks, Very strange issue...I woke up this morning and Plex, Sonarr, Radarr - all my dockers we in a "as new" state. Overnight my CA backup had run (successfully) and a parity check had started. I have stopped the parity check, stopped the dockers and restarted but they dockers are not picking up the old appdata. Background: 2 weeks ago had to replace to failing disks but this was done successfully During this, I noticed my CAbackup had not been running. I did a manual run (no issues) I can see the appdata is there and looks good. I also have the backups I can restore. Just trying to figure out what the issue could be and how best to debug. Diagnostics attached. Thanks! unraid-diagnostics-20191002-0952.zip
  12. Looking for some help. I have had this working for a long time. This morning, I had to shutdown my server to replace the battery in my UPS. When I came back up, I was getting the "Welcome to our server" message when trying to access ubooquity externally.... Internal access works fine (both user (port 2022) and admin (port 2023)). Ombi (which is also reversed proxy'd) is working fine internally and externally. Router ports are fine Nginx ubooquity conf files is fine and has not changed (attaced). Using the one provided and just chnaged to my subdomain (dz-comics) Deleted ubooquity appdata and docker and this has not fixed it No errors in Letsencrypy or ubooquity logs.... Letsencrypt, ombi and ubooquity on "proxynet" This is the URL that has always worked until this morning: https://dz-comics.duckdns.org/ubooquity/ I think the "Welcome" message usually means your nginx conf file has an error? Before flooding the support thread with logs - what are the most common causes for the "Welcome to our server" message? As ombi is working, I lean to an error on ubooquity but am paranoid on a "typo" being an issue after I reinstalled everything. Happy to post anything to get another pair of eyes to sort this...Thanks! [EDIT: Fixed this by restoring an older version of the ubooquity appdata using CABackup. Over the weekend, I am going to try to do a diff and see what the issue was. I have had more issues with Ubooquity than all other services combined. I want to understand why...] ubooquity.subdomain.conf
  13. I was having an issue with getting "Load Qualities" and "Load Folders" in the Sonarr and "Get Quality Profiles" and "Get Root Folders" in Radarr. I pushed the button and they would just spin. @casperse posted a fix (thanks) and this fixed it for me. Just posting in case others run into the issue. I was also getting this error: Do NOT fill in your Base URL...or at least in my situation, this fixed my issue. Just hoping this helps others in fixing the issue. Thanks @casperse!
  14. I did know about that and its very helpful. For my case, I will click on a parent, lets say there are 200 items. If I want to pick 30, it would be good to be able to do this easier if that makes sense. But it is a "nice to have". Something like the SHIFT / CTL options to select in Windows. Just a suggestion, thanks again for this awesome tool.