Tzundoku

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Tzundoku's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. I thought I had to! I have my ip proxied through cloudflare, unsure if that counts. I just tried adding a CNAME that points valheim.mydomain.com to mydomain.duckns.com, doesn't seem to work though. Just tried accessing through IP and that didn't work either though, so my issue is probably related to my mikrotik router settings not playing well with the containers' fixed IP assigned through unraid (although I can ping the container, its not showing up on my routers IP leases so possible issue there with forwarding traffic). Thanks for the reply!
  2. Hey, thanks for this! I'm having moments of brain lags and can't think through on how to properly configure subdomain redirection on a dynamic IP using cloudflare and duckdns. I'm supposed to add an A record in cloudflare which redirects valheim.mydomain.com to my external IP. Not sure how to properly configure this so it follows duckns?
  3. Thanks a bunch. Tried as per the guide, came up with this: I might have misled you as I got confused over what I was seeing: the drive I noticed was btrfs wasn't the nvme cache, the actual nvme cache (similar model to the btrfs one) wasn't appearing in any of my devices (since it dropped offline apparently) and I didn't realize I was looking at the wrong drive. The nvme cache is currently showing (after powering off and taking the server off power for a while), but it appears as a new device if I attempt to set it to the cache pool. The above filesystem status corresponds to the correct nvme drive.
  4. Appreciate the prompt reply. Noticed its for btrfs, tried to see if I could rescue the data since the drive is currently showing as btrfs (no manual format attempted). Attaching current diags, after reboot. tower-diagnostics-20210610-2238.zip
  5. I hope I'll make sense here, Uptime was uninterrupted since upgrading to 6.9.1 (stable launch) until all of a sudden I couldn't access containers remotely. Upon checking I noticed a full syslog, docker/VMs down. Restarted and the cache (xfs) was then showing as an Unassigned device- as soon as I reassigned it to the pool I got the error shown in the title. I attempted to follow this guide, and after mounting there's only a single folder left with some of my NC data. Taking the cache off the array, it appears as it's btrfs with 0 bytes used/0 free until formatted. Any idea what happened here? Any chance I can recover the data? Thanks for your time! tower-diagnostics-20210609-2209.zip
  6. Appreciate the promptness, going to give it a try. Although probably unrelated then, any ideas on the hdd appearing as missing?
  7. Hi there! So the last week or two I've been running into the issue were everything is working fine, then a day or two later I attempt to access a service and later notice that VMs and containers are either missing or stopped, while several btrfs related errors appear in the log. A server reboot brings everything back online, apart from a couple of new log errors showing in some containers (i.e. sonarr). Unsure if this might be related, but I'm passing through an external usb HDD to a Win10 VM using the Unassigned Devices plugin. This HDD initially appears as expected, but after a couple of hours shows as missing, even though the Win10 VM properly recognizes it at the same time. This HDD is used for long term storage of BlueIris videos so there is some form of constant activity on it. I've been playing around with Unraid for a year or so, so I'm still trying to figure how to troubleshoot this. Last 2 diagnostics logs attached, first one tower-diagnostics-20201102-1149.zip was in relation to containers disappearing, second one tower-diagnostics-20201031-0419.zip was related to VMs disappearing while half containers were automatically stopped. Thanks for your time!
  8. So after completing my unraid setup with letsencrypt/duckns for several containers and not tinkering around for several months, I randomly lost access to all forwarded containers (cloudflare error 522). While going through the various settings I noticed that under network settings the titles' message appears: Ethernet interface port 0 is down! Check cable. So I swapped cables and the issue is still there. Plugins and containers are set to auto-update weekly. I attempted updating to the beta 6.9.0 version just in case it resolved spontaneously but the download is idling at 0%. Not sure what else might be required to troubleshoot, feel free to ask. Diagnostics log attached. Appreciate your time, Thanos. tower-diagnostics-20200807-1439.zip
  9. Hi there! I'd like to request some assistance on troubleshooting a weird phenomenon I'm experiencing while connecting to the VM via Splashtop. Tried googling but didn't manage to find anything relevant so far. So I'm running the latest Unraid image on an R710 server with RX580 GPU passthrough and 6 vCPU / 8GB RAM assigned to the VM. The server is headless, so I log to unraid via webGUI and use Splashtop to access the macOS Catalina VM. Whenever I move the mouse all CPU cores spike to 100% usage and the cursor appears to "lag behind". At the same time, I'm using Horos (projecthoros.org) to view medical images which can be pretty demanding depending on the database size, and vCPU usage appears to stay around 50-70% during initial database processing (as long as I'm not moving the mouse). So yeah, any ideas? Thanks!
  10. Hey there, thanks for the great work. Any way I can configure the search engine options? I.e. remove the ones I never use and add "custom" ones from specific sites I search through often?
  11. Hello! I keep running into the following error when attempting to connect Mylar to Deluge: [Deluge] Could not establish connection to 192.168.0.1:58846. Error returned: Password does not match, localclient Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/deluge/core/rpcserver.py", line 267, in dispatch ret = component.get('AuthManager').authorize(*args, **kwargs) File "/usr/lib/python3.8/site-packages/deluge/core/authmanager.py", line 125, in authorize raise BadLoginError('Password does not match', username) deluge.error.BadLoginError: Password does not match I attempted to add the Deluge user "mylar:mylar:5" to /mnt/user/appdata/deluge -> auth but the username is not recognized as existing, I attempted to use the username "localclient" as it appears in the auth file and it is recognized as valid but I'm unable to get the password right: tried the dockers' default, tried copy-pasting the one shown in the auth file, and tried replacing the one shown in the auth file with no luck. Thanks for your time.
  12. Changed settings as shown in the image and followed the linked guide, letsencrypt still comes up with: Challenge failed for domain .myserver.com Type: Unauthorized "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." Checked. When trying to access nginx from outside the network according to the guide (i.e. nextcloud.myserver.com) a page comes up along the lines of "this page is under construction". Also, when attempting to port check ports 80, 180, 443, 1443, the connection is refused on 80/443 and timed out on 180/1443. Thoughts?
  13. Hello there. Unsure if this is the most appropriate place to ask but I guess it's worth a try. I keep getting "Challenge failed for domain.." in the initial setup validation and I suspect I'm messing up with the port-forwarding somewhere along my network. -Following SpaceInvaderOnes' guide on Letsencrypt I have http pointing to 180 and https to 1443. -I have an "obligatory" modem provided by my ISP (Technicolor TG789vac v2) which does not allow/provide an option to switch to bridge mode due to some kind of conflict with VoIP. My port settings are visible in image 1. -I have a Mikrotik hEX PoE Routerboard with port settings visible in image 2, or as follows: /ip firewall nat add action=dst-nat chain=dstnat comment=Letsencrypt dst-port=80 dst-address=!192.168.88.1 protocol=tcp dst-address-type=local to-addresses=192.168.88.88 to-ports=180 add action=dst-nat chain=dstnat comment=Letsencrypt dst-port=443 dst-address=!192.168.88.1 protocol=tcp dst-address-type=local to-addresses=192.168.88.88 to-ports=1443 /ip firewall nat add action=masquerade chain=srcnat comment=Letsencrypt dst-port=180,1443 dst-address=192.168.88.88 protocol=tcp Where 192.168.88.1 points to the Mikrotik router and 192.168.88.88 points to Unraid. Any ideas on where I might be messing up? Please ask if additional info might be required. Appreciate your time and effort.