Resolved Moving a site from an old server to my new Onyx server

[FAB]

Hi all,

I just moved a prestashop store from an old server to my new Plesk server.

To do that:
- I dumped the ddb and imported it in the new server, everything seems good there.
- I tar.gz the site, then ftp it to it's new server. Then I updated user ; group ; and permissions.

(nota: I also reparametered the default host folder from "httpdocs" to "www")

Here is my problem now:
- when I do mywebsite.com -&nbspДанный веб-сайт выставлен на продажу! -&nbspmywebsite Ресурсы и информация., I still see the "If you are seeing this message... etc" (default Plesk page).
- when I do http://www.MYWEBSITE.com/hello.jpg (a test image), I see it
- when I do http://www.MYWEBSITE.com/index.html , I see the default Plesk page.
- when I do http://www.MYWEBSITE.com/index.php , I see the default page of the store.

Do you have any idea? (I just spent 2h on that......... with no success)

Thanks,
FAB

 

[UFHH01]

Hi FAB,

to "correct" file - permissions, you should consider to use the "Plesk Repair Utility"

=> Plesk Repair Utility​

Example command:

plesk repair fs -y -v

... , instead of changing group/user - permissions manually.

(nota: I also reparametered the default host folder from "httpdocs" to "www")

Why did you do that? Who advised you to do that?

Pls. compair/inspect your server - wide vhosts - configuration - files, named as "server.conf", which you can find in the webserver - related paths

For apache:

=> "/etc/apache2/plesk.conf.d" ( for Debian/Ubuntu - based systems ) and "/etc/httpd/conf/plesk.conf.d" ( for CentOS/RHEL - based systems )
​

For NGINX:

=> "/etc/nginx/plesk.conf.d"
​

... in order to see, WHICH default vhosts - paths are used on your server.

The "default" webserver - configuration files are based on Plesk webserver configuration templates, located at "/usr/local/psa/admin/conf/templates/default". If ( for what ever reason ) you could decide to change these templates, pls. do this on your own risk, and without the Plesk support, because the recommended way to change webserver - configuration templates is to overwrite them with "CUSTOM" templates and not with manual changes at the "default" - folder.

A detailed documentation can be found at:

=> Changing Virtual Hosts Settings Using Configuration Templates​

The desrcibed issues/problem is mostly related to the usage of the DEFAULT setting of your IP - address(es), even that you already added a primary domain for one of them after your initial Plesk installation. Pls. consider to choose a DEFAULT domain for each of your IP(s), to avoid the usage of "/var/www/vhosts/default/htdocs".

In addition, it could as well be, that you could have more than one "index" - file on your domain - web - document root ( i.e.: "index.html" AND "index.php" ), while "index.html" could be the default Plesk standart website, which will be created based on the skeleton at : => /var/www/vhosts/.skel/0/httpdocs

Due to the fact that you might use a combination of apache and nginx, then a default "Index files" configuration

index.html index.cgi index.pl index.php index.xhtml index.htm index.shtml

is being used, where "index.html" is served BEFORE "index.php".

You are certainly able to change the default "index - files" setting, by using a custom definition at each (sub)domain, located at:

=> Home > Subscriptions > (sub.)YOUR-DOMAIN.COM > Apache & nginx Settings​

Pls. note, that Plesk supports various operating systems and various Plesk versions, where paths may differ, depending to the Plesk version and the operating system. If you don't provide informations about these two things, you could always experience, that an answer/suggestions/explanation might not include the paths, according to YOUR Plesk version(s) and YOUR operating system(s). Best and recommended usage in this Plesk community is to provide at least the output of the command ( logged in as user "root" over SSH ), for all your threads:

plesk version

 

[FAB]

Thanks!

I understand what happened now!
For some reasons, Plesk added its own index.html in the website root directory. Priorities being what they are, this index.html was seen before index.php.

I actually just remove this index.html and everything seems working fine now.

(update: after verification, Plesk actually added ALL his skeleton files. I removed them manually)

I also ran the command
plesk repair fs -y -v
=> reported zero error (cool!).

NOTA:
# plesk version
Product version: Plesk Onyx 17.0.17 Update #26
Update date: 2017/05/20 04:24
Build date: 2017/03/22 17:00
OS version: CentOS 7
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2