[Support] ich777 - Application Dockers


ich777

Recommended Posts

16 minutes ago, eds said:

Hmmmm.  I'm not at all sure what you mean. 

 

If you use owncast as advertised it pretty clear what needs to be done.   To connect a streaming program like OBS to owncast you use rtmp as the protocol not http(s).  

 

i thought so, the "regular" usage for a reverse proxy is http(s), actually, nginx does support rtmp but not through the regular server blocks as pre configured, specially not when using NPM which is basic ...

 

search for nginx rtmp streaming module and how to use it, then you should see what i mean, the "normal" RP setup doesnt support rtmp out of the box.

 

as start point https://docs.nginx.com/nginx/admin-guide/dynamic-modules/rtmp/

 

no idea if NPM has it pre installed (i guess so), then you "only" have to manually configure it, not so hard, i use it for my personal HLS streaming server with ABR for Live TV web streaming as fun project.

Link to comment
20 minutes ago, alturismo said:

i thought so, the "regular" usage for a reverse proxy is http(s), actually, nginx does support rtmp but not through the regular server blocks as pre configured, specially not when using NPM which is basic ...

 

search for nginx rtmp streaming module and how to use it, then you should see what i mean, the "normal" RP setup doesnt support rtmp out of the box.

 

as start point https://docs.nginx.com/nginx/admin-guide/dynamic-modules/rtmp/

 

no idea if NPM has it pre installed (i guess so), then you "only" have to manually configure it, not so hard, i use it for my personal HLS streaming server with ABR for Live TV web streaming as fun project.

@alturismo Thanks for the feedback.   I am almost certain cloudflare (which apparently now sells a streaming tier) is also involved here somehow.

Fortunately I can reach owncast via the local ip address so there is no need for me to take on this task at this time.

I was just interested if @Mr_Jay84 was working remotely and if he'd conquered the same problem.

Link to comment

@eds in case, take a look at your dns settings in CF, turn off "proxy" feature (orange cloud = on, grey = off, then its just like a dns service ... but like i said, rtmp is a different protocoll and needs some setup (to use the rtmp module) to proxy a rtmp stream, which is then not going through the http part and not really using the domain selection, you will figure it.

 

https://obsproject.com/forum/resources/how-to-set-up-your-own-private-rtmp-server-using-nginx.50/

 

there you see the server block (streaming server part on its own port, not http by domain ...), take a look if you really want to go through it.

  • Like 1
  • Thanks 1
Link to comment
19 hours ago, eds said:

 I am using ngnix proxy manager and I have cloudflare as my registrar. 

I can reach the domain's admin page no problem, but I cannot access owncast using rtmp with the domain name. 

I believe it is because cloudflare is blocking it.  I turned their proxy service off the cname and still no luck.

I am beginning to believe I can't use owncast with cloudflare, but I cannot be sure.

Maybe you can tell me if there is anything in the logs I should be looking at to see if in fact this is the problem.

Like you I use Cloudflare although I use SWAG as the gateway. Works perfectly for me.

Owncast should be used via http or https. My runs via https on my domain name and http internally.

Why would you want to use RTMP just out of interest?
 

Screenshot 2021-07-05 234508.jpg

Edited by Mr_Jay84
Link to comment
2 hours ago, eds said:

@alturismo Thanks for the feedback.   I am almost certain cloudflare (which apparently now sells a streaming tier) is also involved here somehow.

Fortunately I can reach owncast via the local ip address so there is no need for me to take on this task at this time.

I was just interested if @Mr_Jay84 was working remotely and if he'd conquered the same problem.

You stream from OBS to Owncast via RTMP on the internal address

Users access Owncast via the http/https address

Could this be the confusion?

Link to comment
2 hours ago, Mr_Jay84 said:

Like you I use Cloudflare although I use SWAG as the gateway. Works perfectly for me.

Owncast should be used via http or https. My runs via https on my domain name and http internally.

Why would you want to use RTMP just out of interest?
 

Screenshot 2021-07-05 234508.jpg

 

Ummm, cause owncast tells me to???

Link to comment
27 minutes ago, eds said:

Using https my owncast is totally unstable.

 

Is your stream setting, for example,  https://mydomain.com/live or https://mydomain.com:1935?

I think you're getting confused here mate.

 

You use RTMP to stream from OBS to Owncast. This is normally done on your internal network i.e. rmtp://YourUnraidIP:1935/live.

 

Port 1935 is what you stream to from OBS. It's not the port users should connect too, which by default is 8080

 

Then to access the Owncast page via https use (for example) https://Owncast.yourdomain.com

No port is required as it's https.

 

Your gateway should be pointing the domain to the internal address i.e. http://YourUnraidIP:8080

 

 

Edited by Mr_Jay84
Link to comment
2 minutes ago, Mr_Jay84 said:

I think you're getting confused here mate.

 

You use RTMP to stream from OBS to Owncast. This is normally done on your internal network i.e. rmtp://YourUnraidIP:1935/live.

 

Port 1935 is what you stream to from OBS. It's not the port users should connect too, which by default is 8080

 

Then to access the Owncast page via https use (for example) https://Owncast.yourdomain.com

No port is required as it's https.

 

Your gateway should be pointing the domain to the internal address i.e. http://YourUnraidIP:8080

 

 

 

I see. I was unclear in my initial question to you.  I should have asked what you have obs connecting to, the domain name or the ip address of owncast.

 

I have no issue with remote viewing or access the admin page from the domain name. 

For me it was always about OBS connecting to owncast.  And it appears as if you are using the ip address via rtmp to do that as am I. 

 

 

 

Link to comment
1 minute ago, eds said:

 

I see. I was unclear in my initial question to you.  I should have asked what you have obs connecting to, the domain name or the ip address of owncast.

 

I have no issue with remote viewing or access the admin page from the domain name. 

For me it was always about OBS connecting to owncast.  And it appears as if you are using the ip address via rtmp to do that as am I. 

 

 

 

Ah right I see. Yeah you connect to Owncast from OBS via the unRaid IP.

 

You may have to adjust the hardware resources or the stream settings in Owncast itself if you're experiencing buffering the Owncast stream page. My Owncast is set for 3000Kbps but you'll have to tailor yours for your hardware/bandwidth. There's also a buffer/delay setting to be mindful of, too low and your end users might have issues.

 

With regard to OBS.  I have the stream set to use the x264 CPU encoder, CBR, 3000Kbps, fast CPU usage. I tried NVENC but the result was a pixelated stream on the Owncast side. Remember Owncast does a transcode of it's own.

 

My setup is OBS on a Win 10 VM hosted on unRaid streaming to Owncast docker on the same machine. I have four cores (8 threads) assigned to both the docker and the VM. I also tested tested it from various bare metal machines ony CAT6 network with no issues either. I wouldn't recommend trying this on WiFi though.

 

Feel free to ask any more questions if needed.

  • Like 1
Link to comment
10 hours ago, Mr_Jay84 said:

Ah right I see. Yeah you connect to Owncast from OBS via the unRaid IP.

 

You may have to adjust the hardware resources or the stream settings in Owncast itself if you're experiencing buffering the Owncast stream page. My Owncast is set for 3000Kbps but you'll have to tailor yours for your hardware/bandwidth. There's also a buffer/delay setting to be mindful of, too low and your end users might have issues.

 

With regard to OBS.  I have the stream set to use the x264 CPU encoder, CBR, 3000Kbps, fast CPU usage. I tried NVENC but the result was a pixelated stream on the Owncast side. Remember Owncast does a transcode of it's own.

 

My setup is OBS on a Win 10 VM hosted on unRaid streaming to Owncast docker on the same machine. I have four cores (8 threads) assigned to both the docker and the VM. I also tested tested it from various bare metal machines ony CAT6 network with no issues either. I wouldn't recommend trying this on WiFi though.

 

Feel free to ask any more questions if needed.

 

Yeah, sound like we have a similar setup.  I have a 10th gen i3 nuc I'm using running windows 10 pro.  

 

What kind of latency are you getting? I'm seeing is like a 15 second.  But I'm also using wasabi as a storage end point which could be part of the problem, not sure.

Edited by eds
Link to comment
21 hours ago, arturovf said:

19 days after that post this is what it looks like:

I think this has something to do how the Mega sync is working.

Hope you don't mind me asking if you can try to setup your backup like in the age plugin thread with rclone, third post - you have to modify it a little bit to fit for Mega at Step 5 and the following steps.

(You don't have to use age for your backups but I think this is a good step by step tutorial and would give you a good idea how to set it up)

 

 

Link to comment

I use the OpenVPN client to bypass a double NAT situation and share my Jellyfin via external VPS.

 

How can I set up a split tunnel in this case so that I can still access the server from the LAN without problems and also ensure access from the Jellyfin to my live TV address?

 

Or is this just a setting thing in the Jellyfin settings?

Link to comment
On 7/4/2021 at 4:47 PM, ceyo14 said:

it doesn't actually lock up the server, what doesn't work that I can tell is the WebGUI, obviously the Checkmk Docker and for some reason if I try and pull diagnostics using SSH, it freezes and never completes....

Can you try to reinstall the container with this tag again:

grafik.png.4bb37155858ff9adbe56a78b4404c9bc.png

 

The creator from the container updated it yesterday again and I think it should now work.

 

22 hours ago, aurevo said:

How can I set up a split tunnel in this case so that I can still access the server from the LAN without problems and also ensure access from the Jellyfin to my live TV address?

@Opawesome wrote a good tutorial on that, hope that helps:

 

Link to comment
On 7/6/2021 at 1:57 PM, eds said:

 

Yeah, sound like we have a similar setup.  I have a 10th gen i3 nuc I'm using running windows 10 pro.  

 

What kind of latency are you getting? I'm seeing is like a 15 second.  But I'm also using wasabi as a storage end point which could be part of the problem, not sure.

The media is stored on my NAS however I did find it was better to copy the item to the OBS VM first. The Owncast end user has a delay of about 8 seconds, owncast is set at medium for the latency buffer. I've had up to 8 users so far in various parts of the world, playback has always been smooth with no issues.

  • Like 1
Link to comment
On 7/6/2021 at 11:25 AM, ich777 said:

I think this has something to do how the Mega sync is working.

Hope you don't mind me asking if you can try to setup your backup like in the age plugin thread with rclone, third post - you have to modify it a little bit to fit for Mega at Step 5 and the following steps.

(You don't have to use age for your backups but I think this is a good step by step tutorial and would give you a good idea how to set it up)

 

 

What is the objetive of doing this??

Link to comment
1 minute ago, arturovf said:

What is the objetive of doing this??

I don't understand...

You can mount a Mega share to your local unRAID server with rclone and then synchronize everything and see if it works that way.

 

Or you can do the backups like in the tutorial since this is almost the same as with CA Backup and they are encrypted too if you use age.

 

I sync to 3 different providers and have not a single problem, but also have to say that I use my MegaSync Container to sync to Mega and this works also flawlessly.

Link to comment
11 minutes ago, ich777 said:

I don't understand...

You can mount a Mega share to your local unRAID server with rclone and then synchronize everything and see if it works that way.

 

Or you can do the backups like in the tutorial since this is almost the same as with CA Backup and they are encrypted too if you use age.

 

I sync to 3 different providers and have not a single problem, but also have to say that I use my MegaSync Container to sync to Mega and this works also flawlessly.

Well it's just a minor annoyance, and seems it appears im the only one experiencing it I think it doesn't worth the trouble hehe, I may just delete the older folders which doesn't got deleted and be done with it.  I appreciate that in every question I have you are there to help, thank you man

Edited by arturovf
  • Like 1
Link to comment

Cheers!

 

I've got a problem with your OpenVPN-Client docker.

 

I've been using it for quite some while now, but today I rebuilt my OpenVPN-server and thus had to add new authentication files.

At first I had some problems with old and/or wrong shortcuts, but (presumably) got it to work.

 

While the connection seems to get established and I can ping the VPN-IP, the tun-interface doesn't seem to be created and I can't access the server GUI.

 

This is what the log says:

Quote

Fri Jul 9 10:53:51 2021 TUN/TAP device tun0 opened
Fri Jul 9 10:53:51 2021 TUN/TAP TX queue length set to 100
Fri Jul 9 10:53:51 2021 /sbin/ip link set dev tun0 up mtu 1500
Fri Jul 9 10:53:51 2021 /sbin/ip addr add dev tun0 10.8.0.20/24 broadcast 10.8.0.255

 

Doing an "ifconfig" from UnRAID terminal doesn't show that tun0-interface though, which previously had worked.

 

EDIT:

Accessing the Container via Console and doing an "ifconfig" the tun0-interface showed up.

After a tad more tinkering, I changed the default network type "Bridge" to "Host", and now everything works as intended! 🙂

Edited by Turnspit
Link to comment

Again, I'm not sure whether this is related to the Owncast software or the container, but when I try to set up external storage configured with Digital Ocean, I get the error:

 

https://i.imgur.com/hYuOMnN.png

Error: More than 1000 frames duplicated

 

I could've sworn I got storage-based streaming working a few days ago, and it may have been before I updated the container to the latest version. I can't test it on the previous version because it's not listed on dockerhub.

 

The stream basically looks like a slide show with a buffering circle. Also the stream portion uploaded to Digitalocean is split in 1.5mb increments, which clearly isn't right:

 

https://i.imgur.com/FHWC0Iq.png

 

It still works fine if I stream directly from my home server without using external storage, but I obviously don't want that because of my worse upload speed.

Edited by Stubbs
Link to comment
7 minutes ago, Stubbs said:

I could've sworn I got storage-based streaming working a few days ago, and it may have been before I updated the container to the latest version. I can't test it on the previous version because it's not listed on dockerhub.

My containers work a little different, the check on every start/restart if there is a newer version from the application available and installs it.

 

9 minutes ago, Stubbs said:

Error: More than 1000 frames duplicated

Is this eventually related: Click

 

9 minutes ago, Stubbs said:

is related to the Owncast software or the container

I don't think it's related to the container since I do nothing special with Owncast and as said above it installs on the first start from Github itself.

The last update from the container was actually because I added the necessary IntelQuickSync HW acceleration dependencies and packages.

 

Try to create a issue here: Click

Link to comment

So I've been using your OpenVPN container for a while, and have run into an issue. My power went out yesterday and my ups failed. Parity check came back clean, but my VPN container refuses to run properly. All that shows up in the log is:
image.png.82ddd4336b6e6432eefef12522714b73.png
 

I haven't made any changes and have rebuilt the container and this is all I get. I've also tried multiple VPN server files to see if that was the issue and get the same thing.

Link to comment
38 minutes ago, rcm024 said:

I haven't made any changes and have rebuilt the container and this is all I get. I've also tried multiple VPN server files to see if that was the issue and get the same thing.

It seems like something is wrong with the configuration.

Can you try to delete the container and reinstall it again (leave the config files on their spot)?

 

I would recommend to make create a issue on Github since I've only created the template for this really superior container: https://github.com/dperson/openvpn-client

Link to comment
13 hours ago, ich777 said:

Can you try to delete the container and reinstall it again (leave the config files on their spot)?

Have now tried this with no success. I did decide to leave the container running for a few min and got some additional Log output:
image.png.cf7d82c710a456f903a56672ed278e87.png
 

Seems to be missing vpn.conf? But it never had it before and worked fine. Any ideas? If not I'll submit to the github, but wanted to see if there might be something dumb I'm missing first.

 

Thanks

Link to comment
2 hours ago, rcm024 said:

Seems to be missing vpn.conf? But it never had it before and worked fine. Any ideas? If not I'll submit to the github, but wanted to see if there might be something dumb I'm missing first.

What files are im their now?

The configuration file needs to be renamed to vpn.conf

Do you have to enter credentials too to connect?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.