[2016-03-28 22:35:52]
[2016-03-28 22:35:52] Checking the Plesk database using the native database server tools
[2016-03-28 22:35:52] .. [OK]
[2016-03-28 22:35:52]
[2016-03-28 22:35:52] Checking the structure of the Plesk database
[2016-03-28 22:35:53] ........................ [OK]
[2016-03-28 22:35:53]
[2016-03-28 22:35:53] Checking the consistency of the Plesk database
[2016-03-28 22:35:53] ...................... [OK]
[2016-03-28 22:35:53]
[2016-03-28 22:35:53] Checking system users
[2016-03-28 22:35:53] ............................................... [OK]
[2016-03-28 22:35:53]
[2016-03-28 22:35:53] Checking virtual hosts' file system
[2016-03-28 22:36:27]
[2016-03-28 22:36:27] There are files or directories with suspicious permissions in the
[2016-03-28 22:36:27] root directory of the domain 'immo***.com' ................... [WARNING]
[2016-03-28 22:36:27] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2016-03-28 22:36:29]
[2016-03-28 22:36:29] There are files or directories with suspicious permissions in the
[2016-03-28 22:36:29] root directory of the domain 'dyna***.at' ................. [WARNING]
[2016-03-28 22:36:29] To see more details, run the command in the verbose mode: plesk repair fs -verbose
[2016-03-28 22:36:32]
[2016-03-28 22:36:32] Repairing web server configuration
[2016-03-28 22:36:32]
[2016-03-28 22:36:32] Reinstall SSL certificates and set the default SSL certificate for all IP addresses? [Y/n]
[2016-03-28 22:37:38] Reinstalling SSL certificates ...................................
[2016-03-28 22:37:38] [OK]
[2016-03-28 22:37:38] Applying the default SSL certificate to all IP addresses ........
[2016-03-28 22:37:38] [OK]
[2016-03-28 22:37:38]
[2016-03-28 22:37:38] Repair server-wide configuration parameters for web servers? [Y/n]
[2016-03-28 22:37:45] Repairing server-wide configuration parameters for web servers ..
[2016-03-28 22:37:49] [OK]
[2016-03-28 22:37:49]
[2016-03-28 22:37:49] Update the file of sharing passwords and permissions of users according to actual information? [Y/n]
[2016-03-28 22:38:05] Updating the file of sharing passwords and permissions of users
[2016-03-28 22:38:05] according to actual information .................................
[2016-03-28 22:38:06] [OK]
[2016-03-28 22:38:06]
[2016-03-28 22:38:06] Repair web server configuration for all domains? [Y/n]
[2016-03-28 22:38:08] Repairing web server configuration for all domains ..............
[2016-03-28 22:38:15] [OK]
[2016-03-28 22:38:15]
[2016-03-28 22:38:15] Checking the usage of PHP handlers
[2016-03-28 22:38:23] .................................. [OK]
[2016-03-28 22:38:23]
[2016-03-28 22:38:23] Repairing the mail server configuration
[2016-03-28 22:38:23]
[2016-03-28 22:38:23] Reconfigure all domains and mailboxes? [Y/n]
[2016-03-28 22:38:30] Reconfiguring all domains and mailboxes .........................
[2016-03-28 22:40:42] [OK]
[2016-03-28 22:40:42]
[2016-03-28 22:40:42] Restoring DNS server configuration
[2016-03-28 22:40:42]
[2016-03-28 22:40:42] Synchronize DNS zones with the DNS server? [Y/n]
[2016-03-28 22:41:30] Synchronizing DNS zones with the DNS server .....................
[2016-03-28 22:41:30] [OK]
[2016-03-28 22:41:30]
[2016-03-28 22:41:30] Checking MySQL database servers
[2016-03-28 22:41:30] ..................................... [OK]
[2016-03-28 22:41:30]
[2016-03-28 22:41:30] Repair databases on available servers
[2016-03-28 22:41:30] ............................... [OK]
[2016-03-28 22:41:30]
[2016-03-28 22:41:30] Repair database users on available servers
[2016-03-28 22:41:30] .......................... [OK]
[2016-03-28 22:41:30] Error messages: 0; Warnings: 3; Errors resolved: 0
Error: Unable to start service: Unable to manage service by nginxmng: ('start', 'nginx'). Error: [2016-03-28 23:09:31] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/nginx_control' '--start'] with exit code [1]
Can not start proxy server: /usr/local/psa/admin/sbin/nginx-config execution failed:
nginx: [emerg] bind() to 89.163.13*.**:80 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed
- Kein gültiger Support-Code angegeben
- It was identified that your Plesk license was purchased from one of the Plesk Partners. We strongly recommend that you request support from that provider. Plesk Partners are fully trained by Plesk and deliver best-in-the-industry support for Plesk products running on their infrastructure. You can use the product documentation (docs.plesk.com) and Knowledgebase (kb.plesk.com) to find a solution or ask a question on the Plesk Forum (talk.plesk.com). Plesk Partners should use their support codes to contact Plesk technical support team.
So, why you can't asp support from your service provider who is Plesk partner? For access to Plesk support you should have Plesk license which was purchased directly from Plesk. Other possible options can be found in this my post - #6Thank you! I'll wait for a Plesk team member.