xxDeadbolt

Members
  • Posts

    156
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

622 profile views

xxDeadbolt's Achievements

Apprentice

Apprentice (3/14)

28

Reputation

1

Community Answers

  1. I've also had this after my upgrade to 6.10.3. Haven't had time to properly investigate, hopefully you get some pointers here
  2. Hey, I just got the below message when clicking the Apps tab. Tried on Brave, Chrome & Firefox with CA plugin version 2022.03.13 Something really wrong went on during get_content Post the ENTIRE contents of this message in the Community Applications Support Thread OS: 6.9.2 Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36 Language: No data was returned. It is probable that another browser session has rebooted your server. Reloading this browser tab will probably fix this error Reloading doesn't work, I'm not signed in anywhere else & my server hasn't rebooted today. Edit: added CA debugging Edit2: ....& it's back. I didn't do anything else, so not sure what happened CA-Logging-20220314-1558.zip
  3. I had this & had to update the plugins from the Settings > Plug ins > Install Plug in menu, to make sure an available update was recognised as being available. The main 'Plugins' page said they were up to date, but once I done that & they updated, everything scanned & started doing what it does without issue.
  4. I've just updated with minimal reconfiguration, but on a less technical level: thanks for dark mode!
  5. Nope, I've been on the 4.3.9-2-01 tag since the whole thing with the paths
  6. This is how mine is configured, which works for me: In Sonarr, my 'Settings -> Download Client' option has Qbittorrent with the option at the bottom enabled to do this: Then in Qbittorrent, Settings > Bittorrent, I've set the seed limit to:
  7. Have you tried the steps in the link below to try recovering?
  8. Same here. Worth noting that I followed the link in the post below before I updated & went up to step 14 without seeing any errors. Not sure if that's an indicator of how the migration is likely to go or just coincidence. From sounds of things, I would've expected some errors during the process at some point if the db was corrupt in any way.
  9. I don't remember ever doing it manually, other than first creating my custom docker network, but I obviously have at some point. Just thought it was odd since the Docker Auto Update Settings was the only place it seems to be listed. Cheers, Squid
  10. I've had this before, I think it's fairly common. For the missing keys, run the terminal for the nextcloud container in the Docker page (not the general unraid terminal option on the top right corner) and type 'occ db:add-missing-primary-keys' which should sort that. For the phone region, there's a great video here to edit your config file: I'm not sure on the others, I think the X-Frame-Options can be solved in your reverse proxy config - but don't quote me on that one, I may be remembering that one wrong.
  11. I was going through my autoupdate list & noticed a weird container listed, called 'nostalgic_pike': I've no idea what it was for, seems to not actually be there/installed anymore but I can't find a way to remove it. Never heard of the name before, can't find even a repo with that name. Previously installed apps don't show anything either... Anyone seen this before or know where to look to remove it? Edit: Forgot to say, too, that nothing shows in Cleanup Appdata either.
  12. I *think* this is the docker image space/size, not your actual share folder.
  13. Thanks guys, will give it a go tomorrow. Think I was expecting a full file name instead of a wildcard type, like you’ve said @Mystic. I was rummaging through the dirs earlier looking for a file ending .env or something 😄 Edit: That's it working now, thanks again folks!
  14. Thanks for this, wondered what was up with Heimdall! I don't understand what you mean by this part, though, could you dumb it down a little for me, please? I'm not seasoned with modifying things through the terminal this way.