Frequently asked questions

How does PHP 5.6 work on Domainnameshop?

This FAQ entry has information aimed at both non-technical and technical users and developers.

Between 2017-01-15 and 2017-06-01, we upgraded all customers who hadn't already performed the upgrade from PHP 5.5 to 5.6 already. This upgrade was free of charge.

PHP 5.6 was default for all webhotels Medium, Large and Extra Large created on or after 2017-01-15 until May 2018.

Between 2018-09-01 and 2018-12-12, we decommissioned support for PHP 5.6.

2018-12-12, we automatically upgraded all webhotels med PHP 5.6 to 7.2 for customers who had not yet upgraded to 7.1 or 7.2.

Until 2018-12-31, Customers had the option to temporarily downgrade to PHP 5.6 to update their software.

The documentation below is retained for historical reasons.

If you experience problems you think are caused by our configuration or deficiencies with our servers, please first check that your software works with PHP 5.6, and that the tips below don't work out for you, before you contact our support.


When will PHP 5.6 enter regular service?

PHP 5.6 enters regular service after 2017-01-15.

What does this FAQ entry answer?

This page tries to cover some of the questions we think you may ask, or which we have received questions about. We will update it as necessary.

What is the difference between the old and new webservers?

  • The operating system on all new webservers are running Debian 8 Jessie, up from Debian 7 Wheezy.

  • Apache is upgraded from Apache 2.2 to Apache 2.4. If you are running your own .htaccess-file (especially accesscontrol) on your webhotel, this may need to be upgraded. Check Apache-documentation for more information.

  • We are now using uWSGI to run PHP, instead of suPHP (mod_suphp).

What is the difference between PHP 5.5 and PHP 5.6?

There are no big changes between PHP 5.5 and PHP 5.6 on our servers. Check PHP-documentation for detailed information about the changes.

The PHP-configuration on 5.6 is nearly the same as 5.5. Notable changes:

  • We are using the MySQL driver mysqlnd (MySQL Native Driver). If you have an old php.ini, you may therefore get an error message about "mysql connection", "mysql driver", or "mysqli driver".
  • In PHP 5.6, the standard charset (default_charset) is changed from being undefined, to UTF-8. This can have consequences if the HTML-code on your webpages is configured with another charset in the <meta>-tag, when the charset in PHP will have precedence.
  • User-created php.ini files must lie in the root-folder of the users home directory, or docroot (the directory that is used for cloaked www-forwarding).
  • Changes made to .user.ini and php.ini will not get registered immediately anymore, it will take about 5 for .user.ini and 30 minutes for php.ini files.
  • IonCube Loader and Zend Guard Loader can be activated from the control panel for your webhotel. It will not be possible to use your own php.ini if you activate these services. This is a preferred option compared to using user-created php.ini files and other additions.

Which applications/services will have trouble running on our PHP 5.6 webservers?

Most programs and additions that ran on PHP 5.5, will run on PHP 5.6 as well. Check with your program provider to make sure your software is supporting PHP 5.6.

You may see an error message about MySQL, "mysqli" etc. if you have an old php.ini, this file must then be removed.

Regarding self-developed code, check PHP-documentation for what changed that is not backward-compatible with PHP 5.6.

If you are running self-written modules or additions in PHP 5.5 you will most likely have to upgrade them to be compatible with PHP 5.6. This includes (in most cases) IonCube Loader and Zend Guard Loader. Support for IonCube Loader and Zend Guard Loader is recommended to be activated via the control panel for the webhotel.

Can I switch back to PHP 5.5 if PHP 5.6 does not work?

No. PHP does not apply security updates for PHP 5.5 anymore. This means we can not support and run PHP 5.5 on our servers any further.

Can I test/use PHP 5.6 on SSH?

Yes. You can use as long as we offer PHP 5.6. To test PHP 7, use

How long will you support PHP 5.6?

We will support PHP 5.6 until 30 November 2018. If you don't upgrade yourself, webhotels with PHP 5.6 will automatically be upgraded 12 December 2018.

My PHP-program is not working. Why?

Check How can I see PHP errors/debug PHP code? for additional help.

If you are using WordPress or Joomla, you can read more about errors/debugging about these systems here.

Known upgrade issues

If you are experiencing problems after upgrading, check this list of common problems and solutions.

"Error establishing a database connection"

Delete your old php.ini.

"The mysqli extension is missing"

Delete your old php.ini.

Silverstripe does not work

Delete the folder silverstripe-cache.

"Internal Server Error - The server encountered an internal error or misconfiguration and was unable to complete your request"

This is normally caused by invalid .htaccess-rules after upgrading to Apache 2.4. Try removing the .htaccess file. If this works, check your file against in .user.ini

Custom ErrorDocument does not work for PHP files, but works for other files

All filenames ending with .php are handled by uWSGI, Apache's ErrorDocument will never apply for such files.

See also:



© 2019 Domeneshop AS · About us · Terms · Privacy policy