saarg

Fresh install, so the appdata folder was never used before? If that is the case, then you might need to update your reverse proxy conf. Delete the nextcloud sample and restart letsencrypt. That will restore the newest sample. Then edit the sample as instructed at the top of the file, save it and delete the old proxy conf file. Then remove the sample part from the filename and restart letsencrypt.

I don't think there should be any issues if it's a dell p400. Running the card in 8x gen2 shoudln't be an issue as far as I know.

1. Your bios is very old. You have 1.8.2 (From 2011) and the newest is 1.13.0 (2018). 2. You have this error in the syslog about the P400. pci 0000:04:00.0: can't claim BAR 3 [mem 0xbe000000-0xbfffffff 64bit pref]: no compatible bridge window kernel: pci 0000:04:00.0: BAR 3: no space for [mem size 0x02000000 64bit pref] kernel: pci 0000:04:00.0: BAR 3: trying firmware assignment [mem 0xbe000000-0xbfffffff 64bit pref] kernel: pci 0000:04:00.0: BAR 3: [mem 0xbe000000-0xbfffffff 64bit pref] conflicts with System RAM [mem 0x00100000-0xbf698fff] kernel: pci 0000:04:00.0: BAR 3: failed to assign [mem size 0x02000000 64bit pref] 3. You got the below lines in your syslog, which I don't have. Might be different revisions of the card or that your's a Dell card? kernel: nvidia: loading out-of-tree module taints kernel. kernel: nvidia: module license 'NVIDIA' taints kernel. 4. It seems it's a different GPU ID also. Yours is [drm] [nvidia-drm] [GPU ID 0x00000400] Loading driver And mine is [drm] [nvidia-drm] [GPU ID 0x00008200] Loading driver 5. You have the below when the plugin is installed, so there is something going on. Hardware/bios issue is my guess. kernel: resource sanity check: requesting [mem 0xdd700000-0xde6fffff], which spans more than PCI Bus 0000:04 [mem 0xdc000000-0xddffffff] kernel: caller _nv030928rm+0x5d/0xd0 [nvidia] mapping multiple BARs kernel: NVRM: GPU 0000:04:00.0: RmInitAdapter failed! (0x26:0xffff:1227) kernel: NVRM: GPU 0000:04:00.0: rm_init_adapter failed, device minor number 0 So try to update your bios and see if that works.

I'm sorry we have a life outside of linuxserver.

I'd you try to delete it and toe it in manually? You might not see that there is a space. There is a bug that makes the same issue when copy pasting from the forum and typing it manually works.

It looks like you have some empty spaces at the end of the UUID.

I'm talking about the settings in letsencrypt and not port forwarding. I don't know how spaceinvader tells you to set it up, so you should go back and make sure you did it correctly.

Letsencrypt I would say. If you follow the readme in the proxy-confs folder and the info at the top of the proxy-conf file you use it's not hard to get it to work. You have followed some guide you found on the internet and then copy/pasted it in the various config files?

Can you post your diagnostics and I'll see if I find anything there.

I don't have a dummy or monitor plugged in, so not shure if that is the case, but it's worth a try.

Are you using gui boot?

You have configured something wrong.

You don't have to uncomment anything in the default file to get it working.

You can access it via the IP, but you will be redirected to the domain when the page loads.

When you update the container you update everything except nextcloud. So is pacakges and dependencies. Update the container first, then nextcloud.

Then I don't know what is happening. I have a p400 also, but no issues at all. Do you have anything in /dev/dri? Have you tried using an older version of unraid o see if it works there?

You are messing around with settings you don't need to change. There is no mention of changing the port in the proxy conf, so that means don't change the port! It's talking on the internal docker network, so port mapping doesn't apply. 443 is the correct port. Leave the nextcloud config at 444, as that is for accessing locally using IP. As for the default file you keep on insisting to edit, don't! There is nothing you have to comment or uncomment to make either subdomain or subfolder working.

You said you were running it on a single core VPS and I don't see how you can run unraid on a VPS as you need a usb drive for unraids license. I think letsencrypt tries to renew when it's less than 30 days before the cert expires.

If you are not using unraid, this is not the right place for support. Use our discourse or discord. Letsencrypt needs to run if the cert is to be renewed. The check is scheduled to run at night at around 2.

Didn't see it was commented out. You have created a custom network that both nextcloud and letsencrypt use, right? If so you have not followed the instructions at the top of the proxy conf. You have changed the port from 443 to 444. That is something you should not do. Change it back to 443 and restart letsencrypt.

Isn't it easier to just reverse proxy nextcloud using the letsencrypt container? That way you can have both running at the same time and you don't have to copy any certs or expose ports for nextcloud.

If I open the same folder again, it opens the files I had opened before closing the browser. I think.....

Remove the one you added. There is no need to edit anything in the default file to get proxy confs working. All you have to do is to remove the .sample part, edit the file if it is mentioned to do so in the top of the file and restart letsencrypt. Did you restart letsencrypt?

The correct modules are loaded, so it should work. Is the card recognized if you run the command nvidia-smi on the comman line? If it is, then it's just the command the plugin runs at boot to find the UUID of the card that fails for some reason. There is a command you can run to get the UUID that was posted by chbmb earlier in this thread you can try.

I even quoted you the text from the first post and where to click in that text to get to the post describing the command to update.