binhex

Community Developer
  • Posts

    7899
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by binhex

  1. what version is the restore CD?, i see from the Restore CD changelog some mention about fixes to the restore images process:- https://www.urbackup.org/restore_changelog.html link to latest:- https://hndl.urbackup.org/Restore/urbackup_restore_2.4.2.iso
  2. see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
  3. Your VPN providers cert is broken, download the latest cert Sent from my 22021211RG using Tapatalk
  4. this is sadly an unraid bug, lots of people have mentioned permissions issues when upgrading, weirdly it doesnt happen to everybody (i was lucky). best thing to do to reset permissions is this:- 1. stop container 2. delete file /config/perms.txt 3. start container note startup time maybe a little slower than normal but this is a one off.
  5. i have just pulled down the latest image with a blank config and it fired straight up, no issues, i also do not see any sign of traceback in the logs, so unless somebody can tell me how to replicate the issue then its going to be a tough one to fix!. it might be worth posting your issue on the sabnzbd github repo:- https://github.com/sabnzbd/sabnzbd/issues
  6. Your issue is:- 2022-11-10 06:50:43 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) I suspect out of date config file and/or cert, download from your VPN provider. Sent from my 22021211RG using Tapatalk
  7. Overview: Support for Docker image arch-goland in the binhex repo. Application: GoLand - https://www.jetbrains.com/go/ Docker Hub: https://hub.docker.com/r/binhex/arch-goland/ GitHub: https://github.com/binhex/arch-goland Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer 😁 For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here
  8. yeah this is where you are going wrong, this image is not meant to be driven from the rclone cli, once the rclone config has been generated then all config should be done through the env vars e.g. 'RCLONE_OPERATION', 'RCLONE_DIRECTION' etc . If you do want to do custom operations with rclone then i would recommend using the rclone plugin instead - https://forums.unraid.net/topic/51633-plugin-rclone/ if however you do want to proceed with using the rclone cli inside of the container (no support) then you can do what you want by simply using the config option flag and passing it to rclone, e.g.:- --config=/config/rclone/config/rclone.conf
  9. ok you need to go to unraid webui/docker/ left click rclone and then click at the bottom ' Show more settings ...' this will then show you the host path for /config, so its probably somethng like /mnt/user/appdata/binhex-rclone so then go to windows explorer and look for a share named appdata, if its not shown then enable smb for the share.
  10. it doesnt need to be transferred, the rclone cli is set to use whatever path is specified for RCLONE_CONFIG_PATH which in your case is /config/rclone/config/rclone.conf
  11. if you have a cache drive then change the path for /config from /mnt/user/appdata/plex/ to /mnt/cache/appdata/plex/, reason being that for a long time (maybe fixed recently i honestly dont know!) there has been an issue when targeting /mnt/user which can cause apps to crash and even bring down the entire array, i personally always target the cache drive directly as opposed to /mnt/user/ def worth a try!. if that doesnt fix it then the next culprit would be memory, boot to MemTest and run it for AT LEAST 12 hours, ensure there are no errors.
  12. set the first path like so:- then set RCLONE_MEDIA_SHARES as follows:- also please ensure that RCLONE_REMOTE_NAME does indeed match the remote name defined in your rclone config file, including CaSe
  13. i think what is going on is a incompatible change to the config file in deluge, try the following:- 1. stop container 2. rename /config/deluge/core.conf to core.conf.old 3. start container 4. reconfigure deluge via web ui.
  14. highly unlikely a rollback will fix it, but here ya go Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  15. Well it's not lying there is no remote line in that config file, redownload the openvpn config from your VPN provider Sent from my 22021211RG using Tapatalk
  16. You don't need to it's already fixed just pull the latest image Sent from my 22021211RG using Tapatalk
  17. correct, and that was what i was personally using so i wasnt seeing the issue until i switched to wireguard.
  18. arghh you guys got me out of my weekend slumber! :-). ok it looks like arch linux in their wisdom ripped out crypto support which wireguard relies on, here is a post about it and the suggested fix, which ive now tested and confirmed working:- https://unix.stackexchange.com/questions/723616/how-to-fix-missing-libcrypto-so-1-1 fix is now in, please pull down the image at your next convenience, now where's my coffee cup? [emoji846]
  19. simple, the cert and/or openvpn config file is out of date, your vpn provider has changed something and the old config/cert file is no longer valid, it happens a lot.
  20. either by re-creating the the container from scratch, this will pickup all changes from the template (obviously not ideal), or viewing the github readme linked in the first post of this thread.
  21. also change your dns, i see you are using the older name servers which includes the flaky PIA name servers (209.222.x.x) which maybe causing the intermittent lookup failure, the default list of NAME_SERVERS should now be set as:- 84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
  22. you dont update like you, you do it through the unraid web ui, go to docker tab, click on 'check for updates' you should then see an update available for get_iplayer and should be able to update it by clicking on update all.
  23. It's ready now Sent from my 22021211RG using Tapatalk
  24. atomicparsley path now hard set in the latest image, please pull down image. all fixed up in the latest image please pull down, thanks for the screenshot.