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="HLS Streaming Server OBS is fine server doesn't get signal"]398[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2">Before, you said:<br /><comcode-quote param="richbom">when I put server address from droplets and start streaming on obs it is running (I see green and k/s ping on bottom right of obs as well)<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]395[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />Now, you said:<br /><comcode-quote param="wayzata">hit start streaming and get this error:<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]397[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />These are two different behaviors when you attempt to start streaming (actually streaming vs. popping up an error message.) So you're changing things without understanding what they do and also not telling me about it. I cannot read your mind or travel back in time to find out what you messed up, and I don't have time to try and understand what you thought you were doing.<br />From your logs, it looks like you may have forgotten to kill an older NGINX process before you started a new one at some point. Your config options won't apply until NGINX has actually been restarted.<br />With regards to "not understanding" the stream key, the stream key will simply become the name of your .m3u8 file.<br /><b>Edit:</b> I also noticed that the location directory for your http server does not match the hls_path directive for the HLS server. You need to serve via HTTP the same directory that your HLS server is putting its files into.<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="HLS Streaming Server OBS is fine server doesn't get signal"]398[/post], by jacobgkau [quote="2"] Before, you said: [quote="richbom"] when I put server address from droplets and start streaming on obs it is running (I see green and k/s ping on bottom right of obs as well) [snapback]395[/snapback][/quote] Now, you said: [quote="wayzata"] hit start streaming and get this error: [snapback]397[/snapback][/quote] These are two different behaviors when you attempt to start streaming (actually streaming vs. popping up an error message.) So you're changing things without understanding what they do and also not telling me about it. I cannot read your mind or travel back in time to find out what you messed up, and I don't have time to try and understand what you thought you were doing. From your logs, it looks like you may have forgotten to kill an older NGINX process before you started a new one at some point. Your config options won't apply until NGINX has actually been restarted. With regards to "not understanding" the stream key, the stream key will simply become the name of your .m3u8 file. [b]Edit:[/b] I also noticed that the location directory for your http server does not match the hls_path directive for the HLS server. You need to serve via HTTP the same directory that your HLS server is putting its files into. [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.