enigma27

@binhex I do have one further question though. I am using PIA via wireguard in the container and am constantly getting the below when trying to DL items... if I click the spanner and click unblock it will eventually work... if I am DL'ing things in the background (on a schedule per se) it may happen when it first gets added but will eventually resolve itself after the 10min wait.. any idea why this happens? is it because of the name servers in the template of the container and maybe one of them cannot resolve the server of the news reader?

FYI Sorted the above. Changed the permission on the unraid share for just the completed folder to match the incomplete folder and now its working. although not touched the settings of the shares in over 3 years so no idea what caused it.

I am having the same issue as above. Recently after completing a download SAB says it cannot write to the incomplete folder even though nothing has changed on my system other than updating the container. screenshot attached of the error... any idea what's causing or a fix? P.S excuse the title of the file, I swear it was just to test

ok perfect thank you Now i know the VPN works with other buffers I will just swap those out... Thank you

when I say VPN part I am talking about he quote from the author says "the buffer must be active otherwise the VPN is obsolete" but it doesn't say which buffer... is it specifically the Xteve buffer or will it still work with the FFMPEG buffer or VLC buffer. Secondly as stated in my post channels work fine with the following Buffer set as FFMPEG Buffer set as VLC No buffer active How can it possibly be the source? Here is what the log says when trying to connect to a channel with Xteve buffer active and others FFMPEG buffer - Works 2023/03/11 16:20:36 [xTeVe] Streaming Status: Playlist: M3U - Tuner: 1 / 1 2023/03/11 16:20:36 [xTeVe] Streaming Status: Buffering data from FFMPEG 2023/03/11 16:21:11 [xTeVe] Buffer: true [ffmpeg] 2023/03/11 16:21:11 [xTeVe] Buffer Size: 4096 KB 2023/03/11 16:21:11 [xTeVe] Channel Name: Hub Premier 1 FHD 2023/03/11 16:21:11 [xTeVe] Client User-Agent: VLC/3.0.18 LibVLC/3.0.18 2023/03/11 16:21:11 [xTeVe] Streaming Status: Client has terminated the connection 2023/03/11 16:21:11 [xTeVe] Streaming Status: Channel: Hub Premier 2 FHD (Clients: 0) 2023/03/11 16:21:11 [xTeVe] Streaming Status: Playlist: M3U - Tuner: 1 / 1 2023/03/11 16:21:11 [xTeVe] FFMPEG path: /usr/bin/ffmpeg 2023/03/11 16:21:11 [xTeVe] Streaming URL: xxxxxxx 2023/03/11 16:21:11 [xTeVe] FFMPEG: Processing data 2023/03/11 16:21:11 [xTeVe] Streaming Status: Receive data from FFMPEG 2023/03/11 16:21:12 [xTeVe] FFMPEG log: [h264 @ 0x146f74e09780] non-existing SPS 0 referenced in buffering period 2023/03/11 16:21:12 [xTeVe] Streaming Status: Buffering data from FFMPEG 2023/03/11 16:21:12 [xTeVe] Streaming Status: Channel: Hub Premier 2 FHD - No client is using this channel anymore. Streaming Server connection has ended and when Xteve buffer sent - Not Working 2023/03/11 16:33:59 [xTeVe] Buffer: true [xteve] 2023/03/11 16:33:59 [xTeVe] Buffer Size: 4096 KB 2023/03/11 16:33:59 [xTeVe] Channel Name: Hub Premier 10 FHD 2023/03/11 16:33:59 [xTeVe] Client User-Agent: VLC/3.0.18 LibVLC/3.0.18 2023/03/11 16:34:00 [xTeVe] Streaming Status: Playlist: M3U - Tuner: 1 / 1 2023/03/11 16:34:00 [xTeVe] Streaming Type: [TS] 2023/03/11 16:34:00 [xTeVe] Streaming URL: xxx 2023/03/11 16:34:03 [xTeVe] Streaming Status: HTTP Response Status [200] OK 2023/03/11 16:34:03 [xTeVe] Content Type: 2023/03/11 16:34:03 [xTeVe] Content Type: 2023/03/11 16:34:03 [xTeVe] [ERROR] Streaming error (Server sends an incompatible content-type) - EC: 4003 2023/03/11 16:34:03 [xTeVe] Streaming Status: Client has terminated the connection

Hi all. Anyone had issues connecting to channels with the Xteve buffer active today? Channels work fine as soon as I turn the buffer off or switch it to FFMPEG. any recommendations as to what could be causing the issue? I assume the VPN part only works with the Xteve buffer and not FFMPEG or VLC?

my appdata folder is set to cache only although in the docker template I do have it set like the below /mnt/cache/appdata/ rather than the default /mnt/user/appdata/

Only the web interface port as it conflicted with another docker container. Its weird I literally went to login and set-up a stream for tonight and once again all my settings have reverted to default. Stream key, logos, video settings.. all default. Strange thing is I dont think I have changed or updated the container since the last time i used it.

@ich777 Hope you can help sir. just updated the owncast container to the latest which is 0.0.12 and unless I am being really thick if I log into the admin panel and change a load of settings they never seem to stick and revert to default when the container is restarted. For example if I login to admin panel and change the stream key from abc123 to my own on restart of the container it reverts back to abc123 is this a glitch or me being thick

Hi All. Is there a tutorial on how to repair a corrupt database for this container. Mine randomly started playing up tonight even after watching a movie. really would rather not reinstall the whole thing.

Hi All. Really need some help as the NginX docker seems to started acting strange for me. So was simply trying to add a new SSL this evening and it kept giving me an internal error or a functional set of error codes that I couldn't copy down before writing this post. Long story short I tried to reboot my server and now although the container starts up as always the Webgui will not load at all either using the internal IP or the subdomain i have set-up for it as the subdomain (or any of the ones i have set-up for various containers) . looking in the logs all I seem to get is the following that constantly repeats itself ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/default_host/site.conf ❯ /data/nginx/proxy_host/1.conf ❯ /data/nginx/proxy_host/3.conf ❯ /data/nginx/proxy_host/4.conf ❯ /data/nginx/proxy_host/5.conf ❯ /data/nginx/proxy_host/6.conf ❯ /data/nginx/proxy_host/14.conf ❯ /data/nginx/proxy_host/16.conf ❯ /data/nginx/proxy_host/15.conf ❯ /data/nginx/proxy_host/17.conf ❯ /data/nginx/proxy_host/9.conf ❯ /data/nginx/proxy_host/18.conf ❯ /data/nginx/proxy_host/19.conf ❯ /data/nginx/proxy_host/2.conf nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-17/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-17/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) I have tried redownloading the container but does the same thing. any help appreciated/

to be fair i already had that installed. it seem updating unraid borked it.. working again now

Hi all. Maybe a bit dumb on my part but I have just installed unraid 6.10.3 (previously I was on 6.9) and now system temp plugin seems to be broke. when i go into the plugin settings page everything seem to be greyed out, tried rebooting the server a few times but doesn't help any idea?

Hi All. just updated my unraid to 6.10 (was on 6.9) and now SearchXNG container wont start Looks in the logs and this is all it says realpath() of /etc/searxng/uwsgi.ini failed: Permission denied [core/utils.c line 3662] realpath() of /etc/searxng/uwsgi.ini failed: Permission denied [core/utils.c line 3662] SearXNG version 2022.07.08-2864a67c Use existing /etc/searxng/uwsgi.ini ⚠️ Check new version /etc/searxng/settings.yml.new to make sure SearXNG is working properly Listen on 0.0.0.0:8080 SearXNG version 2022.07.08-2864a67c Use existing /etc/searxng/uwsgi.ini ⚠️ Check new version /etc/searxng/settings.yml.new to make sure SearXNG is working properly Listen on 0.0.0.0:8080 ** Press ANY KEY to close this window ** any ideas how to fix?, was working fine all day until i applied the unraid update. I have also checked for updates to the container and it seems up to date this started happening again. soon as the container is stopped it wont start up again, any ideas?

I was thinking maybe the 50% cpu usage is in being used by the host os which i believe is a Linux kernel.