Hey Andrew,

I am really sorry for the delay of this reply as it is actually a public day off for us here. It looks like you have submitted this to my email, our support desk and the forums. Kindly please just use the forums from now on as I have to reply you on 3 different platforms.

I need the SFTP access to the site to troubleshoot this since you mentioned that the IP address is now changed.

Mark, I emailed you the IP. That changed due to your suggestion that we should change the IP.

BTW, it is currently a bit confusing with the support changing to Forums. I just replied to the email I received as I always do. I guess it will improve as we move ahead.

thanks

Just wanted to add that I'm having the same problem ... no thumbnail or description, just the link

Frank

Hey Frank,

Can you please start a new thread in the forums so that we can take a look at your site?

Hey Frank,

Should we not collaborate as these issues are potentially related? Frank, could you send me an email andrew@imnlimited.com?

Thanks

Frank J. Kelly wrote:

Just wanted to add that I'm having the same problem ... no thumbnail or description, just the link

Frank

Thanks,

Andrew

Hey Andrew,

I just done some really extensive tests on both EasyBlog and EasySocial and they pose the same issue here,

https://www.opgroeigids.nl/index.php?option=com_easysocial&debugyoutube=1
https://www.opgroeigids.nl/index.php?option=com_easyblog&debugyoutube=1

They both run on different scripts but results on the same "recaptcha" form. I believe somehow Youtube is flagging the entire block of ip address and requires you to enter captcha.

To show you the exact issue, I have ssh-ed into your server, and tried to browse a video on youtube (Although the video won't appear in a terminal), it's displaying the same exact error message in English, http://screencast.com/t/89rbpJzHUBpT

Interesting ... Andrew do you happen to be running on an Amazon EC2 instance? My primary site is running as an EC2 instance and I find that if I use an exact akeeba back up copy on my development VPS the stream handles youtube video with no problems ...

I've also tried vimeo imports under both environments and vimeo works with no issues?

Frank

Frank, thanks for the update. I sent you an email with some details.

It is definitely related with Amazon EC2 instances or Amazon IPs and YouTube.

I have re-tested our dev site which is running on EC2 on region Ireland, this has no issues with YouTube. It works perfectly. Our issues are since we moved our site to region Frankfurt.

I suspect the AWS Frankfurt region IPs and location to be the problem and that YouTube has flagged those IPs as risky or something... Unless it has to do with the issues which Germany and YouTube have had or having.... mmmmmm

I have logged a ticket via our Developer Support at Amazon and should have an answer in the coming hours. Will post update when I receive it.

Thanks for confirming and sharing this Andrew

UPDATE:

Just received an update from Amazon support:

Thank you for contacting AWS Premium Support about your YouTube issues in Frankfurt. It looks like my colleague, Chandini, has worked with you up to this point. I’ll be glad to look into this to help you resolve this issue.

After some investigation, it appears that your initial suspicion of YouTube blocking the IP range from Amazon in the Frankfurt region is correct, thank you for bringing this to our attention. I can understand your frustration with this and do apologize for the inconvenience. I have reported this situation to our Abuse Team and they are engaging YouTube directly to get this issue resolved. Unfortunately it is out of our control for now and therefore it is unknown how long the resolution may take.

Well, this is a pain in the .....

Wow ... a "pain in the .....: for sure. I guess I should probably begin a process to have them look at the Northern California regions ips as well ...

Frank... Northern California IPs are not affected. Try changing your IP. Do you make use of Elastic IP, if so quick and easy to change.

Comment from Amazon Support Team:

"Lastly, about your contact with the same issue in California, because the entire block of IPs there has not been blocked there, there must be an undiscovered issue surrounding that IP. If they submit a case through customer support, we can work to discover what the underlying problem is for them as well."

Hope this helps you.

Hi Andrew,

Sad to hear . We hope that the issue could be resolve soon. Thank you for the heads up on this issue.

Hello Andrew,

To date I have not tried to change my elastic ip. I think for my situation it might be a different issue. What I did do to see if it was a global problem for my ip was install the free version of Yendif's Video Share program and lo and behold, it works perfectly on the EC2 instance. As a consequence I think it is not the same problem you're encountering with your ip.

I'm going to try to submit a support ticket and see if the guys here can help me work it out ... anything I discover that might help I'll share ...

Thanks

Frank

Quick update,

As per your suggestion Andrew, I changed my elastic ip, just to make sure it was not an issue. Even though changed, I get the same issue with my easysocial stream AND I now see that in easyblog, unless I use the quick post method, videos will not embed in standard blog posts! I'm using the latest release of easyblog ...

Frank

Hi Frank, that is very interesting... Please do keep me updated on the findings. With regards to EasyBlog, ours works perfectly with YouTube. This was a concern to me before but Mark explained that it works as it does not scrape the info from YouTube as ES does. And in my case Amazon found that there was indeed issues with the IP ranges in their Frankfurt region.

Thanks again...

I think it has something to do with users using Amazon EC2 and probably abusing with their ip address on Youtube or some other services. Perhaps these ip address are being blacklisted. I would suggest that you try out a different region as Andrew pointed out earlier

Comment from Amazon Support Team:

"Lastly, about your contact with the same issue in California, because the entire block of IPs there has not been blocked there, there must be an undiscovered issue surrounding that IP. If they submit a case through customer support, we can work to discover what the underlying problem is for them as well."

In Frank's case it has to be something else. He has also already changed his Elastic IP to a new IP and it made no difference...

Hm, perhaps Frank should send an email to Amazon?