brainstuffch
New Pleskian
We have a Plesk Licence on our hosting server. But this is probably a OEM licence (support by the provider of the Server) or a stolen licence.
The hosting Provider has installed Plesk with a lot of false ports and with a lot of bugs.
But the hosting Provider says that we are the admin of our server, and we must know the open port numbers and other problems.
By example, we can not install our own name servers ... the hosting Provider says the problem is on the side of the registrar and the registrar says the problem is on the side of the hosting Provider.
Bevore we had this account, we had an other account on this hosting Provider where Plesk worked correctely with our domain registrar.
We think, that Plesk has a big interest to help us to sole the issue ... and Plesk must do all his possible to stop the betray from this hosting Provider.
We need a direct contact with the plesk support and then we give PLESK an access to the account, and then they install plesk correctely. And Plesk must also inform the hosting Provider that PLESK can not accept, that the good reputation of Plesk is in danger.
PLESK has a verry poor reputation .... we think this is due to the fact that such OEM Licences has a very stupid support.
I find that PLESK works very fine if it is correctely installed. It seems to be the only big problem, that PLESK is often installed by stupid people.
When a hosting Provider install PLESK he does open all needed Ports and then PLESK install without any problem the domains. And if the domains work with her own name servers insteat of the name server of the registrar there is no need to modif the registrars name server. The only thing to do is to say on the interface of the registrar, that the domain points to NS1 and NS2 .xxxxxxxxx.com No need for A Records and other things. When the user installs a domain on a server with PLESK, Plesk asks for the domain Name and the name servers and then all is installed automatically if PLESK is correctely installed.
Thanks
brainstuff
The hosting Provider has installed Plesk with a lot of false ports and with a lot of bugs.
But the hosting Provider says that we are the admin of our server, and we must know the open port numbers and other problems.
By example, we can not install our own name servers ... the hosting Provider says the problem is on the side of the registrar and the registrar says the problem is on the side of the hosting Provider.
Bevore we had this account, we had an other account on this hosting Provider where Plesk worked correctely with our domain registrar.
We think, that Plesk has a big interest to help us to sole the issue ... and Plesk must do all his possible to stop the betray from this hosting Provider.
We need a direct contact with the plesk support and then we give PLESK an access to the account, and then they install plesk correctely. And Plesk must also inform the hosting Provider that PLESK can not accept, that the good reputation of Plesk is in danger.
PLESK has a verry poor reputation .... we think this is due to the fact that such OEM Licences has a very stupid support.
I find that PLESK works very fine if it is correctely installed. It seems to be the only big problem, that PLESK is often installed by stupid people.
When a hosting Provider install PLESK he does open all needed Ports and then PLESK install without any problem the domains. And if the domains work with her own name servers insteat of the name server of the registrar there is no need to modif the registrars name server. The only thing to do is to say on the interface of the registrar, that the domain points to NS1 and NS2 .xxxxxxxxx.com No need for A Records and other things. When the user installs a domain on a server with PLESK, Plesk asks for the domain Name and the name servers and then all is installed automatically if PLESK is correctely installed.
Thanks
brainstuff