binhex

Community Developer
  • Posts

    7880
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by binhex

  1. i was using macvlan for one docker container, but have switched it to ipvlan now. @ich777 thanks for the pm.
  2. not necessary, see here for an explanation of the differences between plex and plex pass:- https://forums.unraid.net/topic/44142-support-binhex-plex-pass/?do=findComment&comment=433841 now onto your issue, you are missing another env var named:- NVIDIA_DRIVER_CAPABILITIES with a value of:- all that should hopefully get it working for you.
  3. As you can probably see from my list of plugins i only have the following installed from your list of commonly installed plugins, which does shorten the list quite a lot, although i am only a metric of 1 so far so take it with a large pinch of salt 🙂 community.applications.plg - 2022.09.30 (Up to date) unassigned.devices.plg - 2022.10.03 (Up to date) unassigned.devices-plus.plg - 2022.08.19 (Up to date) I am loathed to uninstall CA for obvious reasons, but i have nuked UD, so we shall see what happens.
  4. Add me to the list of users affected by this, i was running 6.9.2 without issue for months at a time, i took the plunge on release of 6.11.1 and upgraded on 10th Oct, its now 12th Oct and i have identical symptoms to this post (apart from NO hardware changes for me in years):- https://forums.unraid.net/topic/129456-unraid-kernel-crashing-after-611-upgrade/ Sadly for me, even attempting to generate diagnostics from the cli (web ui not accessible) did not complete, leaving me with no option but to attempt a soft reboot, which hung so hard reset it is. This then allowed me access to the web ui and i have dumped the list of plugins on my system (see below). hardware spec Mobo:- ASUS ROG STRIX X470-F Gaming PSU:- Seasonic SSR-750PD2 Prime Ultra 750 W CPU:- AMD 3900X RAM:- 2 x Corsair CMK32GX4M2A2666C16 (64GB) Cache (appdata/vm):- Samsung 970 EVO Plus 1 TB (NVME) Cache (downloads):- Samsung 500 GB 860 EVO GPU:- Nvidia Quadro P2000 (Plex duties) RAID Controllers:- 2 x IBM M1015 (cross flashed to IT mode) plugins installed CA Auto Turbo Write Mode Support Thread Andrew Zawadzki 2022.09.16 up-to-date CA Auto Update Applications Support Thread Andrew Zawadzki 2021.09.24 up-to-date Community ApplicationsSupport Thread Andrew Zawadzki 2022.09.30 up-to-date ** Dynamix Auto Fan Control Support Thread Bergware/gfjardim 2022.09.16 up-to-date Dynamix Cache Directories Support Thread Bergware 2020.08.03 up-to-date GPU Statistics Support Thread b3rs3rk 2022.02.22 up-to-date ** Nerd Tools Support Thread dmacias72 2021.08.11 up-to-date Nvidia Driver Support Thread ich777 2022.10.05 up-to-date ** Unassigned Devices Support Thread dlandon 2022.10.03 up-to-date ** Unassigned Devices Plus Support Thread dlandon 2022.08.19 up-to-date ** = now removed in hope of better stability. I guess i will let you know in a few days whether the system is still up or crashed again, if crashed i shall be doing a binary split on the plugins still installed.
  5. do this:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
  6. You do not need to translate the file, it looks like the cert is inline so just drop this file into /config/openvpn/ and hopefully the magic will happen, check the log file /config/supervisord.log to track progress Sent from my 22021211RG using Tapatalk
  7. nope there isnt so im at a loss as to what the credentials could be!. in any case you can get around this by shutting down the container and then editing the following file using notepad++ (not notepad!):- /config/syncthing/config/config.xml then look for a section that looks like this (not real values):- <gui enabled="true" tls="false" debugging="false"> <address>127.0.0.1:8384</address> <user>foo</user> <password>$2a$UpBCwxUqHx4f%%FDFFSD$qU9z1bObZ.LVQBtqve</password> <apikey>Yv9cbqSSDFGDSFQbqazQe575Xn</apikey> <theme>default</theme> </gui> delete the values for <user> and <password> so that it ends up looking like this:- <gui enabled="true" tls="false" debugging="false"> <address>127.0.0.1:8384</address> <user></user> <password></password> <apikey>Yv9cStziiWXz3TNRRbqSQbqazQe575Xn</apikey> <theme>default</theme> </gui> save the file, then start the container.
  8. if the issue is intermittent then i suspect the vpn endpoint you are attempting to connect to is having a bad day :-), try another endpoint and/or contact your vpn provider and tell them connectivity to that endpoint is intermittently failing.
  9. those default name servers are for any vpn provider, not just pia.
  10. no problem shown in the snippet of the log, what is the ip of the machine running the web browser and what is the value of LAN_NETWORK?
  11. see Q17 :- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  12. looks like name resolution issues. the above is what you currently have defined, try the defaults instead:- NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
  13. see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  14. interesting!, i run this myself, no such issue, ram usage currently sitting at 870MB uptime 7 days.
  15. https://github.com/binhex/documentation/blob/master/docker/guides/vpn.md
  16. sorry for the delay guys, i had an issue with my smoke test, now fixed and the image was pushed a couple of hours ago, please check and pull.
  17. sorry i dont use reverse proxy :-(, maybe try importing in smaller batches
  18. this indicates something requested that the process exits, probably due to you shutting down the container, if so there is nothing to worry about.
  19. you will have to try pulling down latest to confirm if the issue is resolved. nope.
  20. Thanks for the kind words and the beer money, much appreciated, and thanks for reading the FAQ, a lot of people don't! Sent from my 22021211RG using Tapatalk
  21. that can be ignored and is not related:- https://forums.plex.tv/t/critical-libusb-init-failed/722159
  22. simple, left click syncthing, edit something, edit it back to what it was, scroll to the bottom and click on apply, this will delete the container freeing up space.
  23. should now be fixed, please pull down latest image just built
  24. yes. open qbittorrent webui/tools/options/connection tab/listening port/Port used for incoming connections: