All Activity

This stream auto-updates     

  1. Yesterday
  2. One correction here as all new accounts are now put on our CloudLinux 7 servers which uses 5.16.3. Only our CloudLinux 6 servers which all will be migrated to CloudLinux 7 before the end of the year are running 5.10.1.
  3. a bit outdated, but better than could be, I guess... ok, thank you for reply!
  4. Hello! The perl version on our shared/cloud web hosting plans would be v5.10.1
  5. Last week
  6. What is the Perl version currently on shared hosting accounts?
  7. Earlier
  8. No problem! Glad it is solved
  9. Removed the entry as Fowler suggested and ran phpinfo which indicated version 7.4 was running. I will consider things fixed, thanks for the assistance!
  10. Thanks Brian, will give that a try. Edit: Can somebody on Admin side fix the spelling in the the post title (upgade), that will drive me crazy! I don't see anywhere for me to edit it. Sorry about hat!!
  11. The missing PHP module (GD) can be enabled on your PHP version through the same interface used to change the PHP version in cPanel (Select PHP Version). You should see GD listed with a radio checkbox next to it, just need to enable that and the error should disappear. That said this likely did not / will not have impact on performance as it's just for image manipulation.
  12. Just an FYI on how I fixed this. Identified the images in question using the tool as Brian suggested: http:// https://www.whynopadlock.com/ then had to simply login to WordPress dashboard through secure (https) connection and re-up the images in question. Thanks
  13. Hi there, I posted previously about issues with which php version I was running and if my solution was viable. Still working on that one. But since then I have notice that the Site Health Status within WordPress dashboard indicates performance problems which have occurred since I changed the php version. I have a clone of my original site before changing the php versions and Site Health Status on that only indicates an issue running an out of date version of php. Anyway, screen shot provided, insights appreciated. Thanks!
  14. Thanks Fowler, I will give that a try. I have also discovered an issue with the "site health status" through WordPress dashboard, which has changed since I changed the php versions. I will make a new post for that so it doesn't get buried here.
  15. As no one official is helping you, I will advise. Personally I don't use the PHP selector options in cPanel as, like you have found, they are confusing and needlessly messy. Like two versions of each PHP version... ea and alt. All I do is at the top of the htaccess file for each site is add the following line (for PHP 7.4 in my case) AddHandler application/x-httpd-php74 .php .php5 .php4 .phtml For version 7.3 for example, just change the 74 to 73 for example. For php 5.6, change it to 56. In your case though, what I would do is remove the cpanel generated code your posted # php -- BEGIN cPanel-generated handler, do not edit # Set the “ea-php56” package as the default “PHP” programming language. <IfModule mime_module> AddHandler application/x-httpd-ea-php56 .php .php5 .phtml </IfModule> # php -- END cPanel-generated handler, do not edit And then create a phpinfo file in the same directory and Wordpress and see what version it shows. https://make.wordpress.org/support/handbook/appendix/creating-a-phpinfo-page/ This will show the version you are using. If it says a version you don't want to use, try my method above rather than trying anything through these version selectors. Hope this helps
  16. So everything seems to be working with my fix above. Can anyone confirm this is a reasonable fix? Also, wondering about that entry in the .htaccess? Doesn't that switch the php version back to 5.6? Does that increase security vulnerabilities? Thanks,
  17. I figured out a fix but I don't know if it is the correct one! I tried to enable mysqli extension for 7.3 but it wouldn't save. I tried on 7.4 and it did save. Then I went to the multiphp manager and selected alt-7.4 (ea-7.4 not avail.) That resolved the error but was it the correct way? Thanks,
  18. I noticed this in the .htaccess: # php -- BEGIN cPanel-generated handler, do not edit # Set the “ea-php56” package as the default “PHP” programming language. <IfModule mime_module> AddHandler application/x-httpd-ea-php56 .php .php5 .phtml </IfModule> # php -- END cPanel-generated handler, do not edit I am guessing that is the problem?
  19. Good afternoon! Thanks for the speedy reply as always! I switched to 7.3 under "Select PHP Version" but when I checked the site in question under "MultiPHP Manager" it was still showing as 5.6. When I changed it to 7.3 under "MultiPHPManger" I received an error regarding MySql extension (see attached). Also, note screen shot of "MultiPHP Manager". 7.4 is only available as "alt" and not "ea". I thought I had read that "ea" was preferable. I switched site back to 5.6 under "MultiPHP Manager" so site is running again. Under "Select PHP Version", the default is set to 7.3. The site is running one of the default WordPress themes (recently updated) and no plugins at the moment. Would I assume then that this theme is not compatible? Or is something else going on here? Thanks again!
  20. Good afternoon! You can modify your accounts PHP version directly through cPanel using the "Select PHP Version" interface. We currently offer up to version 7.4, and we recommend running version at least 7.3 assuming your software supports it. You mentioned running WordPress which does run fine on both 7.3 and 7.4, so assuming your plugins and themes are compatible you should be safe to upgrade. If needed you can revert back to an older version if you do experience issues with your sites after changing. Once that change is made all sites under your account will start using that new version, including the new WP site you're building. As for automatically changing PHP versions once they're released unfortunately that's not a feature we can offer at the moment so you would still need to manually change once newer versions are made available.
  21. I hadn't logged into my Wordpress dashboard for one of my sites in a while and noticed the "PHP Update Required". It is running on a very old version: 5.6. While I know it redirects automatically via CloudLinux, should I still update it manually to a newer version? There is nothing extraordinary about the site, just wondering what hazards I might encounter. I am aware that some extensions are not available in newer versions but I don't know much about PHP and don't want to break anything. Also, I will be building a new WordPress site shortly, how do I ensure it uses the newest PHP version and is there a way to have it update automatically when a new version is released? Or would this not be a recommended idea? Any input would be greatly appreciated. Thanks kindly!
  22. These no longer appear to work?
  23. Thanks Brian, that is very helpful! It identified one of the images as having an insecure url. Now to fix it. Thanks again, Brian
  24. This usually happens when your sites code/resources link to http elements instead of https -- the SSL certificate itself is fully secure/trusted but the browser won't reflect that due to use of http, usually for images or third party scripts/libraries. If you enter your site into the tool at https://www.whynopadlock.com/ it will identify those elements so you can update them accordingly.
  25. Good day, I have been playing around with SSL to see if it was working on my site and found that while https works, there is a yellow exclamation point. When I view “more information” and then “view cerificate” everything looks fine. Just wondering why this is? Thanks, Brian
  26. Usually this happens if whois/ID protection is not purchased with the new domain registration. Unfortunately there are individuals out there who have automated the process of looking for newly registered domains, they then scrape the public whois details to obtain the domain owners email, and they'll then spam you with offers for web design, hosting, or other web related services. You can add whois/ID protection to the domain (assuming your TLD supports it) after registration which would prevent your details from being exposed on future whois lookups, if you wanted to do that our billing team can assist through our helpdesk.
  27. Right after I bought a new domain using one of my freshly created gmail account, I immediately received so much spammy messages. I wonder if anyone does experience the same thing? I wonder how can I prevent this?
  1. Load more activity