Update 5.0

The update to version 5 is mainly an update about the new Chinese language, a new basis OS upgrade and some major and minor function changes (check provider changelog). But we also did some cleanup for the CSS and icons in the user interface.

There are a few things to know and consider for updating the system. Please read carefully!

Important Upgrade Notes: Major OS upgrade

This update is making a major OS upgrade of your regify provider. The CentOS 6 system is updated to CentOS 7, which requires a few reboots and SSH re-logins. It also takes some more time than a normal patch updates (10 to 30 minutes, mainly depending on your system speed).

ToDo before upgrading

More RAM for the Virtual Machine

For the upgrade to work, the VM must have at least 2GB of RAM. If you do not yet have 2GB RAM assigned, you may want to shutdown the machine (shutdown -h now) and re-assign some more memory before you switch it back on and start the upgrade.

If you're using the NAGIOS capabilities

Please note that /etc/nagios/nrpe.cfg will be overwritten and nrpe will not run after the upgrade. You may want to make notes of the needed settings before upgrading.

If you're behind a loadbalancer

Please note that with provider V5 a websocket server was introduced for regibox. Even if we do not use extra ports, make sure that your load balancer supports it (eg does not cut long-term connections). If you do not offer regibox, you don't have to care about.

IMPORTANT: Read the dialogues during update!

If dialogues comming up during update, please READ them and follow instructions!

ToDo after upgrading

Icons

Many images have been replaced by font icons (a font containing icons instead of characters). We've chosen typeicons and it works great. By this, we also tried to make it much more easy for you to adapt the colors to your needs. Please check the Provider_customization article for further help and some CSS template. You can still use CSS to overwrite the icons with own uploaded ones. Please do with a skilled web developer.

If you uploaded your own images for customizing (eg grey ones), you very likely have to remove the CSS and the uploaded images after the update! Please check the Provider_customization article for further help and some CSS template.

Please understand that we can't offer detailed help on CSS customizing for free. If you like us to help you on CSS and customizing, please ask us for an offer about professional service by a skilled developer.

codeFooter.php

The update also tries to adapt the codeFooter.php file of your customization. The management of languages and flags has been enhanced and some code must be removed or changed to work. If the automatic update of this file failed, you will get some red ToDo warning in your web-administration main page. In this case, please reset the codeFooter.php to the default and make your changes to whatever it was before.

Provider-SDK access

The provider-SDK is now using IP whitelisting for any access by default. If you use the provider-SDK, you have to enter the incoming IP addresses in the Web administration at Provider settings -> Allowed IP-Ranges for Provider-SDK. You can enter single IP addresses, ranges and subnets. It is also possible to allow access from everywhere (*), but please use that option only if needed.

RAM for the Virtual Machine

Maybe you like to shutdown (shutdown -h now) and set RAM size back to what it was before (eg 1GB)?