Problem with image script

2Pro4u

• May 23, 2018 16:28

I have a site that aggregates news from 3rd party sites, as well as a few of my own. In this site, I have an image script that sites in the img src before the calling of a 3rd party image. This script basically converts any http image from a 3rd party domain to https, as my domain is https. The thing that I've noticed, is that on my other sites (not the aggregator, but what is being pulled), this script broke in pulling their image at all. If I go into my source, and remove the image.php from the img src, and refresh the page, the images then pull just fine. So on my aggregator site, I have dozens of sites, that at first appearance, look like they've stopped allowing their images to be pulled or hyperlinked to, but is what I believe to be the case, is that these site owners, have actually updated their cpanel, to these versions of cpanel that break my image pulling script that keeps my aggregator completely https, without saying images aren't https. I'm just starting to know php, but the image.php was provided here: - Removed - Can anybody here confirm my suspicions that one of the 2 recent cpanel updates broke this script, and if so, if it was because of a security reason with cpanel, or something unintentional by the cpanel dev team? I've looked over the last 2 cpanel changelogs, but I don't really understand if any of those fixes would have broken this image script. Thanks for any help someone can provide me on this issue. (Unfortunately, I'm unable to give a link to my aggregator to show it working/not working.)

• 

  cPanelMichael

  • May 24, 2018 17:47

  Hello @2Pro4u, Can you review the Apache error log (/usr/local/apache/logs/error_log) on one of the cPanel servers the script is fetching the images from to see what appears when reproducing the issue? Thank you.

  0
• 

  2Pro4u

  • May 24, 2018 19:40

  I've looked through the apache error log for the domain name and date that would contain any error from the aggregator (on the same server) for my domain that has the images (the site that's being aggregated), and there are no image errors noted in the error log. Just a bunch of bots trying to find a Wordpress login file.

  0
• 

  cPanelMichael

  • May 24, 2018 19:45

  Hello, You'd need to check the log on the server that hosts the images, as opposed to the server that hosts the aggregator. Thank you.

  0
• 

  2Pro4u

  • May 24, 2018 20:40

  They are both are on the same server, which is why it's even more surprising why it broke.

  0
• 

  cPanelMichael

  • May 24, 2018 20:43

  Hello, Check to see if an error_log file exists in the document root of the PHP script. If so, does it list any specific error messages related to the issue? Thank you.

  0
• 

  2Pro4u

  • May 24, 2018 22:52

  Nothing specific to this problem in the aggregators error_log. The strange thing is, I just recently switched to https myself, and I remember the whole reason I implemented this image proxy was because the site would call all these 3rd party images that weren't secure, and it would make my page show as only partially secure. Now, when I edit my code, and remove the image proxy script, and call the 3rd party images, I don't get this problem, instead the script doesn't pull the images. Could this have anything to do with the cpanel updates or was the https standard changed recently that would have affected this? As far as I know, I have no other code that should be filtering these non-https images, yet now, my aggregator page is *staying* fully ssl, despite not using the image proxy script any more. Whatever it is, it's doing the ssl checking before that image proxy script can get to it. So the server has already deemed it not to be used, before the image proxy script could convert the image to https. Basically my aggregator went from loads of images, to far less, and it happened roughly right after the last two cpanel updates. Any ideas on if the last two cpanel updates could have affected this problem I'm having? (I'm also using CloudLinux if that makes any difference.) Thanks for any more help you can provide.

  0
• 

  cPanelMichael

  • May 25, 2018 17:06

  Hello @2Pro4u, Could you open a

  0
• 

  2Pro4u

  • May 27, 2018 06:30

  Do you mean allow a Cpanel support team access to my server? If so, I'm sorry, but that won't be happening. I have been able to narrow down the issue slightly, the backend of our script uses SimplePie, and while it use to be able to process images from an "enclosure" tag in an rss feed, it now can no longer do that. While I don't know the method or process in which SimplePie accomplishes this, I can tell you that I've not modified SimplePie, and I'm quite certain my code that uses SimpePie wouldn't have been altered in a manner that would affect this. One of Cpanel's last two updates I believe have affected this. Can you tell me, is there a way to safely rollback Cpanel versions, to test the theory that one of these two recent Cpanel versions are the culprit of the problem?

  0
• 

  Infopro

  • May 27, 2018 10:20

  Can you tell me, is there a way to safely rollback Cpanel versions

  
  You cannot roll back to earlier cPanel versions. What you might want to do is check with the developer about the script. github.com/simplepie/simplepie/issues I'm not sure if this is related to your issue but I did find this bug for example: github.com/simplepie/simplepie/issues/539

  0

Please sign in to leave a comment.