Greg001

Members
  • Posts

    5
  • Joined

  • Last visited

Greg001's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Hi all, I've been running home assistant as a docker for a couple of years now with little issue. I set up an uptime monitor pinging the URL and in the past few months, it's been going unavailable for hours at a time. If I try connecting (remote or local) it doesn't respond. When that's happening, I sometimes have issues connecting to Unraid itself. I noticed recently I was using a lot of RAM so added 8GB (total of 16, 2x8GB) and everything seemed to be fine for a few days, then today I got the downtime notification again. Once I got home, I connected to Unraid and the CPU usage seemed to be at a 100%. Then it dropped down as I was watching and I got a notification that home assistant was back up. It felt like me logging into Unraid forced it to kill a process? I looked at the logs and the time I connected sees an action (19:37, process killed), but nothing between 16:50 and then, which is when I got the downtime notification. Would love any insights or suggestions. Uploading the diagnostics in case anyone might see something I'm missing. I don't have any VMs and I've since deactivated a few docker images I wasn't really using, not sure if that will make a difference though. Thanks in advance! tower-diagnostics-20230910-2224.zip
  2. Hi! I've been away for a few weeks. Got back and when checking Unraid notice a device is disabled. Unfortunately I didn't know much about it and my first instinct was to reboot, so my diagnostics don't include any info from when it happened. I've since then read through a few forum posts (and admittedly like others had trouble finding some info since all the links to documentation are broken) and tried to follow instructions. As far as I can tell, the SMART check is ok. I also tested the filesystem which didn't throw up any errors. I've done a spot check on the data (photos and such) which looked fine, but I don't know if that's enough to confidently say all the data is correctly emulated. Is there something else I should be doing before I attempt a "rebuild onto itself"? Thanks in advance! tower-diagnostics-20230708-1428.zip
  3. Darn, and here I was trying out those answers in case it helped my case! Any ideas what might be wrong with my logic and setup? I don't remember having to move or configure anything to indicate where the certificates are generated, could this explain why they can't be found? Happy to post any logs or configs that might help figure this out.
  4. Hey all! I've been lurking for a while (weeks and months by now!) trying to figure out what I might be doing wrong, but figured it was time to actually ask for help I'm trying to set up letsencrypt to access nextcloud and others. I've followed SpaceInvaderOne's videos and various other guides online. I ended up switching to DNS validation thinking it might be an issue with port forwarding or my isp blocking some ports (as I understand it, DNS validation would avoid all this). Letsencrypt logs show "Server ready", but I still can't access my containers. I get an ERR_SSL_PROTOCOL_ERROR message. I've also tried using tools like https://www.sslshopper.com/ssl-checker.html to check and the IP resolves to my router, but it tells me that no SSL certificates were found and to check name resolution and port forwarding (which is how I switched to DNS validation in the first place). Any help would be appreciated! Are there any other tools that might show me better where things are failing? Letsencrypt log below. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ 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=America/New_York URL=REDACTED.net SUBDOMAINS=wildcard EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=dns DNSPLUGIN=cloudflare [email protected] STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing Wildcard cert for only the subdomains of REDACTED.net will be requested E-mail address entered: [email protected] dns validation via cloudflare plugin is selected Certificate exists; parameters unchanged; starting nginx creating GeoIP2 database [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