enigma27

Members
  • Posts

    113
  • Joined

  • Last visited

Posts posted by enigma27

  1. 6 minutes ago, alturismo said:

    depends what "VPN Part" you mean, actually any buffer will work the same way ... xteve, ffmpeg, vlc ...

     

    so, in terms you use xteve behind a VPN Client, yes, all will work then.

     

    and as there where no changes, i would suggest you rather look at your source, changes prolly came from there.

     

    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

     

     

  2. 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?

  3. On 9/5/2022 at 5:55 AM, ich777 said:

    I've tried it now on my server and over here this is not the case.

    Have you changed anything in the template?

     

    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.

  4. @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

  5. 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/

  6. 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?

     

    image.thumb.png.52561941e5004cf88696785564f76302.png

  7. 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?

  8. great container. made it really simple to stream to my private owncast website.

     

    I have one question.. I am using Nvenc H264 encoder which seems to be working as Nvidia-SMI shows it being used by OBS... but my CPU is also being used at 50% while running

     

    why would this be?

     

    GPU encoder shows approx 35% usage but CPU is at 50% I thought CPU would be lower

     

    image.png.f0c9098a3c18c247de4742fb699235b0.png

     

    image.png.f67ffabb2eacf7bc407c3f0e928f2bf5.png

  9. Hi all.

     

    Could really use some help getting this working. I am using the most basic version of xteve and have imported my M3u and XML and that all shows up fine in the dashboard and channels are mapped. I am getting issues when trying to add the DVR to Plex.

     

    When I try searching by IP address I get an error in please saying "There was a problem adding the device: 192.168.102.2:34400"

     

    If i test the Xteve URLs in VLc they are up and running and I also seem to ab able to load the M3u and XMl in emby and again they work fine.

     

    Any ideas on why plex cannot connect to the Xteve proxy wtih IP?

  10. On 7/6/2021 at 1:26 PM, Johnny Utah said:

     

    Just curious how you accomplished this if you wouldn't mind sharing please?  Was hoping to allow Bedrock players to access my Java server.

    Hi Johnny

     

    So don't think it was straight forward and should have probably wrote it down but from memory I did the following

     

    Downloaded Spigot from the website and uploaded the Jar to the server (Couldn't get it to download through mineos webui)

     

    I then created a new server and made the jar file for the server the Spigot JAR i had uploaded. Once that was up and running I downloaded the required plugin Geyser-spigot version and added that to the plugin folder within the server folder. i then followed the instructions in the config file that came with Geyser to what i needed it to be and booted up the server and it just seemed to work.

    • Like 1
  11. Hi @binhex.

     

    got a weird issue and cant seem to work out what's happening so hoping someone can give me some insight.

     

    I have two servers running that I leave up all the time. The last few mornings I have woken to find the actual docker unresponsive and I am unable to access the webUI. restarting the docker container seems to sort the issue. looking at the logs for the docker I see the following happens around 4am each morning.

     

    2021-06-24 04:00:04,672 WARN received SIGTERM indicating exit request
    2021-06-24 04:00:04,673 DEBG killing start-script (pid 75) with signal SIGTERM
    2021-06-24 04:00:04,673 INFO waiting for shutdown-script, start-script to die
    2021-06-24 04:00:05,674 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22811341001200 for <Subprocess at 22811341389584 with name start-script in state STOPPING> (stdout)>
    2021-06-24 04:00:05,674 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22811341051840 for <Subprocess at 22811341389584 with name start-script in state STOPPING> (stderr)>
    2021-06-24 04:00:05,674 INFO stopped: start-script (terminated by SIGTERM)
    2021-06-24 04:00:05,674 DEBG received SIGCHLD indicating a child quit
    2021-06-24 04:00:05,675 DEBG killing shutdown-script (pid 74) with signal SIGTERM
    2021-06-24 04:00:05,676 DEBG 'shutdown-script' stdout output:
    [info] Initialising shutdown of process(es) '^mineos' ...
    
    2021-06-24 04:00:06,677 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22811341389488 for <Subprocess at 22811341385984 with name shutdown-script in state STOPPING> (stdout)>
    2021-06-24 04:00:06,677 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22811341385792 for <Subprocess at 22811341385984 with name shutdown-script in state STOPPING> (stderr)>
    2021-06-24 04:00:06,677 INFO stopped: shutdown-script (exit status 0)
    2021-06-24 04:00:06,677 DEBG received SIGCHLD indicating a child quit
    Created by...
    ___. .__ .__
    \_ |__ |__| ____ | |__ ____ ___ ___
    | __ \| |/ \| | \_/ __ \\ \/ /
    | \_\ \ | | \ Y \ ___/ > <
    |___ /__|___| /___| /\___ >__/\_ \
    \/ \/ \/ \/ \/
    https://hub.docker.com/u/binhex/
    
    2021-06-24 04:03:46.880040 [info] Host is running unRAID
    2021-06-24 04:03:46.918733 [info] System information Linux 975ded9594a1 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux
    2021-06-24 04:03:46.969616 [info] OS_ARCH defined as 'x86-64'
    2021-06-24 04:03:47.019571 [info] PUID defined as '0'
    2021-06-24 04:03:47.086145 [info] PGID defined as '0'
    2021-06-24 04:03:47.168529 [info] UMASK defined as '000'
    2021-06-24 04:03:47.206732 [info] Permissions already set for '/config'
    2021-06-24 04:03:47.265553 [info] Deleting files in /tmp (non recursive)...
    2021-06-24 04:03:47.318753 [info] WEBUI_PASSWORD defined as 'xxxxxxxxxxxxxx'
    2021-06-24 04:03:47.400914 [info] JAVA_VERSION defined as '16'
    2021-06-24 04:03:47.481562 [info] Starting Supervisor...
    2021-06-24 04:03:48,039 INFO Included extra file "/etc/supervisor/conf.d/mineos-node.conf" during parsing
    2021-06-24 04:03:48,039 INFO Set uid to user 0 succeeded
    2021-06-24 04:03:48,046 INFO supervisord started with pid 9
    2021-06-24 04:03:49,048 INFO spawned: 'shutdown-script' with pid 76
    2021-06-24 04:03:49,050 INFO spawned: 'start-script' with pid 77
    2021-06-24 04:03:49,051 INFO reaped unknown pid 10 (exit status 0)
    2021-06-24 04:03:49,102 DEBG 'start-script' stdout output:
    [info] Starting MineOS-node...
    
    2021-06-24 04:03:49,102 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2021-06-24 04:03:49,102 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2021-06-24 04:03:49,340 DEBG 'start-script' stdout output:
    mineos daemon already running. PID: 86
    
    2021-06-24 04:03:49,343 DEBG 'start-script' stdout output:
    [info] MineOS-node started

     

    something seems to be trying to shut the image down but I cant work out what.

     

    None of my other docker images shut down and I have no scripts within Unraid either that asks for docker to be shut down.

     

    any idea what maybe causing it?

  12. Hi All.

     

    Anyone got a swag proxy-conf file to access the webUI from a sub domain?

     

    tried a few that i have for other dockers but none seem to work

     

    Don't worry sorted it

     

    anyone know of a tutorial showing hoe to install the crossplay plugin Geyser?

     

    dont worry sored this also.

  13. Thank you sir

     

    I made a slight tweak to this as swag gave an error on a missing file in case anyone else wants to use it.

     

    saved file as owncast.subdomain.conf

     

    server {
    	listen 443 ssl;
    
    	include /config/nginx/ssl.conf;
    	include /config/nginx/error.conf; <-- removed this as swag logs said the file was missing
    
    	server_name owncast.*; <-- changed this as its seems to work same as other dockers
    
    	location / {
    		proxy_pass http://IPOFSERVER:PORT;  
    
    		proxy_set_header Range $http_range;
    		proxy_set_header If-Range $http_if_range;
    		proxy_set_header X-Real-IP $remote_addr;
    		proxy_set_header Host $host;
    		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    
    		proxy_http_version 1.1;
    		proxy_set_header Upgrade $http_upgrade;
    		proxy_set_header Connection "upgrade";
    		}
    }

     

    • Like 1
  14. @ich777

     

    Thanks very much for the owncast docker this is really interesting. A couple of questions

     

    1. port 8080 is already being used for another docker. is it safe to just change this to another port in the template?

    2. Is there a simple proxy-conf I can edit to use this docker with swag so I can use my own domain to reach the site?

    • Like 1