I mostly work with cPanel/WHM but, I have to work with Plesk for just one client of mine. He's on Plesk becoz I came to know Plesk worked better on 256MB VPS than cPanel in the early days. Hence, on my recommendation, he is on Plesk on a 512 MB Memory VPS till now for all these years.
I wonder how tedious it might be to convert from Plesk to cPanel? The client basically uses Joomala + vBulletin and runs forums as of now.
Also, which CP will perform better on 512 MB VPS - Plesk or cPanel.
I have server that has a SINGLE customer on it - this is not economical to run under PPA - how do I remove it from the PPA management and not disrupt the current site/email on it?
The plan is to run it on webmin - there is no way it can justify PPA for 1 site.
I've got a customer that has a website at hisdomain.com . He created a subdomain called dev.hisdomain.com for the new version of his website. Now he wants to take it live. Had he created dev.hisdomain.com as a subscription instead of a subdomain, it would have been easy to "rename" the old site to old.hisdomain.com and then rename the new site to the current name.
Am I going to have to move all the files around at the command line or is there an easier way to switch around the sites? The server in use is CentOS 6.6
I am currently using phpdotnuke for a site, and have a forum linked to it supplied by activemodules.com. I would like to move to a non-cms site and something like vbulletin, so want to convert the forum db from MSSQL to MySQL - and hopefully keep all the posts and login data!
As a complete novice to that process, is there any pointers out there in terms of reading material, non-command line software etc I can use? Has anyone done this conversion, and what are the dangers?
I am wondering if there is an easy way to convert apache to nginx on my Plesk 12 server. Ideally, I would like to save all my hosts without having to re set them all up. I have been searching online, but haven't found a simple way to do so.
I have a website that was running fine for a month or two until my host recently changed some settings on the server, and now it shows a bunch of errors. I contacted the host and they said >
"To avoid the errors, please do not use disabled function. If you need such functionality, you can have your own php.ini on your root http folder containing only necessary option"
Since I'm not a programer, I have no idea what they're talking about. So, I asked them how to do that, they're reply of course was>
"Please consult with the script writer on how to convert ini_set function in your code to php.ini seting. As the script is not encrypted, you can do it with commenting all ini_set calls and write a substitute on php.ini (Create php.ini file in webroot folder)."
I tried to contact the developer, but it appears he has gone MIA! So, now I am left with no clue how to fix the website, so I turn to you guys!
The website is [url]. You can see the errors in the header, but I'll post them here as well>>
"Warning: ini_set() has been disabled for security reasons in /home/buymydom/public_html/includes/global.php on line 3
Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/buymydom/public_html/includes/global.php:3) in /home/buymydom/public_html/includes/global.php on line 32
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/buymydom/public_html/includes/global.php:3) in /home/buymydom/public_html/includes/global.php on line 32"
My question is, How do I convert ini_set function in my code to php.ini?
I'm facing problem with latest Apache 2.4.9. Previously we used Apache 2.4.7 ​version which supports DER SSL certificates. But Latest Apache(2.4.9) is not working with DER SSL certificates. I have to convert DER certificate to PEM format to start the Apache server. Am i missing anything ? Is DER certificate not supported in Apache 2.4.9 ?
I'm having a small dilemma at the moment as I have never admined a server via SSH only, though following a well written Perfect Server guide might help. As the topic states, would you recommend using a control panel to manage a dedicated server (for one person), or would you recommend using SSH management and setting up the services there?
I have never tried to perform the latter option but would really like to as I'm a complete Linux noob Ok well maybe not complete, I know more than most people do, but I'm far less proficient than those who actually use and like the system on a daily basis.
I'm thinking of taking out a new VPS but am unsure of whether to go with CPanel or Plesk.
I have used CPanel with WHM & it works really well. I have read that it does take up a lot of memory & as I'm going for a low end VPS - with 348mb to start with, I was wondering about Plesk, which is also offered by the hosts.
Is Plesk more memory-friendly?
Does Plesk operate in the same way as CPanel - offering Admin as in WHM & easily configurable client panels?
as a newbie moving up to VPS hosts from shared hosts. I'm looking for a bit of advice on which would be the best to go for.?
i have used cPanel before & found it very easy to use, BUT have never used Plesk, only via their web site using the Demo panel & also found it easy to use... what im looking to host is a small community forums & hopefully a small game server on the same host to run ET "Enemy Territory"
Ive been told that ET can be installed on cPanel easily but when looking at the demo of plesk in Modules, it shows a couple of game servers but not ET. could anyone please say if plesk is also capable of running this game or not.. also as a newbie which of the 2 control panels would be the best for me.?
Is there a way to transfer plesk accounts to cPanel platform? Things to note, that I do not have root access, but do have WHM as it is a reseller account.
I have read that cPanel consumes a constant 258MB of RAM. That seems like a huge overhead for the convenience it provides.
Plesk consumes less? How much?
This is to run LAMP -- so what I want to know is how much RAM is the minimum needed to run LAMP under different control panels. (The bandwidth of the sites to be run is low.)