saarg

Community Developer
  • Posts

    5374
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by saarg

  1. No, the settings file for Gitlab. Check the documentation of Gitlab to find the correct file. The one you mention is for reverse proxy and doesnt have anything to do with changing the ports to access Gitlab. You do need to adjust the proxy config if you reverse proxy Gitlab.
  2. Not sure if those cards are still supported by the driver. You also need to install the nvidia plugin and download the nvidia build. For the driver to work, you have to remove the blacklisting so the driver can load.
  3. Not correct. You need to let the container run and it will renew it before it expires. It attempt to renew every night at about 2. When is your cert expiring?
  4. You only changed the port mappings. Gitlab itself doesn't know about those mappings. When you set an IP for the container, the port mappings are obsolete and will be the ones set in the container (Which is the container ports in the template). So to change these to the standard http/https/ssh ports, you need to change the settings file in gitlab.
  5. It's not by default in the template. You can easily add it yourself. The Readme on github is the reference for the correct syntax.
  6. Did you upgrade unraid? Sounds like you upgraded to the normal build and not using the nvidia plugin to download the nvidia build.
  7. Read the link about updating in the first post.
  8. If the share setting is secure, that might be the issue. You have different layers of permissions, from the host to the VM, then the user running nextcloud. You have to make sure both the VM and the user running Nextcloud have write permissions. Can you write being root in the VM? Can you write being the user running nextcloud in the VM?
  9. Probably the permissions on the host side then.
  10. There should be a command somewhere in this thread you could issue to check if the card is working. It was posted by chbmb a few pages back I think. You did download the nvidia build using the plugin? Or did you just install the plugin?
  11. What do you mean by usb pass through the vpn? Do you mean that you want to pass through a usb network adapter to the container?
  12. Not wget. Open the link you posted in a normal browser and you can see all the releases. Then add the correct filename to the link and follow the guide.
  13. Try using /mnt/cache/ or /mnt/diskX/ instead of /mnt/user/ for the app appdata path. Also, please don't restart the application, restart the container. It's the same developer for this as the old version you used.
  14. You should be able to browse for the different versions if you remove the last part of the link.
  15. You can't use the stubbing method you used as all your USB controllers have the same ID. So you need to look at the new method of stubbing using the PCI ID. I don't remember which release it was added, but go through the release announcements to find it. Might have been 6.8, but might have been in one of the 6.7 releases.
  16. The reason is that you have your unraid usb on the same usb controllers that you use vfio-pci.ids on.
  17. Nextcloud was nice enough to include a binary that is glibc only. Since we use alpine and that is musl based, it will not work in our container. They also don't have any arm versions of the binary either as far as I know.
  18. This is basic docker stuff. I suggest you read the docker faq to learn about the basics of docker. /config inside the container is the appdata folder on the host side (unraid). So /config/cache inside the container is /whatever_you_mapped_as_appdatafolder/cache on Unraid. Probably /mnt/cache/appdata/jellyfin/
  19. That depends on what you want with you from the old setup. Of you want the watched status and all settings, then copy the appdata from the old container. If you don't mind setting all settings again and either don't care about watched status or use trakt to sync it (if there is plugin for plex), then start fresh.
  20. Which problem are you referring to? if it's the issue with the onlyoffice or what the name of the new built in stuff is, then the problem is nextcloud as they just slapped on a static built binary that is only usable on glibc systems and isn't arm compatible either. So not much we can do about it. I don't know what the Nextcloud guys was thinking when they did that.
  21. You need to post the docker run command so we can see which folder you are mapping. With the info you posted, we can only guess.
  22. Try to run this command and see if it works after that. docker exec -it ddclient chown abc:abc /ddclient.conf For some reason the config file is owned by root. Have to check if that is something we did.