As I read, when Plesk and WHMCS are in the same server, you may have 502 bad gateway errors when creating an account through WHMCS..Page not Found/Timeout/502 Bad Gateway error creating accounts with Plesk 10+..By default Plesk 10 and above performs a forced restart of apache when an account is created or suspended which causes WHMCS to lose connection to the server, and if your WHMCS is on the same server, you will also lose connection to WHMCS at the same time.
In order to resolve this please refer to the following knowledgebase article for instructions on configuring Plesk to perform a graceful restart instead: URL..
But when I activate nginx in Plesk the 502 bad Gateway problem comes back.Is there an option to activate Nginx graceful restart in Plesk?
I run a virtual server (Ubuntu 12.04, Plesk 12, Postfix 2.9.6) using plesk to manage multiple domains. The server address is server.domain1.com. I use plesk to also manage domain1.com regarding all services, including DNS and mail.
What I just found is that postfix sometimes issues the following warning:
server postfix/trivial-rewrite: warning: do not list domain server.domain1.com in BOTH mydestination and virtual_alias_domains
The essential part of my main.cf is: myhostname = server.domain1.com mydestination = localhost.$mydomain, localhost.localdomain, localhost virtual_mailbox_domains = $virtual_mailbox_maps, hash:/var/spool/postfix/plesk/virtual_domains virtual_alias_maps = $virtual_maps, hash:/var/spool/postfix/plesk/virtual virtual_mailbox_maps = , hash:/var/spool/postfix/plesk/vmailbox virtual_transport = plesk_virtual
And /var/spool/postfix/plesk/virtual_domains contains amongst others:
I do not have any issues with receiving or sending e-mails right now, but would like to get rid of the error message however.
Could it be the problem that postfix automatically sets mydomain to $myhostname with skipping the first part (i.e., mydomain is implicitly set to domain1.com)? Should I manually set mydomain to server.domain1.com instead? Any other recommendations? Since mydomain seems to be used in multiple options [URL] ..., I wonder what I might destroy with changing this? As all mail services run without any further troubles at the moment, I don't want to break this...
As I assume that quite some people use a plesk-based server to manage the domain to which the server itself belongs to, I would assume that there should be a general fix/check to updated mydomain accordingly?
I am new to Parallels software, more specifically Parallels Panels. I have installed a trial copy of the software on my Windows 2008 R2 SP1. This is a Dedicated machine with no other users on it. I presume installation of Panels was successful because I can log in and see the admin control panel. I created a customer with success. I am now trying to create a subscription using the default service plan. After entering all the appropriate info on the new subscription page and submitting it, a few moments later I receive the following error:
Error: Filename: ?C:Inetpubvhosts estyourwebhostingprosite.comhttpdocsweb.config Error: The configuration section 'system.webServer/rewrite/rules' cannot be read because it is missing a section declaration In module Exception type: System.Runtime.InteropServices.COMException at Microsoft.Web.Administration.Interop.AppHost
I'm trying to create a new domain extranet.ondes.fr to have a forward on an another website.
And have this error message : "Erreur: Failed domain creation: Impossible de mettre à jour les données du domaine : Failed mail post-configuration: Can't create mail domain servie: mail_Facade->createDomain() failed: mailmng failed: MEAOPO.PostOffice.AddPostOffice failed for name extranet.ondes.fr [extranet.ondes.fr]"
recently i created a domain subscription with 3 alias domains. Thanafter i created a sub domain to a folder in the main domain. At first all went fine but after deleting the alias domains subdomains ans domain supscrption to register all the 4 domains each seperately a problem accured and i cant add any subdomain to none of the 4 domains. registering the domains themselves as individual domain works for each one perfect. But as soon as i try to add a subdomain on any of that 4 domains i get an error that the dns data could not be updated. As it looks like there is still some codes in the plesk database that links to 4 domains in any kind together and prevents me to creste a subdomain.
How can i manually remove all the domains subdomains and alias domain garbage from the plesk database. I use windows version of plesk panel 11.0.9 on windows 2008 server datacenter edition. I have good skils in IT but im not familiar with mysql and plesk. how to remove the records from plesk Mysql database. Command line commands internal commands locations that have to be altered and all other needed steps.
I recently upgraded to version 11.0. Since the upgrade, I am not longer able to to create Sub-Domains. I did this all the time with version 10x with NO issues whatsover, but now I get the following error when trying to create a subdomain:
I have two servers, a plesk 11 installation and a plesk 12. Running Centos.
On the plesk 11, set up by others, I have a nameserver running NS1.xxxx.net & ns2.xxxx.net point to the IP of the server.
I want to create a nameserver on the plesk 12 -- can't see how to do this. Is there a nameserver setup function in plesk 12?
More advanced question:
The domain name xxx.net is hosted at 1&1 where I have put the IP of the plesk 11 server in the A records for ns1.xxxx.net and ns2.xxxx.net. I have pointed ns3.xxxx.net and ns4.xxx.net at the IP of the Plesk 12 server -- as I would like to use these addresses for consistency. If necessary, I'll use ns1/ns2.yyyy.net.
I have noticed that for each new subscription I create Plesk automatically creates an FTP account. Further; I cannot delete this. (It seems the Remove button would allow me to delete additional FTP accounts but not the one added when the subscription was created).
I would like:
1) To delete these system created FTP accounts
2) To prevent it doing this in future. I would like to create subscriptions without FTP accounts.
I'd prefer to do it this way and leave the FTP server running. However; I am wondering about disabling FTP access altogether if I have to. I do use SFTP. I'm afraid my Linux knowledge is so limited I don't know if SFTP uses the FTP server; so if I turned off the ftp server whether that would prevent sftp access?
The motivation for doing this is that while I have 'customers' and subscribers in fact I am the only user and will transfer files to the server by SFTP and then move them around the server logged on via SSH. Since I'm not using FTP it seems sensible not to have all these accounts floating about.
Have some very important questions regarding changing plesk ports and creating full backups.
1. When changing plesks port number, what exactly will it effect? Will it effect auto updates, etc.?
2. When creating a backup, I'd like to backup the entire server to rollback at anytime when changes are made to core files, is this possible?
3. With backups, somehow I'd like to schedule backups to possibly make nightly copies to an external hard drive on my computer for a fail safe method just in case the server happens to crash and I'd need to restore to another server/service. How would this be possible?
I have following Warning when creating a new Domain inside a Subscriptions:
I found this Article: [URL] .....
But in my case this does not solve the Problem.
1> All permissions are right. 2> When I type command '/usr/local/psa/bin/repair --restore-vhosts-permissions' i get the answer 'Directory permissions were successfully updated.' 3> The Order of Webuser and FTPUser (as described in the article) could also not be the problem, because in my case there is only one user (There is only Webuser and no FTP-User.) 4> When typing '/usr/local/psa/bin/repair --update-vhosts-structure' I get the following error 6 times each:
Unable to update the structure of the home directory: an unexpected error has occurred. update-vhosts-structure failed: mkdir: cannot create directory `./webroot.kk-bits.com/logs': File exists ERROR: Cannot relink logs. Target directory '/var/www/vhosts/webroot.kk-bits.com/logs' is in invalid state.
To get the error 6 times seems to mean, that i have this problem with 6 Domain.
I've checked the firewall and FTP is allowed incoming, I added the passive ports to the firewall. Plesk shows the user in active connections, but when I connect to any domain I get an error that its not able to retrieve the directory. I am not sure if plesk just doesn't know what the directory is or if the main config messed up on the domain or sites level. I am running Plesk 12 on CentOS7.
I understand it is not possible to move a domain to another subscription, or to create a new subscription with an existing domain name.The problem I have is I wish to use a different IP address for a domain within a single subscription. I need to do this to establish SSL cert on one of the domains.
I have multiple domains on a single IP address and many require SSL Certificates.
I have enabled SNI in /etc/psa/psa.conf so it now says "SNI_SUPPORT true" as it was originally set to False. Setting this to TRUE then enabled the SSL option in 'Websites & Domains'.
I then purchased and installed the SSL Cert and activated it in the domain settings. On a dedicated IP address, this would work.
When I checked the certificate. it was not using the assigned SSL cert, instead it was using the Servers default certificate (plesk) that is assigned to the shared IP address.
When I check, I get the error message: "[warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name"
I then rebooted the server and it made no difference. I changed the domain to a spare dedicated IP address, and the SSL Cert was certified correctly (it used the correct SSL Cert). When I changed it back to the shared IP address, it reverted back to the shared IP address' SSL cert. So the new SSL Cert was being ignored.
For info: currently running 11.0.9 on Centos 5 and I'm testing this with latest IE, FF, Chrome so it accepts TLS Server Name Indication.