Techn0mancer

@snowboardjoe I get that when I use SSH and if I use the console from the docker icon I get "sh: sudo: not found"

I'm getting the following when I try to run the command

I'd really like to see a docker for Hubzilla "Hubzilla is a powerful platform for creating interconnected websites featuring a decentralized identity, communications, and permissions framework built using common webserver technology." https://project.hubzilla.org/page/hubzilla/hubzilla-project

I've been experiencing seemingly random reboots and today when it came back up, the plugin told me hardware errors were detected, to install mcelog (done) and post my diagnostics (where are these found?). Do I need to wait for the next crash to get the mcelog data?

I won't say I figured it out, but I beat my head against the keyboard until it started working

I followed the directions here http://lime-technology.com/forum/index.php?topic=53542.msg522472#msg522472 As far as I can see I didn't miss anything. I also get the same result trying to redirect myserver.com/htpcman to the HTPC Manager docker. For that I added: location ^~ /htpcman { include /config/nginx/proxy.conf; proxy_pass http://10.11.12.106:8085/htpcman; }

So eventually letsencrypt started. Now I can't get it to redirect traffic to nextcloud. I have port 443 open and I've followed, to the best of my knowledge, the configuration instructions I've found, but using nextcloud.myserver.com results in connection refused. If I try nextcloud.myserver.com:7443 (the port forwarded for nextcloud), it does connect to my server so the domain is resolving to my ip

2 things that come to mind as i also just bought a new namecheap domain and went through this yesterday: 1) You need an A + Dynamic DNS record for @ and also anything else you define. In my case that was also 'www' and 'nextcloud' 2) do you have dynamic dns setup? is that your correct WAN ip? I'm using Mace's DDClient docker to update namecheap with my IP address. I've already done point 1. As for 2, I haven't set up ddclient yet. I manually entered my WAN IP at namecheap, but I have no clue where it got 192.64.119.73

I can't get this to work at all.. It keeps killing itself. The most useful thing I see in the docker log is "Detail: Failed to connect to 192.64.119.73:443 for TLS-SNI-01 challenge" It's a domain I purchased tonight from namecheap. I have created "A + Dynamic DNS" record at namecheap pointing to my public ip address. My router is forwarding 80 and 443 to 88 and 443 as defined in the docker template. I'm just at a loss.. Has anyone else seen this error and knows how to fix it?

I started seeing the same message so I closed the port

I've had issues with accessing unRAID webui if I didn't use the --cpuset-cpus attribute to limit the cores my Plex container uses. Have you tried setting it to use all but one or two cores?

In a manner of speaking.. Althub blamed Sonarr or my settings, Sonarr seemed to expect me to set up additional software to see what was going on. Both said I was the only one reporting an issue. No one wanted to own the issue, so I had to find a new indexer. New indexer behaves as you would expect. I still believe the issue to be with althub, at least in my case.

In my case, althub test passes, but every nzb added via api results in the following: Message Request Failed: Failed to add nzb Ballers.2015.S02E05.720p.HDTV.x264.nzb Exception NzbDrone.Core.Download.Clients.DownloadClientException: Failed to add nzb Ballers.2015.S02E05.720p.HDTV.x264.nzb at NzbDrone.Core.Download.Clients.Nzbget.Nzbget.AddFromNzbFile (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode, System.String filename, System.Byte[] fileContent) <0x41840c60 + 0x0026f> in <filename unknown>:0 at NzbDrone.Core.Download.UsenetClientBase`1[TSettings].Download (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode) <0x417a7300 + 0x00525> in <filename unknown>:0 at NzbDrone.Core.Download.DownloadService.DownloadReport (NzbDrone.Core.Parser.Model.RemoteEpisode remoteEpisode) <0x417a6780 + 0x00561> in <filename unknown>:0 at NzbDrone.Api.Indexers.ReleaseModule.DownloadRelease (NzbDrone.Api.Indexers.ReleaseResource release) <0x417a65c0 + 0x000c1> in <filename unknown>:0 at NzbDrone.Api.Indexers.ReleaseModule.<.ctor>b__7_0 (System.Object x) <0x4179eb30 + 0x0002b> in <filename unknown>:0 at (wrapper dynamic-method) System.Object:CallSite.Target (System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,System.Func`2<object, object>,object) at Nancy.Routing.Route+<>c__DisplayClass4.<Wrap>b__3 (System.Object parameters, CancellationToken context) <0x416b0310 + 0x0014f> in <filename unknown>:0 from Sonarr, and NZBGet gives me ERROR Sun Aug 21 2016 10:03:13 Could not add collection Ballers.2015.S02E05.720p.HDTV.x264.nzb to queue ERROR Sun Aug 21 2016 10:03:13 Error parsing nzb-file Ballers.2015.S02E05.720p.HDTV.x264.nzb ERROR Sun Aug 21 2016 10:03:13 Error parsing nzb-file: Premature end of data in tag html line 1 ERROR Sun Aug 21 2016 10:03:13 Error parsing nzb-file: Opening and ending tag mismatch: body line 3 and html ERROR Sun Aug 21 2016 10:03:13 Error parsing nzb-file: Opening and ending tag mismatch: hr line 5 and body

Is anyone using this docker also using althub as an indexer? Sometime within the last week I started getting errors for any nzb added from althub either via rss sync or manual search, either through web UI or the Android app NZB360. I don't believe the docker is to blame as I'm receiving NZBs from other indexers, but the team at althub says everything is fine on their end. I even tried deleting the docker and image, redownloading and having it build a fresh config and scan everything back in with the same results. I'm hoping to either find others having the same issue or someone with a specific idea of what setting in my config might be wrong since they all look fine to me

Updated first post and hoping one of the Docker gurus here can take the time to give it a go.