- Siteground.com trusted by 250,000 domain owner.
- Unlimited web space, unlimited bandwidth transfer.
- 24/7 support, email support, phone support.
- Free domain name.
- Unlimited email accounts, unlimited FTP accounts.
- Unlimited MySQL database. Ecommerce ready hosting.
- Siteground Coupon : Siteground Discount $1.95/month
- Siteground Coupon : Siteground Discount 40% Off
** This Siteground Review is hosted with Siteground Hosting.

   

Our wordpress blog hosted with siteground hosting can not be automatically updated via the wp-admin update core service. And its not a first time issue, we have faced this problem numerous time, and the wordpress version failed to get updated. From the wordpress error, we learn that this is to do with the directory permission and access issue. We have tried few configuration to fix this problem, but no luck after all. Appearing that siteground hosting for wordpress blog hosting is harder than we expected, there might be some server issue.

We have wordpress blog setup at few other cpanel web hosting and not face this problem, for example is bluehost, hostmonster, hostgator, justhost hosting, and others.

500 – Internal Server Error
This is a temporary server error.
Please try to reload the webpage later.

If you are the webmaster of this site please log in to Cpanel and check the Error Logs. You will find the exact reason for this error there.

Common reasons for this error are:

* Incorrect file/directory permissions: Above 755. In order files to be processed by the webserver, their permissions have to be equal or below 755. You can update file permissions with a FTP client or through cPanel’s File Manager.
* Incorrect Apache directives inside .htaccess file. Make sure you have not specified unsupported directives inside the local .htaccess file. Such include PHP settings and Apache module settings.”

Siteground Coupon $1.95

One Response to “Wordpress update core failed can not create directory”

  1. George Says:

    It’s because some of your files and folder have 777 perms and SiteGround are security maniacs :) Change them to 755 and you will be fine:)

Leave a Reply


10 Most Recent Posting