Search results

It's normal behavior. Webserver listens on 80 (http) and 443 (https) ports, so your requests pass to webserver and it try to find corresponding vhost. You turned off ssl support for vhosts, so webserver could not find corresponding vhost and shows you default vhost. Why do you want to see 403...

noname1, You could setup php max_execution_time setting in Plesk (subscription level). Plesk automagically set the same value for nginx and fastcgi corresponding timeouts so you don't need additional actions with configuration files.

Could you provide us with additional info? I see that you use Atomic third-party repository, do you have another third-party repos? Could you describe of action order: Plesk installation/upgrade, repository setup, mysql install/upgrade?

Cedric70, Looks like you need use Domain Alias feature. So remove your custom DNS record and create domain alias. Additional info you could get there - http://download1.parallels.net/Plesk/PP11/11.5/Doc/en-US/online/plesk-customer-guide/65286.htm

Do you have any custom vhost config templates?

Could you show screenshot with problem?

Problem with MU was fixed. You could install updates from autoinstall.plesk.com.

Did you check corresponding settings in 'Websites & Domains' -> 'Web server settings', 'nginx settings' part?

Did you verify your FTP credentials?

stefanoostwegel, vhost.conf is custom config which should be created manually. In most cases you do not need to create it. Did you try to reconfigure all configs using `plesk sbin httpdmng --reconfigure-all` command?

Thank you for your report. It's will be fixed soon. (bug#138712)

It's a good idea to post your request on http://plesk.uservoice.com/

Inexo-Dev Could you share id of your support request?

Could you show me what do you have in your Plesk db? # mysql -u admin -p`cat /etc/psa/.psa.shadow` -e "use psa; select * from smb_productUpgrades;" And after that, let's remove all cached upgrade info: # mysql -u admin -p`cat /etc/psa/.psa.shadow` -e "use psa; DELETE FROM...

`plesk` utility was implemented in Plesk 11.5 version. If you have older Plesk version you could use:

Why not? It's work w/o problem..

Could you provide more info about your system? Plesk version, clean install or upgrade? What did you do before it happens?

Sounds like your Plesk was not properly upgraded. It's good idea to contact with support team.

11.5 release http://www.parallels.com/download/plesk/installer/

I'm sure you ask about this: http://download1.parallels.net/Plesk/PP11/11.5/Doc/en-US/online/plesk-unix-cli/39181.htm