Error 403 Forbidden on all sites after migration

[dedisoft1]

Hi,

We have installed Plesk 12 on a fresh up to date Ubuntu 14.04 x64 server.

After installation, and before any migration, we have moved some folders:

- /var/www/vhosts -> /opt/vhosts
- /var/qmail -> /opt/qmail
- /var/mysql -> /opt/mysql

We have created symlinks, modified some configuration files (Plesk included) and ran domains reconfiguration script (zero domain installed, but just in case the script will do anything else).

After that, we have launched Plesk Migration Wizard (from Plesk 9 to last release).

Everything has worked fine: all domains have been migrated on our new folders (/opt based) and owners has been correctly defined for each domain. The same for MySQL and all mail accounts.

We have checked Apache VirtualHost configured by Plesk Migration Wizard : our new folders are used (/opt).

So all seems to be ok.

But now, all websites (configured with Apache and Apache PHP module) returns 403 Forbidden error.

We have try changing to FastCGI with Apache same error.

We have try changing to full Nginx (PHP and static files), some websites run.

We have checked some KB (112884, 800) but all seems to be good.

Is there any steps we have omitted when we move folders ?

Have you some suggestion to find where the problem comes from ?

Thanks in advance

Regards,

 

[IgorG]

You shouldn't move vhosts location manually. Use special transvhosts.pl script.

 

[dedisoft]

Hi,

Thanks for your reply and sorry for my late reply.

We already have tried this script. To be sure, I've reinstalled the server, used transvhosts.pl, corrected some errors on Apache conf (the script didn't modify all files and Apache refuses to start after...) and then re-run the migration tool.

Same problem here, error 503 on all websites.

We already have this error during the summer, and Plesk support has corrected this directly on the server. Now it's another server and the bug still persists.

We will try with Ubuntu 12.04 but we prefer using Ubuntu 14.04 (because it's a new server so last version is prefered).

Regards,

 

[dedisoft]

Hi,

Apache logs contains interresting thing:

AH01630: client denied by server configuration

So it seems that Apache configuration hasn't been created correctly. How can I check / reconfigure Apache with Plesk ?

If I change anything manually, this can be removed by Plesk later...

PS: KB 120112 has already been verified.

 

[dedisoft]

Running /opt/psa/admin/bin/httpdmng --reconfigure-all didn't change anything.

503 forbidden still persists.

 

[dedisoft]

Hi,

We have tried Ubuntu 12.04 amd64 rather than Ubuntu 14.04 (prefered version).

On Ubuntu 12.04:

- transvhosts.pl works correctly (not on Ubuntu 14.04)
- migration is successfull

We will try now upgrading this server to Ubuntu 14.04 just to check if this is possible.

Regards,

 

[dedisoft]

Hi,

So migrating from Plesk 9 to Plesk 12 on Ubuntu 12.04 works like a charm.

Migrating from Plesk 9 to Plesk 12 on Ubuntu 14.04 didn't work.

Migrating from Plesk 12 on Ubuntu 12.04 to Plesk 12 on Ubuntu 14.04 didn't work too.

It seems that Ubuntu 14.04 isn't very well supported...

 

[UFHH01]

Sorry dedisoft,

these are too less informations to investigate your possible issues/failures/problems. If you are stuck with your investigations, please provide some log - errors and it might be as well a good idea to change to a debug - level to receive a more detailled log.

Parallels Plesk Panel for Linux services logs and configuration files ( KB - article: 111 283 )​

Please be aware that on Ubuntu 14.04 the standard apache 2.4 is used, which needs some configuration modifications ( http://httpd.apache.org/docs/2.4/upgrading.html ).
As well, it could be a good idea to upgrade your PHP version to 5.5.20, which works very well on Ubuntu 14.04 ( ppa : ondrej/php5 ).

 

[dedisoft]

Hi,

Thanks for your reply.

I know that Apache 2.2/2.4 have different configurations files.

Our problem is solved (we are using Ubuntu 12.04 for this server).

I have send these information "just for information", and to tell about what has been tried.

About modifying Apache 2.4 files, I don't like this suggestion. Plesk will recreate configuration on another moment, so all modifications can be lost.

And as this is a migration, I think Plesk must be able to produce correct configuration files for Apache 2.4.

We have done a similar migration last summer, and Plesk has correctly generated all configuration files. Some other errors has been corrected by support.

We will use Ubuntu 12.04 until Plesk is removed...

Regards,

 

[UFHH01]

...

About modifying Apache 2.4 files, I don't like this suggestion. Plesk will recreate configuration on another moment, so all modifications can be lost.

And as this is a migration, I think Plesk must be able to produce correct configuration files for Apache 2.4.

We have done a similar migration last summer, and Plesk has correctly generated all configuration files. Some other errors has been corrected by support.

We will use Ubuntu 12.04 until Plesk is removed...

Regards,

To avoid overwrites for configuration files in case of updates/upgrades/patches, you always have the choice to use CUSTOM templates.

Changing Virtual Hosts Settings Using Configuration Templates ( Plesk 12 online documentation )
​

What happened in the past, is not always transferable to current procedures. In your case, there was no standard apache 2.4 installation from the operating system vendor and so former migrations were mostly done without any issues, regarding your webserver configuration files. Even that Plesk supports Apache 2.0 to 2.4, the slightly different changes for Apache 2.4 are ( not yet ) implemented in the Plesk template configuration files, but due to the case, that you have the possibility to use custom templates, it will only take a few minutes to adjust this - be aware that Plesk doesn't replace any system adminstrators, it just makes their lives a bit easier. ^^

 

[dedisoft]

I understand.

In our case, we have choose to just install a fresh Ubuntu with all updates.

Then we have installed Plesk. So Plesk has installed Apache himself.

We will just try to see if Plesk can do the job "alone".

Thanks for your suggestion.

Regards,

 

[UFHH01]

Hi dedisoft,

Plesk is not shipped with apache, it relies on the installed version which you install, based on the operating system from your vendor. You always have the choice to change the apache version, but Plesk itself will not do this.