• Hello everyone,

    I need help recovering my self-hosted WordPress website, hosted by OVHcloud: [ redundant link deleted ].

    For several days, the homepage has been returning an HTTP 500 Internal Server Error. I also cannot access /wp-login.php, so I cannot log in or access the WordPress admin dashboard to manage or repair the website.

    Here is the information I have been able to confirm:

    • Hosting provider: OVHcloud, shared hosting.
    • PHP version shown in the hosting control panel: PHP 8.0.
    • Disk space usage: 1020 MB out of a 1000 MB limit.
    • Static file: /license.txt loads successfully, but the homepage and WordPress login page fail.
    • WordPress update: I received an automated email stating that an automatic update to WordPress version 7.1.3 could not be completed. I have not been able to confirm whether this is related to the problem.
    • OVHcloud’s response: They have confirmed that they have not detected any infrastructure issues affecting my hosting service. They also confirmed that security patches have been applied to the PHP versions they support, including PHP 8.0. They recommend upgrading PHP, while taking plugin compatibility into account.

    Message repeatedly appearing in the Apache logs:

    AH00687: Negotiation: discovered file(s) matching request: /homez.10002/bernatu/www/index.html (None could be negotiated)

    I do not know whether this message is related to the HTTP 500 error. There is also another log entry related to FastCGI, but I have not been able to determine its cause.

    I would appreciate advice on the following questions:

    1. How can I identify the actual cause of the HTTP 500 error when I cannot access the WordPress admin dashboard?
    2. Could the Apache message concerning index.html be related to the problem?
    3. Could the incomplete WordPress update or the hosting storage limit being exceeded have contributed to the failure?
    4. What safe steps would you recommend to restore the website and regain access to the admin dashboard without losing any content?
    5. How can I first make sure I have a complete backup of both the website files and the database?

    I would prefer not to make changes blindly that could make the situation worse or cause data loss.

    Thank you very much for any help or guidance you can provide.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator threadi

    (@threadi)

    If I understand you correctly, your hosting disk space is full. Among other things, this prevents the installation of updates – such as essential WordPress core security updates – and can also trigger the “Error 500” you are experiencing.

    To resolve this, you first need to identify what is consuming so much storage space in your hosting account. Check whether your hosting provider offers an interface for this purpose. If not, you can use FTP to inspect your hosting directories and locate large files. For instance, you could immediately delete backup files via FTP; this would free up space and likely resolve the issue. If you find other large files, you will need to determine how they are used within your project. Be careful not to delete files in /wp-content/uploads/, as these are managed via the WordPress Media Library; deleting them directly could cause errors in your site. An exception to this would be files in subdirectories created by plugins – you know your project and its plugins best, so you should be able to distinguish these.

    Because your disk space is full, you can create a backup either by contacting your hosting provider’s support team or by performing it manually: download all directories and files via FTP and export your database as a dump file. Depending on the number of files, the manual process could take several hours. Database dumps can typically be generated using tools provided by your host.

    eshbanbahadur

    (@eshbanbahadur)

    Your disk is at 1020 MB of a 1000 MB limit, and that alone can cause a 500 error, because PHP can’t write sessions, cache or temp files. It’s also the likely reason the 7.1.3 auto-update stopped partway. Free up space first over FTP or the file manager. Old backup zips in wp-content, cache folders and big log files are the usual culprits. Then check the site root for a leftover .maintenance file and delete it. If it still errors, turn on WP_DEBUG and WP_DEBUG_LOG in wp-config.php and read wp-content/debug.log, which names the failing file. If the half-finished update left core files mismatched, re-upload fresh wp-admin and wp-includes folders from the same version without touching wp-content or wp-config.php. The AH00687 negotiation line in the Apache log is harmless and unrelated.

    Thread Starter bernaterra

    (@bernaterra)

    Hi everyone,

    Thank you for your suggestions. I have followed some of the recommended steps, but I still need help figuring out what to do next.

    Here is what I have done so far:

    • I downloaded the contents of my /home/bernatu/www directory using FileZilla to create a local backup.
    • I exported my WordPress database through phpMyAdmin and saved the SQL file on my computer.
    • I checked the WordPress root directory and enabled the display of hidden files in FileZilla. I could not find a .maintenance file.
    • I could not find an error_log or debug.log file in the WordPress root directory.
    • I deleted more than 20 MB of files, including some images from wp-content/uploads/2026 and a ZIP file of approximately 15 MB from /home/bernatu/.wp-cli/cache/core. I understand that deleting images can break pages, so I have stopped deleting files for now.

    The main problem is that OVH still reports exactly 1020 MB used out of a 1000 MB limit, even after I deleted more than 20 MB of files and refreshed the control panel. I have not been able to confirm whether the disk usage calculation is delayed or whether other files are still consuming the quota.

    My website and /wp-login.php still return HTTP 500 errors. The automatic WordPress update to version 7.1.3 also failed.

    I would appreciate some guidance on the safest next steps.

    1. Is there a way to identify the actual disk usage on OVH shared hosting, including files outside the www directory?
    2. Could the hosting quota display take some time to update after files are deleted?
    3. Is there a safe way to enable WordPress debugging or retrieve the relevant PHP/FastCGI error logs without access to the WordPress dashboard?
    4. Once the disk space issue is resolved, what is the safest way to check whether the failed core update left WordPress files incomplete?

    I would prefer not to replace WordPress core files or disable plugins until we have more information about the cause of the error.

    Thank you for your help.

    Moderator threadi

    (@threadi)

    You need to delete far more than 20 MB – and, as I recommended, NOT from wp-content/uploads. Doing so has made certain files untraceable, even though they’re expected to be in the media library. Once the website is back up, there would be gaps in the layout. Fortunately, you downloaded the files – I’d recommend that you don’t upload them back to the exact same location once the problem is resolved.

    The information about how much storage space is being used may also be cached by your host. No one here knows how long that cache lasts. I would therefore recommend once again that you contact your host’s support team and ask them about this. They can also answer your questions – questions that probably no one here can answer, since it’s unlikely that anyone on the wordpress.org forum works in support at OVH.

    The safest way to ensure that all WordPress core files are present after the problem has been resolved is to upload them manually. This is described in the article here: https://wordpress.org/documentation/article/updating-wordpress/#manual-update

    You can enable debugging in WordPress as described here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ – however, if your disk space is full, this will only lead to additional errors because the debug.log file cannot be written. I would therefore strongly recommend that you do not do this until the actual problem (the full disk space) has been resolved.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.