carnivorebrah

Still having this problem, and can't find a solution. My log file is filled with errors and warnings that I can't get rid of. Searching for the error just takes me to GitHub where it states it's "fixed" in whatever version (i'm on the latest and its still not fixed), or Reddit or here where there's no solutions. Makes no sense that it works and just randomly stops multiple times throughout the day. Having to restart it every few hours is getting incredibly annoying. Log: [1680787763] unbound[1:0] info: service stopped (unbound 1.13.1). [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:7fd::1 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:7fd::1 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:dc3::35 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:7fe::53 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:a8::e port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:1::53 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:12::d0d port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:200::b port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:9f::42 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:7fd::1 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:1::53 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:200::b port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:12::d0d port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:a8::e port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:dc3::35 port 53 [1680787764] libunbound[21:0] error: udp connect failed: Cannot assign requested address for 2001:500:200::b port 53 [1680787764] unbound[1:0] warning: setrlimit: Operation not permitted [1680787764] unbound[1:0] warning: cannot increase max open fds from 40960 to 156232 [1680787764] unbound[1:0] warning: continuing with less udp ports: 2125 [1680787764] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning [1680787764] unbound[1:0] error: Could not open logfile /dev/null: Permission denied [1680787764] unbound[1:0] info: start of service (unbound 1.13.1). Container: Queries being resolved by unbound in pi-hole: My Pfsense box is 10.100.1.1 and pointed to my Pi-Hole at 10.100.1.2 for the DNS Resolver. Pi-Hole is pointed to Unbound. It "works" for a little bit, and randomly stops until I restart it. Then it does it again and again and agian.

Did you ever find a solution for this? I'm getting the same error in my log, and I'm trying to fix that plus my Unbound just randomly stops working multiple times a day every day. Can't find a solution for that either.

Does any one know why I constantly have to restart this container in order for it to work until I have to restart it again? Multiple times a day, every day, DNS will just stop working all together. Restart Unbound, and everything starts working again until it doesn't. I'm using a dedicated pfsense box that is pointed directly to my pi-hole container that is directly pointed to unbound. Diagnostics attached. diagnostics-20230324-1106.zip

Same here. In the Apps tab, it shows up under Action Centre as "Deprecated", and has a note on it that reads: Advised to switch to the version from SimonF which is also compatible with Unraid 6.12+ This application template has been deprecated Tried searching Google to see if I could find it anywhere, but not having any luck.

I ended up just giving up on encryption, and disabled it completely. Didn't even install the end-to-end encryption or default encryption module apps. Looks like it won't be fixed until NC 26, and I'm not waiting for it to just break again. It was too much of a pain to decrypt my old files and rebuild the instance numerous times trying to get it to work.

It just never ends with this thing. Now I'm running into this bug: https://github.com/nextcloud/server/issues/32003 Does anyone know where the openssl.conf file is they are saying to modify? I can't find it in anywhere in the nextcloud appdata folder.

Were you ever able to find a solution for this? I'm having this exact issue on a fresh install. It just repeats this over and over nonstop. This is in the log: {"reqId":"SAzLk3RXnQcdzjQmmAAF","level":3,"time":"2023-02-24T22:55:00+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Not installed","userAgent":"--","version":"","exception":{"Exception":"Exception","Message":"Not installed","Code":0,"Trace":[{"file":"/config/www/nextcloud/lib/base.php","line":680,"function":"checkInstalled","class":"OC","type":"::"},{"file":"/config/www/nextcloud/lib/base.php","line":1144,"function":"init","class":"OC","type":"::"},{"file":"/config/www/nextcloud/cron.php","line":43,"args":["/config/www/nextcloud/lib/base.php"],"function":"require_once"}],"File":"/config/www/nextcloud/lib/base.php","Line":284,"CustomMessage":"--"}} I'm using the most recent spaceinvaderone nextcloud install tutorial. Setup MariaDB and my nextcloud share. Then this is what happens when I try to start Nextcloud after installing it. Google brings me to the quoted post above with no solution. Found this too, but still no solution: https://help.nextcloud.com/t/first-time-nextcloud-user-unraid-setp/144861 Finally found this: https://github.com/linuxserver/docker-nextcloud/issues/280 Apparently it's already "working". It just didn't report anything in the logs except errors. All I had to do was open the web UI to see it was working.

Wow, okay, rebooting fixed it. Now the renamed share is showing up with the new name and all the other shares. I really wish it would have just said "Reboot to apply changes" instead of "share name deleted". At least I still have my data which is what matters in the end.

I tried! They won't download. I don't know what else to do. I have not tried rebooting, but honestly I'm scared to try that.

I am in the process of trying to setup Nextcloud from scratch, but wanted to back up my old copy of it to have just in case I needed something from it. I tried renaming the "nextcloud" share I had in Unraid to "nextcloud_bak", but when I clicked "Apply" it said "nextcloud_bak" deleted, and then all of my shares disappeared. I have no idea what to do. I have 15TB of data and I'm freaking out because I can't access any of my shares any more. I tried downloading diagnostics, but it just sits there never downloading. Please help! When I try to cd to the "user" directory, it gives this error now: bash: cd: user: Transport endpoint is not connected

I had this exact issue. I had to remove "ncp disable" from my ovpn file and now it works fine. My ovpn file didn't have this option in it.

Holy hell... this thing is going to be the death of me. Found the solution at the below link where someone had the exact same issue with the exact same board/cpu combo. Had to reflash the BIOS using IPMI. VMs all working again. https://serverfault.com/questions/959234/enable-supermicro-virtualization-in-bios

It's just one thing after another with this thing... smh... In order to fix my issues with my GPUs randomly not working with my old motherboard, I decided to upgrade my motherboard, and went ahead and upgraded my CPUs and RAM in the process. I can now get Unraid to boot with my GPUs that randomly decided they would no longer work on my old motherboard. The problem I'm now having is that none of my VMs will work, and have disappeared from my list of VMs after I attempted to resave the new CPU pin assignments. Now, when I try to recreate them from my backups, I get the following error: UNSUPPORTED CONFIGURATION: EMULATOR '/USR/LOCAL/SBIN/QEMU' DOES NOT SUPPORT VIRT TYPE 'KVM' After some searching, I found that this is due to "SVM" being disabled in the BIOS. However, my BIOS doesn't have "SVM", it has "Intel Virtualization Technology", which is enabled. I checked everything else in the BIOS and everything is enabled as well. I'm not sure what is causing this or how to fix it. The new motherboard is a Supermicro X9DR3-LN4F+ and the CPUs are E5-2690 V2 CPUs. BIOS version is latest 3.4. I also noticed that the VM Manager shows this warning: But my BIOS shows that this is enabled and supported for both CPUs: Chipset north bridge: Chipset south bridge: I really don't know what else to do now.

Well now it randomly decided it's going to boot now. I can't even deal with this thing any more.

My server is being the biggest pain in my ass lately. It randomly decided it's no longer going to display video though the P2000 that I bought to replace the P2200 that it decided it was no longer going to work with anymore. Now I have two several hundred dollar paper weights that have been sent to PNY only for them to tell me "they work great!" The only card I have that will work is a GT 710 that is basically only good for video out. My problem now is that this piece of shit won't let me access the web UI or ping it anymore. It boots and gets the IP address I have assigned to it in the console, but I can't ping it or access the web UI anymore. I can even log into the console, but have no idea what to do to make the web UI accessible. What the hell is going on with this thing? EDIT: I can access the webUI and ping it ONLY when I go into safe mode. My guess is this has something to do with the version of Nvidia driver being incompatible with my GT 710. But now I can't disable it/downgrade it in safe mode. What the heck am I supposed to do?

Are you transcoding 1080p or 4K with it? I'm transcoding 4K, and I could have up to 3 streams at once, but usually just 1 or 2. I was hoping to have something that could handle that, and have room to grow as I share with more and more people. From what I can find through searching, it looks like the GTX 1660 may be the most comparable non-Pascal card to the P2000. So, I may just go with it seeing as I'm having bad luck with the Pascal card. EDIT: Well, never mind. That card requires doing something that I'm not even allowed to talk about on here, and can't find through simple searching. At this point I'm ready to just shut it down and sell it for parts.

What is the recommended card? My logic of buying the top of the line card was obviously wrong because the P2200 didn't last 2 years. I would expect to get 4+ years out of a $400 card at the very least.

So, as a test, I switched out the P2200 for a spare GT 710 I had lying around. I'm able to get it load all the way to the log in screen with this card, but oddly, it doesn't show up in the Nvidia plug-in: It does show in my IOMMU groups though: Why wouldn't it show in the Nvidia plugin? Diagnostics attached. It's really odd that everything was working with the P2200, except the login screen, but with the GT 710, it's the complete opposite. diagnostics-20221106-1324.zip

Hmm, alright. It is a Supermicro X9DRL-iF, which does have IPMI and a VGA port for displaying video, but I have the BIOS set to the PCI slot the GPU is in for video output because the VGA port wouldn't work before. I can try switching the BIOS to the VGA port and seeing if it works now instead of the GPU...

That makes sense. No, I just have the BIOS set to the PCI slot the GPU is in for video output. I'm starting to wonder if this is an issue with 6.11.1 itself, instead of the driver, and if I should try posting in the release thread for it with details of my issue since upgrading.

Sorry, I edited my original post to include that Plex has zero issues transcoding with this card, except for the distorted screen that's connected to the GPU (worked before 6.11.1). I can have multiple 4K transcode streams running simultaneously, and they work great. I bought the card in 01/2021. I tried shutting down the server, reseating the card and booting back up, but got the exact same issue as before. So, I tried downgrading from "latest" to "production branch" in Nvidia Driver Settings, and rebooted. This time it gets a little further in the loading process, and it stops at a different error. Does this help indicate anything else? I also attached another copy of Diagnostics using the new driver. diagnostics-20221019-1118.zip Loading screen stops here with "production branch" driver:

Diagnostics attached. diagnostics-20221019-0140.zip That would suck since it's not even 2 years old, and worked fine up until upgrading to 6.11.1 tonight. I don't have another machine I can test it with, but I can at least try shutting down the server and reseating it in the slot. It also has no issues displaying anything up until the point where it says it's mounting the disks. BIOS displays fine, etc. It also transcodes 4K just fine in Plex. It's only the Unraid console that just freezes and stops loading at boot.

I know this sounds trivial, but I just updated to 6.11.1 and I'm no longer able to use my GPU (P2200) to display my Unraid console on a screen and for Plex transcoding simultaneously. It worked previously in 6.10.3, and versions before that. After upgrading, I noticed that the text displayed while booting would stop at the point of mounting the disks (screenshot below). Before upgrading, it would load all the way to the prompt to enter login credentials, and I could always wake the screen to login through the console. I also noticed after upgrading, if I started a transcode in Plex, the connected screen becomes distorted (screenshot below). I tried reinstalling the driver and rebooting, but the issue still remains. The GPU isn't being used by anything else and it's not stubbed at boot. It's only used for transcoding in Plex and displaying the Unraid console on a screen. I'm not sure what else to do to get this working like before. Any help is greatly appreciated. Connected screen stops here at boot: Connected screen after starting transcode in Plex: Nvidia Plugin: Syslinux config:

Mapping the cert files from Swag fixed it! Thank you! Yes! See the above post to map the cert files. That worked for me just now. Although, I'm using Swag, which uses a different path for the files: /mnt/user/appdata/swag/keys/letsencrypt/ instead of: /mnt/user/appdata/NginxProxyManager/letsencrypt/live/npm-33/

As another troubleshooting step, I completely started over from scratch by changing the data directory and setting everything back up. However, I still have the issue with emails going straight to quarantine, and the sender being added to the karma records. I can send emails without issues. All of the connection diagnostics pass as well. I'm not sure what else to try at this point.