sparklyballs

until inevitably he tries the same trick while inebriated and at wiping time gets the wrong hand......

the default setting in the template is for host mode, so any and all ports will be exposed irrelevant of the EXPOSE line in the dockerfile.

https://github.com/linuxserver/docker-sabnzbd/blob/master/Dockerfile#L24

https://github.com/linuxserver/docker-sabnzbd/blob/master/Dockerfile#L25

Bumped a new build to pick up 2.2.0 which was released to the sabnzbd ppa about 45 minutes ago (at time of this post).

no dodgy fixes required anymore the DMCA notice on this repository has been lifted and we have updated the image to pull the files at build time

TLDR;

it's working as expected unraid doesn't support ipv6 hence that particular error but everything else is working as expected

the actual command to run smokeping from the CLI is s6-setuidgid abc /usr/bin/smokeping --config="/etc/smokeping/config" --nodaemon

or i guess maybe you could hit "refresh" on your browser.......

not quite sure what else you expect us to be able to do, unless you fancy paying airfare for one of us to come and hold your hand for you !!!!

Great for open fires in the winter

new pull of the image and i'm getting graph data ok

it makes no difference, on unraid 6.4 port 443 is being used by the https page for the unraid webui and so is not available for any containers and as letsencrypt runs in host networking mode.....

port 443 on 6.4 is used for the https version of the unraid webui.

i've got 8500+ movies and there's no slow down at all.

This image has been rebased to ubuntu xenial as alpine linux no longer works for the 2.5x versions of resilio-sync. @Kash76 as part of the rebase it has been updated to 2.5

there's also another big difference.. one app is sonarr and the other is radarr.

That's an extremely advanced topic way beyond the scope of our support and i've no idea if it is even possible with the kodi headless container.

yeah nginx in the newer alpine uses two locations for tmp files for some reason and the perms weren't set on the other one

i reverted the last commit that was probably the cause, it seems latest jetty version doesn't play nicely.

/js/content.js is not the webui it's at whatever port you mapped 80 to , eg if you mapped 80 to 8088 then it's <your-ip>:8088

well that would suggest a server side error , ie the torrent site.

dunno , just added ubuntu iso torrent via url and downloaded torrent file with no problem and they're downloading.

what would be more useful if you were to use the latest letsencrypt version, as it's been rolled back to the earlier version, and the latest version of nextcloud which is on the newer version. we need to ascertain whether the problem is solely the LE side, the nextcloud side or a combination of both.