saarg

You were the one that said you passed it through to a VM. I assume you removed the VM template then. Have you rebooted after you remove the VM template? If you haven't rebooted, do so and post the output of lspci -k. If you have rebooted, still post the output of of the above command.

Is it chosen in the VM template? If so, unraid automatically binds the GPU to vfio so the Nvidia diver can't be used.

It's there. Click here (in the first post). For upgrading the Nextcloud version, please see this guide here.

Tested it here and it's the same. Most likely a bug in calibre-web.

The problem is that you are passing it through your a vm. That means the nvidia driver is not loaded, and the plugin doesn't see the card.

And here I finally thought I knew a little bit of nginx and you implement a new thing crushing my nginx selfesteem! 😛

You have tried to update using both command line and webgui? Did you install the latest v17 before going to v18? Regarding exporting users, you have to check the nextcloud documentation.

You have to set the IP and port in the proxy-pass line instead of the variable. So if there is already a proxy-conf you can use, just edit that one.

Does it say in the logs why it failed?

I didn't see the user part. The users are stored in the database. I have no idea if it's possible to export the users and import it again. If you have it still working, why do you need to set it up again?

He hasn't set the correct permissons for root. Root is a user after all.

Look at the previous page. Hint: occ files:scan

Did you add the variable to add the binary? -e DOCKER_MODS=linuxserver/calibre-web:calibre

You haven't set the permissions for the user correctly. Google for the correct command to allow access.

That is something we don't support. Use local storage for the /config mounts.

The command is executed from your host, so it is complete in the readme. The only thing you have to substitute is which grabber you configure. You need to do docker exec using the -u abc part or else you configure it as root and you will get permission problems.

You are doing it wrong. You use the grabber in tvheadend to grab the info from xmltv.se. In the readme at GitHub linked in the first post, you have the info for configuring the xmltv grabber. Use the Norway xmltv address when it asks for it. Use the Swedish grabber in tvheadend as it works for Norwegian channels also. I used it for years.

You can't as we only use the latest driver at the time of building the new build.

Be sure to update the container and also nextcloud. I just tested it here and had no problems adding 2 shares using smb/cifs. I had to update Nextcloud though, as I was still on 17.0.1 and smb/cifs refused to work on that version. You do not have to fill out the field above domain (Ekstern undermappe på norsk). This might be your issue as it tries to use a folder under yourserver\share\ which fails. I think that you mistook this as the place to mount the smb/cifs share inside the container, which is not the case. Why are you trying to run docker exec -it name nextcloud config?

Check the link to the manual update procedure in the first post of this thread for the correct path to occ.

It's yourself that you should be saying sorry to 😉

The plugin doesn't query the gpu. Getting the UUID is done once at boot and that is all. I don't think there is much we can do about the issue as it's most likely a combination of kernel, driver, GPU and bios versions. Hopefully it's solved in a later build.

Permissions looks correct from what you have posted. Only the top one _gsdata is wrong. Don't run commands from another container as that is a sure way to make problems. Remove those from your template. We chmod the /data mount to the correct user and group on start, so restart the container and permissions should be correct. You might have done something to the files inside the container also, so do a force update on the container to set it back to normal.

Have you read the Readme on Github? https://github.com/linuxserver/docker-calibre-web

You can remove the CONTEXT_PATH variable and you don't have to use /airsonic. I don't know why it was set like that when the template was made. Probably to use it in subfolder reverse proxy. You also have to remove the template address so the CONTEXT_PATH field isn't reset each time you update the container. That is a "feature" in the docker implementation in unraid. If I remember correctly you have to enable authoring mode to remove the template address. I have to check if we can remove it now and not affect current users.