Report post You have 30 minutes to complete this form before the CAPTCHA will expire. Security image * Required field JavaScript is required to view this page. Either you do not have JavaScript enabled in your web browser, you do not have cookies enabled in your web browser, or this website is misconfigured such that cookies do not save correctly. This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="New Setup - Digital Ocean Droplet"]314[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2">Hi there!<br />Commenting on your usage of NGINX as a media server: I find it great for re-streaming to other platforms, but not suitable as a platform in itself, for <i>my</i> needs. Streaming services like Vimeo/Livestream, YouTube, etc. have content distribution networks that are able to transcode into better delivery formats and handle a lot of load; your one droplet, on the other hand, might have issues with too many people trying to read the raw stream from it at the same time. If it's only going to be a small number of users, though, then it might very well be fine.<br />It sounds like you already got that part figured out, which is great. If you can view the stream in VLC on your computer, you should be able to view it on VLC for Android; RTMP is supported on VLC for Android. There's not anything you can "optimize" in the NGINX config file with regards to that.<br />As far as firewalls go, that's an option since you're reading the stream directly, but it will only work if you have static IP addresses for the devices you're accessing the video from (assuming a simple setup). If the video is going over the internet, that means you'll need static public IPs. If you're just streaming over a local network, then the firewall would be easier to set up, but also less necessary. I think you already know that stuff. The RTMP port is TCP 1935 (which you can change in your config file), so that's what you can restrict by IP if you want to do so.<br />Are there currently any sticking points for you/concrete questions I can answer? If I'm wrong about being able to view the video from your server already, let me know and I can help with that. Otherwise, it sounds like you already have things set up. NGINX isn't a fully built-out streaming server, but it should be fulfilling your basic requirements already, unless I'm overlooking something.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="New Setup - Digital Ocean Droplet"]314[/post], by jacobgkau [quote="2"] Hi there! Commenting on your usage of NGINX as a media server: I find it great for re-streaming to other platforms, but not suitable as a platform in itself, for [i]my[/i] needs. Streaming services like Vimeo/Livestream, YouTube, etc. have content distribution networks that are able to transcode into better delivery formats and handle a lot of load; your one droplet, on the other hand, might have issues with too many people trying to read the raw stream from it at the same time. If it's only going to be a small number of users, though, then it might very well be fine. It sounds like you already got that part figured out, which is great. If you can view the stream in VLC on your computer, you should be able to view it on VLC for Android; RTMP is supported on VLC for Android. There's not anything you can "optimize" in the NGINX config file with regards to that. As far as firewalls go, that's an option since you're reading the stream directly, but it will only work if you have static IP addresses for the devices you're accessing the video from (assuming a simple setup). If the video is going over the internet, that means you'll need static public IPs. If you're just streaming over a local network, then the firewall would be easier to set up, but also less necessary. I think you already know that stuff. The RTMP port is TCP 1935 (which you can change in your config file), so that's what you can restrict by IP if you want to do so. Are there currently any sticking points for you/concrete questions I can answer? If I'm wrong about being able to view the video from your server already, let me know and I can help with that. Otherwise, it sounds like you already have things set up. NGINX isn't a fully built-out streaming server, but it should be fulfilling your basic requirements already, unless I'm overlooking something. [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.