orlando500

Members
  • Posts

    208
  • Joined

  • Last visited

Everything posted by orlando500

  1. thanks.. i just updated again to a new build of delugevpn and vollah. everything worked again without changing a bit...
  2. Nah i dont have not done any special bindings. Just read that you had to put localhost there after the update. Before that i had the ip of the server 192.168.10.20 as i have in sonarr. But radarr didnt work so tried localhost. But same result.
  3. Im having problems with binhex-radarr connection to binhex-delugevpn for downloads. binhex-sonarr with setup like this is working: @binhex any clues where i should start checking?
  4. ah thanks.. yes i was using the binhex-delugevpn with proxy functions. And had it on radarr. Have not been in the forums for a week so have not gotten the memo :-) guess i should read up before upgrading.
  5. [SOLVED] thanks Cessquill hi, i upgraded to 3.0.2.4552 of radarr (binhex version) but after a reboot radarr says all my download clients are unavailable. [v3.0.2.4552] NzbDrone.Core.Download.Clients.DownloadClientUnavailableException: Unable to connect to Deluge, please check your settings ---> System.Net.WebException: The operation has timed out.: 'http://192.168.10.20:8112/json' ---> System.Net.WebException: The operation has timed out. Strange as it uses same setup as sonarr and have been working with the same config. Any pointers? EDIT: seems radarr is also refusing incomming api calls... have not changed that either... strange
  6. Hi, thanks for the fast reply. Maybe in a bit slow here to night but where do i flash the card from...? guess you add some menu items somewhere but cant seem to find them.
  7. hi, im late to the party, but i got my self a couple of Mellanox 10G cards and a 10G spf+ switch. I installed the mellonox plugin but that only shows info on the card: Info:FW Version: 2.42.5000 FW Release Date: 5.9.2017 Product Version: 02.42.50.00 Rom Info: type=PXE version=3.4.752 Device ID: 4099 Description: Node Port1 Port2 Sys image GUIDs: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 MACs: 0002c9382cd0 0002c9382cd1 VSD: PSID: MT_1170110023 and a link here to this thread... am i missing something on the firmware tool side?
  8. After updates to my binhex dockers i get [54da0c7] Unknown exception in url **api Error: Not supported proxy scheme in medusa. is this a proxy or a medusa problem? edit: solved my self. seems the new version of medusa needs http:// in front of ip adress of the proxy. Was not needed until this release.
  9. i get 107 mb/s with sabnzb, i use multible server providers to get enough speed set to balance. i have 1gb/1gb fiber.
  10. Hi, thanks for this great docker. in use every day :-) I was looking for a way to handle downloads that failed. and it seems nzbtomedia is the way to go. Is there anyway that nzbtomedia can be a part for the docker as default?
  11. I added ncp-disable to the config file after looking at the info at https://www.privateinternetaccess.com/helpdesk/kb/articles/what-s-the-difference-between-aes-cbc-and-aes-gcm and then it connected without errors...
  12. I added ncp-disable to the config file after looking at the info at https://www.privateinternetaccess.com/helpdesk/kb/articles/what-s-the-difference-between-aes-cbc-and-aes-gcm and then it connected without errors...
  13. tried that, same error. Did remove it because binhex said i should be removed in another post here.
  14. Still got the message : 020-11-03 00:09:23,774 DEBG 'start-script' stdout output: 2020-11-03 00:09:23 OPTIONS ERROR: failed to negotiate cipher with server. Add the server's cipher ('BF-CBC') to --data-ciphers (currently 'AES-256-GCM:AES-128-GCM') if you want to connect to this server. 2020-11-03 00:09:23 ERROR: Failed to apply push options 2020-11-03 00:09:23 Failed to open tun/tap interface 2020-11-03 00:09:23 SIGHUP[soft,process-push-msg-failed] received, process restarting when using this opvn file client dev tun proto udp remote no.privacy.network 1198 resolv-retry infinite nobind persist-key data-ciphers-fallback aes-256-gcm auth sha1 tls-client remote-cert-tls server auth-user-pass credentials.conf compress verb 1 <crl-verify> Have copied in new .perm and cert in from newly downloaded zip file. Have tried 4 different ovpn files, and have used notepad++ to edit. what are im doing wrong @binhex ?
  15. Edit: Updated to new docker with 1.20.2.3370 public version and it seems to work for me again. Is there a bug in the version in current image? Server Version#: 1.20.2.3343 Player Version#: 8.6.0.20351 (shield pro version 8.2.0 (32.6.435.1) When going into the plex client on the shield today i noticed that my last added movies was gone. I have done no changes to the config and have been the same for months. I tried to add the last added movies to the home screen again. didnt happen. did it again with some others sections i could add. Then tok a reset of the shield. Same error. Then i did a reset in plex client and did go auto mode for homescreen. All sections ok. Did go back to manual setup. Tried to remove plex shows etc that i dont use. It then removes all my “my added tv shows” and “just added movies” sections from the client. See video https://youtu.be/MwFppBkckDY Anyone else have this?
  16. ok i will do that also. never had this error before and the syslog as far as i can see (limited) it says something about memory.
  17. Hi, the Fix Common Problems plugin found that i had a hardware problem. Im not sure but it seems its the memory? Can someone confirm this for me? how can i tell wich module it is? I have attached the diag file with mcelog included. hal-diagnostics-20200920-0954.zip
  18. run into the same problem with this message filling up the log
  19. Hi, have anyone had this problem? i run the lastest build of the docker and it seems deluge is falling asleep somehow. or something under the hood. Medusa adds torrents to deluge. But its not starting the download and dont show any peers. Its like the network has gone idle. When restarting the docker everything is back to normal. No errors in the docker logs.
  20. yeah after they upgraded i seem to have some issues connection tru that node. When got home.. the deluge seems unresponsive and have not started downloads in que. Got a lot of this when restarting docker: 2020-08-13 16:17:43,212 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 11 retries left [info] Retrying in 10 secs... 2020-08-13 16:17:53,289 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 10 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:03,548 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 9 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:13,630 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 8 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:13,630 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 8 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:23,723 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 7 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:33,810 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 6 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:43,955 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 5 retries left [info] Retrying in 10 secs... 2020-08-13 16:18:54,043 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 4 retries left [info] Retrying in 10 secs...