Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

mbc0

Members
  • Joined

  • Last visited

Everything posted by mbc0

  1. Is this unsupported now? :-( will the plugin work instead?
  2. Ok, Complete re-install now running on SSD as well same problem! just a black screen This worked perfectly for me on V5
  3. uninstalled & re-installed another 20 times or so today to try and get this working! Any pointers on diagnosing this please? Many thanks This is at the end of my logfile, any ideas? [10.18.16 00:52:48.097 INFO ystemWatcher p42.service.peer.CPCConnectCheck] Connect to CPC after 0ms [10.18.16 00:52:48.206 INFO ystemWatcher up42.service.peer.PeerController] Attempting to connect to CPC. delay=60000 [10.18.16 00:52:48.461 INFO e-listen-1-1 .handler.ChannelExceptionHandler] SABRE:: Uncaught IOException in channel pipeline! msg=not an SSL/TLS record: 8063000000412d31383738327c636f6d2e636f646534322e6d6573736167696e672e736563757269747$ [10.18.16 00:52:48.465 WARN e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x2f47079b, L:/192.168.0.33:58800 ! R:/216.17.8.52:443] [10.18.16 00:52:48.469 INFO e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x2f47079b, L:/192.168.0.33:58800 ! R:/216.17.8.52:443]), remotePeer=$ [10.18.16 00:52:48.470 INFO e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.52:443. connectFuture.isDone=true, channel=[id: 0x2f47079b, L:/192.168.0.33:58800 ! R:/216.17.8.52:443] [10.18.16 00:52:50.398 WARN e-listen-1-2 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x4b0e7874, L:0.0.0.0/0.0.0.0:33562 ! R:/216.17.8.51:443] [10.18.16 00:52:50.399 INFO e-listen-1-2 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x4b0e7874, L:0.0.0.0/0.0.0.0:33562 ! R:/216.17.8.51:443]), remotePee$ [10.18.16 00:52:50.399 INFO e-listen-1-2 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.51:443. connectFuture.isDone=true, channel=[id: 0x4b0e7874, L:0.0.0.0/0.0.0.0:33562 ! R:/216.17.8.51:443] [10.18.16 00:52:52.399 WARN e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x7d69e29b, L:0.0.0.0/0.0.0.0:51224 ! R:/216.17.8.48:443] [10.18.16 00:52:52.400 INFO e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x7d69e29b, L:0.0.0.0/0.0.0.0:51224 ! R:/216.17.8.48:443]), remotePee$ [10.18.16 00:52:52.400 INFO e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.48:443. connectFuture.isDone=true, channel=[id: 0x7d69e29b, L:0.0.0.0/0.0.0.0:51224 ! R:/216.17.8.48:443] [10.18.16 00:52:54.396 INFO e-listen-1-2 .handler.ChannelExceptionHandler] SABRE:: Uncaught IOException in channel pipeline! msg=not an SSL/TLS record: 8063000000412d31383738327c636f6d2e636f646534322e6d6573736167696e672e736563757269747$ [10.18.16 00:52:54.397 WARN e-listen-1-2 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0xa008bf2f, L:/192.168.0.33:52478 ! R:/216.17.8.47:443] [10.18.16 00:52:54.398 INFO e-listen-1-2 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0xa008bf2f, L:/192.168.0.33:52478 ! R:/216.17.8.47:443]), remotePeer=$ [10.18.16 00:52:54.398 INFO e-listen-1-2 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.47:443. connectFuture.isDone=true, channel=[id: 0xa008bf2f, L:/192.168.0.33:52478 ! R:/216.17.8.47:443] [10.18.16 00:52:56.398 WARN e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x49f272c8, L:0.0.0.0/0.0.0.0:46166 ! R:/216.17.8.11:443] [10.18.16 00:52:56.399 INFO e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x49f272c8, L:0.0.0.0/0.0.0.0:46166 ! R:/216.17.8.11:443]), remotePee$ [10.18.16 00:52:56.399 INFO e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.11:443. connectFuture.isDone=true, channel=[id: 0x49f272c8, L:0.0.0.0/0.0.0.0:46166 ! R:/216.17.8.11:443] [10.18.16 00:52:58.401 INFO e-listen-1-2 .handler.ChannelExceptionHandler] SABRE:: Uncaught IOException in channel pipeline! msg=not an SSL/TLS record: 8063000000412d31383738327c636f6d2e636f646534322e6d6573736167696e672e736563757269747$ [10.18.16 00:52:58.402 WARN e-listen-1-2 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0xbed47c54, L:/192.168.0.33:58750 ! R:/216.17.8.8:443] [10.18.16 00:52:58.403 INFO e-listen-1-2 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0xbed47c54, L:/192.168.0.33:58750 ! R:/216.17.8.8:443]), remotePeer=R$ [10.18.16 00:52:58.403 INFO e-listen-1-2 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.8:443. connectFuture.isDone=true, channel=[id: 0xbed47c54, L:/192.168.0.33:58750 ! R:/216.17.8.8:443] [10.18.16 00:53:00.402 INFO e-listen-1-1 .handler.ChannelExceptionHandler] SABRE:: Uncaught IOException in channel pipeline! msg=not an SSL/TLS record: 8063000000412d31383738327c636f6d2e636f646534322e6d6573736167696e672e736563757269747$ [10.18.16 00:53:00.403 WARN e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x41e0ba7b, L:/192.168.0.33:60626 ! R:/216.17.8.7:443] [10.18.16 00:53:00.403 INFO e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x41e0ba7b, L:/192.168.0.33:60626 ! R:/216.17.8.7:443]), remotePeer=R$ [10.18.16 00:53:00.403 INFO e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.7:443. connectFuture.isDone=true, channel=[id: 0x41e0ba7b, L:/192.168.0.33:60626 ! R:/216.17.8.7:443] [10.18.16 00:53:02.405 WARN e-listen-1-2 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0xf8f32dcb, L:0.0.0.0/0.0.0.0:37998 ! R:/216.17.8.4:443] [10.18.16 00:53:02.405 INFO e-listen-1-2 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0xf8f32dcb, L:0.0.0.0/0.0.0.0:37998 ! R:/216.17.8.4:443]), remotePeer$ [10.18.16 00:53:02.406 INFO e-listen-1-2 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.4:443. connectFuture.isDone=true, channel=[id: 0xf8f32dcb, L:0.0.0.0/0.0.0.0:37998 ! R:/216.17.8.4:443] [10.18.16 00:53:04.398 WARN e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x73494c8f, L:0.0.0.0/0.0.0.0:53298 ! R:/216.17.8.3:443] [10.18.16 00:53:04.399 INFO e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x73494c8f, L:0.0.0.0/0.0.0.0:53298 ! R:/216.17.8.3:443]), remotePeer$ [10.18.16 00:53:04.399 INFO e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.3:443. connectFuture.isDone=true, channel=[id: 0x73494c8f, L:0.0.0.0/0.0.0.0:53298 ! R:/216.17.8.3:443] [10.18.16 00:53:06.401 INFO e-listen-1-2 .handler.ChannelExceptionHandler] SABRE:: Uncaught IOException in channel pipeline! msg=not an SSL/TLS record: 8063000000412d31383738327c636f6d2e636f646534322e6d6573736167696e672e736563757269747$ [10.18.16 00:53:06.402 WARN e-listen-1-2 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x41ed03b6, L:/192.168.0.33:33128 ! R:/216.17.8.55:443] [10.18.16 00:53:06.403 INFO e-listen-1-2 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x41ed03b6, L:/192.168.0.33:33128 ! R:/216.17.8.55:443]), remotePeer=$ [10.18.16 00:53:06.403 INFO e-listen-1-2 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at /216.17.8.55:443. connectFuture.isDone=true, channel=[id: 0x41ed03b6, L:/192.168.0.33:33128 ! R:/216.17.8.55:443] [10.18.16 00:53:08.404 WARN e-listen-1-1 handler.AppProtocolStartListener] SABRE:: Channel failed to reach state for app protocol start. channel=[id: 0x8ba8b158, L:0.0.0.0/0.0.0.0:33130 ! R:central.crashplan.com/216.17.8.55:443] [10.18.16 00:53:08.405 INFO e-listen-1-1 .handler.ChannelLifecycleHandler] SABRE:: Channel became inactive. ctx=ChannelHandlerContext(CHANNEL_LIFECYCLE_HANDLER, [id: 0x8ba8b158, L:0.0.0.0/0.0.0.0:33130 ! R:central.crashplan.com/216.17.$ [10.18.16 00:53:08.405 INFO e-listen-1-1 .network.sabre.SabreNetworkLayer] SABRE:: Cancelling connect to 42 at central.crashplan.com/216.17.8.55:443. connectFuture.isDone=true, channel=[id: 0x8ba8b158, L:0.0.0.0/0.0.0.0:33130 ! R:centr$ [10.18.16 00:53:11.580 INFO MQ-Peer-0 saging.security.SecurityProvider] SP:: Session secured in 707 ms. RemotePeer-[guid=42, SERVER]; PeerConnectionState-[state=CONNECTING, mode=PRIVATE, currentAddressIndex=0, layer=2/2(Peer::NIO), $ [10.18.16 00:53:12.033 INFO MQ-Peer-2 ervice.peer.PeerVersionValidator] WE have an old version, localVersion=1435813200480 (2015-07-02T05:00:00:480+0000), remoteVersion=1460005200540 (2016-04-07T05:00:00:540+0000), remoteGuid=42 [10.18.16 00:53:12.131 INFO ystemWatcher up42.service.peer.PeerController] Connected to CPC after 23sec
  4. uninstalled & re-installed another 20 times or so today to try and get this working! Any pointers on diagnosing this please? Many thanks
  5. No amount of uninstalling/reinstalling will get rid of this black screen! Have tried all suggestions in this thread but constant black screen! :'(
  6. Hi, Just wondering if anyone can help me please? I have an I5 unRAID with 12GB RAM & 12TB Of Space and am using this docker to backup online and to my HP Microserver. I am currently just backing up to my Microserver on a 1GB LAN and get great speeds when backing up but the analyzing is killing my CPU (Java at 110% ish) and will take weeks! The problem actually seems to be MP3 files, I am seeing that crashplan will analyse a 4GB MKV in about the same time as it takes to do an MP3? I have 50,000 MP3's and it is taking approx 45 seconds to analyze each one? can anyone tell me if this is normal or what I can do to speed this up? Many Thanks
  7. Just in case anyone else encounters this... it is the same for Sonarr as well as Headphones, they use the Webui port and not the daemon port like couchpotato :-)
  8. Has anyone been successful in using this with headphones? here is the debug log I am getting... 2016-07-02 18:22:06 DEBUG Deluge: Connection failed, let's try HTTPS just in case 2016-07-02 18:22:06 DEBUG Deluge: FYI no SSL certificate configured 2016-07-02 18:22:06 DEBUG Deluge: Using password M******0 2016-07-02 18:22:06 DEBUG Deluge: Authenticating... 2016-07-02 18:22:06 DEBUG Deluge: addTorrent Authentication 2016-07-02 18:22:06 INFO Sending torrent to Deluge
  9. Many thanks jonathanm, after looking through the logs I found that there was a problem with ca.crt I re-downloaded the file and everything is working perfectly! I have now apparently moved from the UK to the Netherlands :-) Thanks very very much to you and everyone that chimed in to help with this :-)
  10. Hi, yes it is :-) trying to find a log that may help! any pointers?
  11. Great to have this running now, thanks very much! I just have a problem with it not working lol! Deluge is now running but my IP is still showing my WAN address (tested with the checkmytorrentip) is the ip for LAN_NETWORK - Internal LAN network (see Q7. for details)supposed to be the unRAID IP or the Docker IP? I have tried both but still my IP is shown? Thanks again :-)
  12. ah FFS! Thanks matey
  13. Notes For help on configuration for PIA, AirVPN and custom VPN providers please go here http://lime-technology.com/forum/index.php?topic=45812.msg437678#msg437678 IMPORTANT - To allow access to the Deluge webui, Privoxy and Deluge deamon you need to specify you LAN network, using CIDR notation for the mask, a subnet mask of 255.255.255.0 would equate to CIDR /24, 255.255.0.0 would equate to CIDR /16. Hi, I cannot find where to define these values? Do I type out the credentials.conf to look like the above? I can find this information everywhere on how to setup but can find anywhere that tells me where to enter the config?
  14. Ah, that will be why then jonathanm, I presumed that deluge would have started so I can begin configuration... is there an installation/setup guide anywhere? I can only find advanced settings....
  15. Thanks for the replies, I have changed appdata/delugevpn for full access, restarted but still no joy, as for the IP that is the IP of my unRAID server...
  16. Hi All, Am I missing something obvious here? I cannot even get going? I have installed the docker but cannot connect to the WEBUI? I just get This site can’t be reached 192.168.0.33 refused to connect. I have tried uninstalling & reinstalling
  17. Hi all, Is there an "easy" guide for this at all please? so far I have installed the container openvpn-as apt-get easy-rsa but now stuck with this error? root@UNRAIDSERVER:/usr/share/easy-rsa# ssh build-ca ssh: connect to host build-ca port 22: Connection timed out Many Thanks in advance!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.