16/01/2017 All domains with a valid DNS record have now been shifted to the new server. As from the 27th of January 2017 the old […]
All domains with a valid DNS record have now been shifted to the new server.
As from the 27th of January 2017 the old server will cease to exist.
[su_spoiler title=”In a nutshell Help” style=”fancy”]
We are trying to email people after your A/C is shifted
If you are having issues please don’t keep trying to access your emails otherwise the new server may block you.
See if you can access your webmail
If you can access your webmail that means you are connected to the new server.
If you are using secure email settings make sure that on your email client (*1):-
sv3.nzhost.net.nz please change to mail.yourdomain.xxx (*2) or sv5.nzhost.net.nz
secure2.nzhost.net.nz please change to mail.yourdomain.xxx (*2) or sv5.nzhost.net.nz
(*1) Email Client is the software you use to access your email example Outlook, Thunderbird, Windows Live Mail etc.
(*2) Note mail.yourdomain.xxx please change to your domain example mail.nzservers.com
More info on mail settings
How one person resolved SMTP issues using outlook:-
“When selecting the pop protocol the outgoing SMTP port was automatically selecting port 25 with no encryption. I just had to change the port to 465 and select SSL as the encrypted connection in the advanced tab. Also the outgoing server tab I had to tick “My outgoing SMTP requires authentication and select “use same settings as incoming”. As an added measure I flushed and registered the dns settings. Hope this helps out others as well” – Thank to Ravneil Lal Systems Administrator Ba Motor Parts Ltd
Note:- change the incoming and outgoing email servers to sv5.nzhost.net.nz if you are having problems as this will bypass any caching issues.
Although Auto should work with secure SMTP setting, SSL should work as well.
With Outllook make sure you select ‘Finish’ to save the changes.
Make sure your SMTP authentication is set correctly – click here for help
How can you check you are on the new server?
If you see the IP 184.108.40.206 you are on the new server
If you see the IP 220.127.116.11 you are on the old server
If you get really stuck please send an email via your ISP or Gmail/Yahoo/Hotmail etc
You can text me on 0274437083 and text ‘Help emails domain yourdomain.xxx’ please include an alternate email address with your text.
Please check on http://whatsmyip.org and email/text back the IP you see at the top to email@example.com or firstname.lastname@example.org
We have to change some old concepts to keep in pace with market trends plus security issues.
Change always comes with some teething issues.
I know technical jargon is loathed by some. If you don’t read this then the issues will surface reasonably quickly once your site is shifted over.
If nothing else please read about emails.
If you do not know how to access your CPANEL now is a good time to find out how.
http://yourdomain/cpanel is the best way to access your CPANEL
(please replace yourdomain with your own domain name)
Most of you will not have an issue.
If you use secure2.nzhost.net.nz for your mail server your email client will have issues once your site is shifted over.
If this happens to you simply use sv5.nzhost.net.nz in place of secure2.nzhost.net.nz or simply use webmail until your resolve the issue.
Webmail is accessed by using http://yourdomain/webmail
For those using the Gmail interface, you will need to know your email password when changing the mail server.[su_accordion] [su_spoiler title=”More Information on Emails” style=”fancy”]
The current server allowed people to use secure2.nzhost.net.nz as a SMTP and POP3 server for SSL sites to avoid the warnings given by some email clients.
NZServers attached this certificate to the mail servers to allow a signed certificate to work with emails and to allow connections to GMAIL using a signed SSL certificate.
Finally, CPANEL some time later provided a complimentary SSL certificate provided by COMODO assigned to sv3.nzhost.net to get around the warnings issued by some email clients and accessing CPANEL.
When your domain has been shifted you may have issues with using secure2.nzhost.net.nz.
You can use this link to see if your domain has been shifted over
Enter your domain name only and hit the DNS lookup button
If you see an IP address 18.104.22.168 you have been shifted to the new server
If you see an IP address 22.214.171.124 you are still on the old server
When your site is shifted over please use sv5.nzhost.net.nz as a mail server for SSL conections.
To access Cpanel :–
https://sv5.nzhost.net.nz:2083/ or http://yourdomain.xxx/cpanel
Do not use https://sv3.nzhost.net.nz:2083
This section is mainly for developers.
The default PHP version is 5.3 for reasons of minimising problems when shifting sites.
You can very easily shift to a higher PHP version using your CPANEL
If your website was developed by someone other than NZServers please share this link with your developer.
[su_spoiler title=”PHP History Current Server” style=”fancy”]
The existing server runs PHP as a compiled module under Apache known as Mod PHP or PHP DSO.
Running PHP like this is very fast, the only downside is PHP when it writes files to the server has to do this as the Apache user called ‘Nobody’.
There are different ways or running PHP usually at a cost of speed where PHP writes and reads files as the site owner instead of Apache.
Products like WordPress normally adhere to rules, except some plugin developers who depart from the rules creating permission issues.
Having PHP running as the same user makes it a lot easier using software applications like WordPress.
Switching over to a new way of running PHP makes the transition of existing websites a challenge which rely on PHP.
For PHP sites there will be some downtime as permissions and users have to be modified quickly.
The ownership of users is only possible as an administrator known as root user making the process slower than usual in getting sites across.
PHP versions from 5.3 thru to 7.1 are available
The PHP version is selected using the MultiPHP Manager
Editing PHP information is done by using the MultiPHP ini Editor
Under Mod_LSAPI these files are ignored unless they exist in the public_html folders.
Any attempts to modify PHP values can be done using .htaccess or you have controls on the servers new CPANEL to modify certain PHP values.
Using .htaccess the changes apply recursively where a PHP.INI files is only applicable to the folder the php.ini file is located.
[su_spoiler title=”More info php.ini files” style=”fancy”]
php.ini file directive
magic_quotes_gpc = Off;
Under .htaccess will become:-
php_flag magic_quotes_gpc off
php_flag magic_quotes_gpc off
Warning if you use values like
php_flag register_globals Off
this is valid for PHP 5.3 only.
A value like this will create an error 500 error if this value is used in PHP 5.6
Sites which are shifted over and an error 500 is created will be shifted to PHP 5.3 until the error is resolved.
PHP MultiPHP Editor
You can select the home folder of select the domain which is the public_html folder
There is an editor mode where you can manually enter values.
Note enter valid entries and not deprecated values
This is like a firewall which looks for unusual activity used by sites accessing your web site.
Over time we have created exceptions for some users.
As everything is new we will not be applying the same exceptions unless we have to.
We will be transferring over the old whitelist over the new server
Your new CPANEL will allow you to select the PHP version you require.
[su_spoiler title=”Cpanel More Info” style=”fancy”]
Select the MultiPHP manager
Please note if you are using .htaccess or php.ini files o modify values make sure these are valid before the site is shifted over.
For some sites expect some downtime, especially very large sites.
The plan is to shift the smaller sites first, leaving larger sites to later.
As we are shifting to a new platform and different method of handling PHP so there could be some teething errors.
Propagation is based on a test using a Linux command using Googles DNS servers.
Once we see the correct IP mainly 126.96.36.199 we know the site using Googles DNS servers has updated and the site has migrated.
During this time (January 2017) we would ask you to minimise any changes while this transition takes place.
Any permissions above 755 will cause the site to crash
The PHP user nobody become the site user.
We will do our best to resolve these once the site is shifted.
The existing version is 5.5 the new version is 5.6
They may be exceptions where we have to reset the MYSQL user password
If this happens we have to locate the file where this is located and reset the password.
Centos versions 6.0 or higher allow SSL certificates to use a shared IP.
This is the default now for the new server.
Anyone on a dedicated IP will shift back to a shared IP.
The SSL trend is increasing being adopted as a preference by Google in search results.