clayp

WordPress is compatible with all operating systems, including Windows, macOS, and Linux. Regardless of your operating system, you can install WordPress locally using appropriate tools. However, WordPress is more optimized for Unix/Linux-based systems and web server stacks. The majority of WordPress websites are hosted on Linux operating systems, often using stacks like LAMP (Linux, Apache, MySQL & PHP). For local installations on Windows, macOS, or Linux, you can utilize XAMPP, a popular PHP development environment.

And if there are any compatibility issues, they are more likely related to the versions of the software packages that you are using.

WordPress server requirements:

1. Web server: Nginx or Apache with mod-rewrite module.
2. Disk space: At least 1 GB.
3. PHP: Version 8.0 or higher.
4. Database: MySQL 5.015 or higher (An alternative is MariaDB, version 10.1 or higher)
5. RAM (Random Access Memory): At least 512 MB.
6. CPU (Central Processing Unit): At least 1.0 GHz.

As you said It showed a 403 forbidden error, because of HTTP status code sent by the server when the client (user) initiating the request doesn’t have permission to access a specific page or resource.

1. Contact your host
It is a server-side error, and a recommended and safer solution for fixing the error is to contact your hosting provider. Reach out to their support team, describe the issue, and they will likely resolve it by disabling specific security rules or whitelisting the requested page.

2. Find whitelist.conf or exclude.conf file and add following code.

<locationmatch "/wp-admin/page.php">

    SecRuleRemoveById 300013

    SecRuleRemoveById 300015

    SecRuleRemoveById 300016

    SecRuleRemoveById 300017

    SecRuleRemoveById 949110

    SecRuleRemoveById 980130

</locationmatch>

<locationmatch "/wp-admin/post.php">

    SecRuleRemoveById 300013

    SecRuleRemoveById 300015

    SecRuleRemoveById 300016

    SecRuleRemoveById 300017

    SecRuleRemoveById 949110

    SecRuleRemoveById 980130

</locationmatch>

3. Disable mod_security for specific URL
With this approach, you can deactivate mod_security for particular URLs rather than for your entire site, providing a more secure option. You can define the URLs to match using regex within the <If> statement below.

<IfModule mod_security.c> 
    <If "%{REQUEST_URI} =~ m#/admin/#">
      SecFilterEngine Off SecFilterScanPOST Off 
    </If> 
</IfModule>

First, Clear your website cache and create a backup using a plugin such as BlogVault. 

Then, delete the .maintenance file from your site’s server, using your cPanel or FTP client.

1. Log into your cPanel account.
2. Navigate to Files > File Manager.
3. Inside public_html, search .maintenance file.
4. Right-click on it and choose Delete.

After that check your WordPress dashboard, and you’ll see that the error “An Automated WordPress Update Has Failed to Complete” has been resolved.

If you can’t find the .maintenance file then, go to File Manager > Settings and select Show Hidden Files from the window that pops up.

• Check for conflicts: Theme or plugin conflicts can cause WordPress updates to fail. You can deactivate plugins one by one and check which plugin is the cause.
• Check for database or server issues: Issues with the site’s database or server can cause WordPress updates to fail.
• Check for maintenance mode: Maintenance mode can cause WordPress updates to fail.
• Check the permission: Permission errors can cause WordPress updates to fail.
• Check for other causes: Other causes of WordPress update failures may be problems with the WordPress REST API. 

1. Manually update – using WordPress dashboard

1. Log into your WordPress dashboard. Navigate to the Updates link. If there’s an update, click on the corresponding link.
2. Inspect your wp-admin dashboard; if a database update is required, a pop up will appear. Click on it to finalize the update.

2. Manually update – using cPanel

Here are the steps to update WordPress manually:

1. Download the latest WordPress version to your computer.

2. Log in to cPanel and access File Manager.

3. Go to the root directory of your site (public_html).

4. Delete the wp-content and wp-admin directories.

5. Click on the “Upload” to upload the zipped WordPress file to your site server.

6. Extract the zipped file.

7. Move the wp-admin and wp-includes folders to the root directory, along with any loose files. Only the wp-content folder should remain.

8. Compare the two wp-content folders and only move files and folders that don’t already exist on your site to avoid unintentional deletion of plugins, themes, and media.

9. In File Manager, locate the version.php file in the wp-includes folder and note the value for $wp_db.

10. Close File Manager, open phpMyAdmin from cPanel, find your site’s database and open the wp_options table. Check the value for db_version and ensure it matches the version number from the version.php file. Update if necessary.

11. Log in to wp-admin, check the dashboard for messages, and follow any instructions to update the database.

After completing these steps, add “/wp-admin/about.php” to your site URL to verify if the WordPress version updated correctly.

It could be possible if you started with one theme and later switched to another theme. To display your blog posts on either the front page of your site or a dedicated Posts page, some changes are required to set up the post.

1. Log into your WordPress dashboard.
2. Navigate to the Post > Edit.
3. On the right side of the page, click on Visibility and set it as Public.

Hello @deedslag

As you said you face “Error Establishing A Database Connection”, which happens when the website refuses to connect to the WordPress database.

There is a high chance that the issue might be due to insufficient server resources. If not then check the below solutions.

Solutions:

–>Error establishing a database connection

1. Check your database server

The error message may arise on your WordPress site when your MySQL server is unavailable. Various factors can generate this error, it commonly occurs due to an excessive number of connections.

A database server has a maximum limit on simultaneous client connections. When this limit is reached, additional connections may be denied. Please reach out to your hosting provider to inspect and address potential issues with your MySQL server.

1. Connect to your control panel.
2. Inside public_html, create one php file.
3. And, add the following code: 

<?php
$link = mysqli_connect(‘localhost’, ‘username’, ‘password’);
if (!$link) {
die(‘Could not connect: ‘ . mysqli_error());
}
echo ‘Connected successfully’;
mysqli_close($link);
?>

Replace username, database name and password.

4. Access this file in browser
   https://domain-name/test.php

2. Check the Database Login Credentials
   1. Open the file manager from the cPanel account.
   2. Open your wp-config.php file.
   3. Next, verify this data in your database. For this go to Databases > phpMyAdmin.
   4. Make sure that both data should be the same.
3. Fix the corrupted files
   A corruped theme or plugin is one of the factors that cause file corruption.

Themes:
1. To solve this, navigate to Apperance > Themes from your WordPress dashboard. 
2. Choose another theme and check your page, then check whether it solved the issue or not. If not then the issue could be a corrupted plugin. In that case, consider deactivating all plugins and gradually reactivating them one by one to pinpoint the problematic ones.

Plugins:
1. Go to the File Manager.
2. Inside public_html, choose wp-content folder.
3. Rename the plugins folder.

By taking this step, you will deactivate all your plugins simultaneously. The same process can be used for disabling all WordPress themes. However, it is crucial not to disable both themes and plugins concurrently, as this can significantly complicate the process of identifying the root cause of the problem.

If the error disappears after renaming the plugins folder, it indicates that one of the plugins is causing the issue.

4. Repair the database in WordPress

Add the following code in your wp-config.php file.

define(‘WP_ALLOW_REPAIR’, true);

Next go to http://www.your-domain.com/wp-admin/main/repair.php in your web browser.

Two repair options will be presented – select the one that suits your needs.

Once the repair process is over, check your WordPress site to verify if it has returned to its normal state. If successful, promptly remove the function from your wp-config.php file to prevent potential misuse, as the repair page can be accessed by anyone without the need for login credentials.

–>503 error

1. Temporarily Disable Your Content Delivery Network 

Occasionally, the 503 error may not originate from an issue on your website but from your Content Delivery Network (CDN). If you use a CDN, a swift method to determine this is to temporarily deactivate it.

2. Review logs and enable WP_DEBUG

Add the following code in your wp-config.php file.

define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );

3. As above mentioned, disable and re-enable your plugins and theme.

Please check your database, it may be corrupted and reset your password if possible.

1. Reset password
   You can reset the password from the WordPress dashboard, by clicking on Reset Password or Lost Your Password.
   OR
   1. Log into your cPanel or FTP.
   2. Navigate to Databases > phpMyAdmin.
   3. Choose your database, choose the wp_users table and change the username and password.
2. Security plugins block you
   If you use a WordPress security plugin, you might unintentionally restrict your access. For example, several WordPress security plugins come with functionality to restrict login attempts, which may temporarily ban you if you input an incorrect username/password multiple times.
   
   You have two options: wait, as typically the block is temporary and you can retry after a while, or you can manually disable the security plugin to regain immediate access.
   
3. Check your Site URL
   1. Log into your cPanel account.
   2. Go to the Files > File Manager.
   3. Inside public_html, open the wp-config.php file and check both URLs.
   
4. Check your File permission
   Ensure that wp-login.php is set to 664.
   Ensure that the wp-admin folder is set to 775.

• This reply was modified 2 years, 3 months ago by clayp.

1. Rename plugins:
   First, you need to rename the Wordfence plugin folder, Have doubts about the success of 2FA or reCAPTCHA, or perhaps question whether they are not appearing initially for authentication. I also suggest to disabling other plugins (In your case Jetpack and others that you currently use) and trying to log into your dashboard.
2. Rename theme:
   1. Log into your cPanel account or FTP.
   2. Navigate to public_html > wp-content > theme.
   3. Rename the theme folder, and try to access your dashboard.
3. Corrupted login file:
   Back up WordPress before deleting the login file.
   Download the most recent version of WordPress and then log into your cPanel account or FTP. Navigate to public_html > wp-config file. Add your login details. Now try to log into your dashboard.

• This reply was modified 2 years, 3 months ago by clayp.