alicecantsleep

Members
  • Posts

    25
  • Joined

About alicecantsleep

  • Birthday 10/13/1987

Converted

  • Gender
    Female
  • Location
    Austin

Recent Profile Visitors

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

alicecantsleep's Achievements

Noob

Noob (1/14)

1

Reputation

  1. This appears to be a corruption of the plugin's database. Uninstalling and reinstalling will not resolve as the database remains in it's original location. Remove or rename \\boot\flash\config\plugins\disklocation and disklocation-devel and disklocation-master if you have those folders, then reinstall plugin and reconfigure. Happy weekend!
  2. This would be AMAZING - lets get this comment count up and maybe they'll notice it more. lol
  3. I've had some time to accept that I screwed up and lost some data. I just didn't want to accept it before and was still looking for some solution. Time to rebuild!
  4. Ok but there's NO way to undo that, even though I still have all the data? Flashdrive backup restoration or anything? Nothing can undo that? I still have the data on the drives. Can I not restore from a previous backup to restore that config and redo? That seems like something that should be possible.
  5. I guess I'm just confused as to why I can't rebuild the drive. I have the valid parity data and all the other disks. The data is there to rebuild it I just can't get unraid to realize it.
  6. I could've sworn I cleared the config last time. Seems like I fucked up. I'm starting to find missing data now. Either way, here's the diagnostics. thenervecenter-diagnostics-20220204-0042.zip
  7. A while back my disk 2 took a few UDMA CRC errors and disabled. It appears to be cable related. I have replaced the cable now but I'm having issues re-enabling the disk. I stopped the array and started it without the problem disk. Then added it back in and restarted the array. However, instead of prompting for a data-rebuild, it prompted to clear the disk. Which is fine, if it needs to do that before a data-rebuild. I'm just concerned I've lost the 10tb of data that was on the disk. If Unraid won't prompt a data rebuild after the clear is done, I think I'm screwed. I rebuilt this drive a couple months ago when the errors first happened, but when they happened again and the drive re-disabled, I decided to leave it disabled until I could afford the replacement parts. After getting the new parts installed I did exactly what I did last time. I wiped the drive, cleared the config preserving all assignments, added the drive back. Started array. Stopped array. Removed the drive, started then stopped the array again. Added the drive back, started array. Last time this is when it kicked off the data rebuild. This time it prompted to clear the disk instead. Any insights? I appreciate any assistance!
  8. FYI everyone - there has been zero response for months now. I am planning to replace this in my system now since there are no updates or support. #deadapp
  9. I seem to have two series stuck in my notifications list/preview. I get two listed when I try to exclude it but only one will let me include or exclude them. They show in plaintext instead of a @ role mention. If I click the react to get the role I get "Invalid React Role Mention Clicked" in my logs. Is there a way to clear out the notifications list entirely and re-generate it? Without reinstalling the bot at least? Hopefully @CyaOnDaNet can come out of a 1.5 year hibernation on this thread and assist. EDIT: If this happens to you, remove the .db files in your appdata folder for this docker and restart the docker. You'll have to setup your notification settings again - but now I don't have broken links!
  10. I have everything setup, notification list posted, and users subscribed to shows, but I'm not getting any notifications at all about recently added stuff. My old channel with my tautulli notes is still pinging normally, but I get absolutely nothing from this bot. I'm also having an issue with it properly reporting users as watching. It seems to kinda work for me as the admin, but nothing for any other users. I've linked all the accounts, so I'm not sure what the issue is. Any help would be greatly appreciated! EDIT: I thought it might be an issue with the Tautulli to bot webhook, so I checked the logs. Seems it's sending it some of the time. Half the time I get a webhook notification failure. But it does seem to update the watching role, just very slowly. Still no recently added notifications tho.
  11. Looks like you need libffi Thank you. I was able to install libffi via nerd pack and get my script running. Thanks!
  12. Having a bit of a nightmare just trying to run a python 3 script. I've (re)installed python 3 via nerd tools and pip via terminal but I can't install the future module. I reach out to the team who made the script and according to them, my python3 installation is missing files. I attempted to uninstall python3 and reinstall it, but nerd tools won't uninstall it. I removed nerd tools entirely and reinstalled it, but this did nothing to alleviate my issue. I am on Unraid 6.8.3 using Nerd tools 2019.12.31, Python 3.9.0, and Pip 20.3. When I run 'python3 -m pip install future' or 'pip3 install future' I get the attached error. Any help would be greatly appreciated!
  13. I've changed the server_name in each .subdomain.conf file but it still say there is a conflict. I don't understand how since the containers and storage locations have different names. Where else do I need to change it for this subdomain? server { listen 443 ssl; listen [::]:443 ssl; server_name radarr4k.*; EDIT: I have confirmed it's the presence of both sonarr.subdomain.conf and sonarr4k.subdomain.conf that create the error as removing sonarr4k clears the error. I just got it working for ombi no problems. So there is a solution.
  14. I have recently decided to setup separate instances of Radarr and Sonarr exclusively to handle my 4k content. I installed a second docker instance of each and named them radarr4k and sonarr4k respectively. I set the appdata folder to the same name and placed them on my custom dockernet along with the rest of the others and swag itself. I duplicated my old configs for each to save me some time. I then listed a subdomain in my DNS and added the new subdomains to my swag docker settings. Next I duplicated the proxy-configs and saved them under radarr4k.subdomain.conf and sonarr4k.subdomain.conf. I edited the the file to match the new docker name. I'll paste that below. However, after waiting the 48 hours to ensure my DNS entries propagated fully, my subdomains still don't work. I had the same issue a while back with my speedtest docker and subdomain. Is there a step I'm missing? I also have this weird issue where sometimes sonarr4k.mydomain.com forwards to heimdall.mydomain.com even though I haven't had Heimdall installed for a long time. I even ensured I removed the heimdall.subdomain.conf file and dns entries to try and resolve it. Unfortunately that did not work. Finally, after adding the sonarr4k and radarr4k files, I now get this error in swag: nginx: [warn] conflicting server name "radarr.*" on 0.0.0.0:443, ignored nginx: [warn] conflicting server name "sonarr.*" on 0.0.0.0:443, ignored nginx: [warn] conflicting server name "radarr.*" on [::]:443, ignored nginx: [warn] conflicting server name "sonarr.*" on [::]:443, ignored Unraid 6.8.3 I recently migrated to swag from letsencrypt with no issues. The issues described here were also happening in letsencrypt prior to migration. sonarr4k.subdomain.conf EDIT: I should add that my original subdomains for sonarr, radarr, and others still work fine. Just the new ones don't.
  15. Hiya! I'm having an issue with a subdomain.conf file for my docker 'speedtest'. Since there was no template I copied one of the more basic ones and modified it to try and get it to work. Unfortunately that endeavor has failed and here I am. speedtest.subdomain.conf - https://codeshare.io/aJXrME The speedtest docker is the new Openspeedtest docker. Setup with standard config: On custom docker network for letsencrypt. WebUI available at :3001. That's why I put 3001 in the subdomain.conf as I had seen other dockers set similarly in their subdomain.conf files. Thanks for any and all help! EDIT: I was able to resolve my issue with the following speedtest.subdomain.conf file: server { listen 443 ssl; listen [::]:443 ssl; server_name speedtest.*; 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_app speedtest; set $upstream_port 8080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }