Question / Help Can't Connect to only YouTube. Other site work fine.

[astebbi1]

Hey all, I've been fighting with this for 2 days now. I'm trying to connect OBS running on a linux VPS instance with a full desktop GUI to YouTube.

I have been able to connect to smashcast so it can't be firewall or security related right?

Open to any ideas, let me know if you need more info. Log attached.

 

[Narcogen]

It can be if the firewall is configured to specifically block access to YouTube ingest servers to prevent that activity, rather than just blocking RTMP ports in general.

 

[astebbi1]

Thanks for the idea, firewalld isn't currently installed on the server. Any other way to test this theory?

 

[Narcogen]

There's not really anything to test.

10:57:40 PM.447: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://a.rtmp.youtube.com/live2...
10:57:40 PM.462: adding 92 milliseconds of audio buffering, total audio buffering is now 139 milliseconds
10:59:50 PM.052: The connection timed out. Try a different server, or check that the connection is not being blocked by a firewall or other security software (ETIMEDOUT).
10:59:50 PM.052: [rtmp stream: 'simple_stream'] Connection to rtmp://a.rtmp.youtube.com/live2 failed: -2

The server cannot reach the selected ingest server. Either it's being blocked on the server or upstream of it, or networking on the VPS is misconfigured. This is absolutely a network issue and nothing else. You should give these lines in the log to whomever maintains that instance or the data center it is in and ask why the YouTube ingest server can't be reached, but the ingest server of other services can be.

 

[astebbi1]

Thank you, that makes sense and is a big help.

Other than contacting the VPS provider, is there anything I can do around configuring the VPS networking? Maybe put that ingest server on a whitelist within my VPS instance?

 

[Narcogen]

It's rare to be allowed that flexibility in configuring a rented VPS instance. A whilelist in your instance won't override a blacklist being enforced by the provider.

This is either intentional, or it's an error. If it's intentional, you're not going to be able to fix it. If it's an error, the provider can and should fix it.

 

[astebbi1]

Much appreciated, seems like contacting the provider is the way to go. Will report back if I hear back from them.

 

[astebbi1]

Hey so if you're reading this in the future here's what I did to get it working.

Started up a new instance with xfce4 desktop instead of kde. All other settings the same. Not sure what was wrong with the initial setup but it works now.