• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Problem when previewing websites

TreDek

New Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
Plesk Obsidian Web Host Edition 18.0.64 Update Nr. 1
I imported some wordpress pages manually, since the import tool always threw me some error. That is not the point though. The problem I now have is that even though Plesk seems to recognize these pages as WP pages (they are connected to the WP toolkit, databases are connected as well), the preview only shows the Plesk welcome page. Also, the disk space is shown as 0.1MB, even though there's obviously a full WP installed.

I suspect that, since multiple pages exist in subdirectories of the one first associated with the service plan, the size might be added to that one. That would at least explain the small file size shown, although I can't imagine this is how it is supposed to work. It is a bit of an odd folder structure I must say.

Any ideas on what I could try or check to solve the problem with the previews and wrong file size shown in the list of websites for that customer? Thanks.
 
Typically, you would see a default page because index.html has priority over other index files, such as index.php. More details on how to sort out the issue you can find in the following article. If the issue still persists after defining a custom index file, please let us know.

Regarding the disk usage being incorrectly calculated, please try executing the following command:

/usr/local/psa/admin/sbin/statistics --calculate-one --domain-name=example.com
 
Back
Top