![\"\"](\"https:\/\/www.hostvento.com\/kb\/hosting-faqs\/wp-content\/uploads\/2019\/05\/d30710f6-d2ba-4abe-afdc-51836077d96c_common-wp-errors-16-min.jpg\")
<\/a><\/figure>\n<\/div>\n\n\nThis error message appears when there is a code error on your website, usually in the functions.php file. Instead of the website loading, you simply get a notice explaining the problem and the location where it happened.<\/p>\n\n\n\n
Use SSH File Transfer Protocol (SFTP) to access the given file and solve this issue. Because FileZilla is an open-source, free program, we shall use it in this case. Log in to the backend of your website using the SFTP credentials that your web host supplied you.<\/p>\n\n\n\n
Locate the disputed file now. You can see that the issue is with the functions.php file for your site’s current theme in the image above. Thus, you must choose View\/Edit from the context menu when you right-click on functions.php in order to enter the theme’s folder.<\/p>\n\n\n
<\/a><\/figure>\n<\/div>\n\n\nIf you keenly check the Parse error message<\/strong>, you will find that it also lets you know on what line the problem has occurred. So, you simply need to find that line and fix the problem. In the example mentioned above, the problem is about missing parenthesis.<\/p>\n\n\n Then save your file and select Yes<\/strong> when your FTP client asks for replacing the existing file on the server. With this, you will be able to check your site and see that it loads normally.<\/p>\n\n\n\n It is a very rarely known and mysterious error in WordPress and is called as the White Screen of Death (WSoD)<\/strong>.<\/p>\n\n\n\n With this error your entire site gets replaced with a blank, white nothing, leaving no error messages or further assistance display.<\/p>\n\n\n There are several reasons for this problem to occur and usually means that your site can\u2019t be loaded properly.<\/p>\n\n\n\n Therefore, even for troubleshooting it, there are several ways.<\/p>\n\n\n\n Here are quick tips that you use to troubleshoot this particularly tricky problem:<\/strong><\/p>\n\n\n\n 1. Disable your plugins:<\/strong> The main cause behind the WSoD<\/strong> is a faulty plugin, so make sure you disable them all and check if it fixes the problem.<\/p>\n\n\n\n 2. Disable your theme:<\/strong> WordPress themes can also lead to this issue. Use SFTP<\/strong> to replace it with one of WordPress\u2019s default themes.<\/p>\n\n\n\n 3. Activate the WordPress debug mode:<\/strong> With this feature, you will see errors directly on each page. This can help you identify the primary cause of the WSoD<\/strong>.<\/p>\n\n\n\n 4. Purge your cache:<\/strong> Also, the caching solution of your website will help you to see outdated files even if the WSoD<\/strong> has been fixed. Therefore, it\u2019s better to clear your cache and check if the problem has been resolved.<\/p>\n\n\n\n 5. Raise your memory limit:<\/strong> Your site might fall short of memory. The maximum limit of memory can be set by editing your php.ini<\/strong> file.<\/p>\n\n\n\n Implementing these methods will help to fix the WSoD<\/strong> in the vast majority of cases. But, if there are still issues occurring, it is better to contact your host\u2019s support team for more help.<\/p>\n\n\n\n Another issue is the Internal Server Error<\/strong> which can be quite difficult to find the underlying problem.<\/p>\n\n\n Fortunately,\u00a0compared\u00a0to\u00a0the\u00a0WSoD,\u00a0there\u00a0are\u00a0less\u00a0causes\u00a0for\u00a0this\u00a0issue. It\u00a0may\u00a0happen\u00a0if\u00a0the\u00a0server\u00a0problem\u00a0is\u00a0undetectable\u00a0and\u00a0is\u00a0typically\u00a0brought\u00a0on\u00a0by\u00a0one\u00a0of\u00a0the\u00a0following\u00a0causes:<\/p>\n\n\n\n Simply speaking, .htaccess<\/strong> is a file that shows the way your site communicates with its server. With this file, you can increase your site\u2019s security, and prevail some of the default server settings. For confirming if this file is causing the Internal Server Error, you simply need to disable it.<\/p>\n\n\n\n This can be done by using SFTP. Generally you will get this file in your site\u2019s root directory, which is often titled public_html<\/strong>.<\/p>\n\n\n Simply change the file\u2019s name for disabling it. For example, if it is renamed as .htaccess-disabled<\/strong>, you can then check your site to know if the issue isn\u2019t occurring now.<\/p>\n\n\n\n In case your problem gets fixed with this, you need to generate a new, bug-free .htaccess file<\/strong>. For this, go into your admin dashboard and access Settings > Permalinks<\/strong>.<\/p>\n\n\n It isn\u2019t compulsory to make any real changes here. Simply clicking on Save Changes<\/strong> will help to generate a new .htaccess file<\/strong>. This might hopefully resolve the issue.<\/p>\n\n\n\n But if the problem still doesn\u2019t get resolved, you might need to increase your PHP memory limit<\/p>\n\n\n\n To\u00a0increase\u00a0your\u00a0PHP\u00a0memory\u00a0limit,\u00a0see\u00a0this\u00a0guide. If\u00a0you\u00a0are\u00a0unable\u00a0to\u00a0raise\u00a0your\u00a0limit\u00a0any\u00a0higher,\u00a0you\u00a0may\u00a0want\u00a0to\u00a0consider\u00a0upgrading\u00a0your\u00a0hosting\u00a0package.<\/p>\n\n\n\n You might be familiar with 404 Error<\/strong> as an internet user.<\/p>\n\n\n It means that the requested page could not be found by the server. This issue is frequently encountered when your website has altered URLs and broken links. It may also happen if the page that is requested is unavailable.<\/p>\n\n\n\n The.htaccess file is once more the most frequent cause of this problem. This file also manages the hyperlink structure of the webpage. It is plausible that your URLs are being redirected to incorrect pages. It would be necessary for you to first create a fresh.htaccess file.<\/p>\n\n\n\n However, if still the error persists, you may need to re-upload .htaccess<\/strong>. You can create a new file, give it the name .htaccess<\/strong> (mention the period, and you don\u2019t need to add a file extension), and paste in the following default code:<\/p>\n\n\n\n You can now upload the file to the root folder to your site. After following all this, the 404 error you\u2019re seeing should be resolved.<\/p>\n\n\n\n This error, true to its name, may arise if your website cannot access its database. You can locate your website’s database, which houses all of its content, if you are unfamiliar with the phrase. It contains user data as well as your pages and posts. Your website would stop working entirely if you could not access the database.<\/p>\n\n\n\n There are a few possible causes for this problem, however wp-config.php is the one file on your website that causes the majority of them. This file contains all of the database information for your website, hence it is the source of the issue.<\/p>\n\n\n\n In order to repair the connection, access the wp-config.php<\/strong> file of your site, located in its root folder.<\/p>\n\n\n Once located, right-click on the file, and select View\/Edit<\/strong>. First check whether the credentials in the file are correct and for this, access your phpMyAdmin<\/strong> to get the correct details. In case you find that the hostname, username, password, and\/or database name in the file are incorrect, replace so that the error gets fixed.<\/p>\n\n\n\n But, if the error persists, you will need to activate WordPress\u2019 automatic database optimization tool. You can use this tool to repair corrupted databases, and to turn it on add the following line to your wp-config.php<\/strong> file:<\/p>\n\n\n\n Then save the file and upload it back to your server in order to run the new script by browsing https:\/\/yourwebsiteurl.com\/wp-admin\/maint\/repair.php<\/strong>. The resulting page will look like as below:<\/p>\n\n\n You just need to click on either of the buttons to run the repair tool. After the process is complete, the page will reload, and a message telling you that the database tables have been fixed will be displayed.<\/p>\n\n\n Now, this should fix your database connection error. Make sure you remove the line WP_ALLOW_REPAIR<\/strong> from wp-config.php<\/strong> when have completed with the task.<\/p>\n\n\n\n This error appears after a site was browsed several times but was unsuccessful to load. This indicates that the server is trying to load the site, and has basically given up.<\/p>\n\n\n Though there can be variety of reasons for this error, the most common is that your site lacks the resources it needs to function accurately. For example, if you are using shared hosting<\/strong>, another site can use your server\u2019s resources. Or it might happen that your site has exceeded its maximum allowed bandwidth.<\/p>\n\n\n\n In the event that this problem keeps happening, you may want to consider upgrading your hosting package. A different hosting package with more resources could assist you in preventing website lag and outages. Also, because you will have more server resources, your website will not be impacted by other sites experiencing high traffic.<\/p>\n\n\n\n This error will appear if your website is straining the server excessively. Consequently, it is preferable to speed up your website in order to prevent resource-hogging plugins. Make sure your performance is not being hindered by your theme as well. You will need to raise your PHP memory limit once more.<\/p>\n\n\n\n You might come across a situation when your sidebar has moved from its standard position next to each page and post\u2019s main content, and has decided to lie underneath your main content.<\/p>\n\n\n This is due to an issue with the HTML or CSS code<\/strong> of your theme. Hence, this error can occur due to a recent changes made to your theme. Recently, if you\u2019ve edited any of your theme files, you can revert them to their previous states, to check if that resolves the problem.<\/p>\n\n\n\n To be more specific, you should look out at two main things when troubleshooting this problem:<\/p>\n\n\n\n Observe your theme for such issues to get the source of the problem. Running the affected page through the W3C Markup Validation Service<\/strong> will help you to find the source of the error faster.<\/p>\n\n\n\n Images can break on your website in several ways. They can be display in an incorrect manner after uploading or you won\u2019t be able to upload them at all. What matters is that the issue occurs due to the incorrect file permissions.<\/p>\n\n\n\n This basically means that the website is unaware that you are authorized to add and access the files that you are attempting to work with. This error is caused by a plugin that unintentionally changed your permissions or by a hack on your website. Fortunately, this is simply fixable.<\/p>\n\n\n\n You will need to access your site using SFTP<\/strong> again. For this go to the uploads folder, located in the wp-content directory<\/strong>.<\/p>\n\n\n But, you don\u2019t need open this folder. Just right-click on it and select File permissions<\/strong>, to open the folder\u2019s permission settings.<\/p>\n\n\n Set the Numeric value to 744<\/strong>, so that the owner (i.e., you) can read and write uploads. Click OK<\/strong> after that to get the new permissions applied.<\/p>\n\n\n\n Repeat the same process for all files inside the folder. For that right-click on uploads and select File permissions<\/strong> again. This time, set the value to 644<\/strong> and check the Recurse into subdirectories<\/strong> option. Also, select Apply to files only<\/strong>.<\/p>\n\n\n\n The Media Library on your website will function regularly when you save your changes. By uploading an image to your admin dashboard, you may verify this. If the problem still occurs, follow the previous steps again but set the uploads folder’s permission value to 755 rather than 744.<\/p>\n\n\n\n All the errors mentioned until now have occurred due to technical problems. But, to get locked out of your admin dashboard is something different. This generally is seen when you forget your password.<\/p>\n\n\n Don\u2019t panic. Losing your password doesn\u2019t mean that you won\u2019t be able to access your site. Firstly, click the Lost your password?<\/strong> link on the login page. You can recover your password by entering your username or email address.<\/p>\n\n\n In majority of cases, this will work. Yet there are some instances where this feature may have issue such as it could be disabled or maybe you won\u2019t have access to the email you signed up with.<\/p>\n\n\n\n In this case, reset your password using\u00a0phpMyAdmin<\/strong>. Though, this method can be risky as there can be accidental problems with your site or database. So, this method should be used as a last solution. This process will vary based on your web host and setup, but we\u2019ll be using the\u00a0hostvento<\/strong> control panel<\/strong>\u00a0in this example.<\/p>\n\n\n\n After getting logged in, click on Domains<\/strong> and select Edit<\/strong> for the site you want to access.<\/p>\n\n\n Then, open phpMyAdmin<\/strong>.<\/p>\n\n\n Next, find your user table, usually called wp_users<\/strong> or something similar. After getting it, search for your specific user account and click on Edit<\/strong>.<\/p>\n\n\n Now change your profile\u2019s information, right from its password. Replace the current string in the user_pass <\/strong>row with your preferred password.<\/p>\n\n\n Set the function drop-down menu to MD5<\/strong> to encrypt the password. After saving the changes, you log in again with your new password.<\/p>\n\n\n\n In actuality, maintenance mode is an automated function that momentarily stops your website while it is being updated. By doing this, you will be able to prevent potentially problematic scenarios when users attempt to access your site’s functionality while it is being updated.<\/p>\n\n\n\n The site gets updated so quickly that it is very difficult to notice the change. However, if the update is cancelled before getting completed, your site gets stuck in maintenance mode until further notice.<\/p>\n\n\n\n Fortunately, this problem can be fixed easily. Simply fire up SFTP<\/strong> again to access your site\u2019s root folder, and delete the file named as .maintenance<\/strong>.<\/p>\n\n\n This file is what activated maintenance mode, so removing it will revert your site back to normal. However, you\u2019ll also need to retry the failed update, as this error means that it didn\u2019t successfully complete.<\/p>\n\n\n\n WordPress offers the most useful feature of scheduling posts for a particular time. This helps you to line up posts in advance, leave the site alone to get content automatically published at the time set.<\/p>\n\n\n\n On the other hand, sometimes feature fails, and gives a Missed schedule <\/strong>error next to a post.<\/p>\n\n\n This problem generally occurs due to \u2018cron jobs\u2019<\/strong>. These are tasks used by WordPress to automate certain processes.<\/p>\n\n\n\n In case the correct cron job<\/strong> does not trigger when a post is scheduled, it won\u2019t get published and will remain in your admin dashboard until you publish it manually.<\/p>\n\n\n\n In order to avoid this error, use a plugin such as Scheduled Post Trigger<\/strong>.<\/p>\n\n\n It is free and very lightweight plugin and makes sure that the cron jobs<\/strong> responsible for publishing scheduled posts run as per the expectations. When you activate it on your site, you can stay relaxed as your scheduled posts will get published on time from now on.<\/p>\n\n\n\n It is very important to keep your WordPress site updated at all times. We have recommended this many times to every website owner. If you are using a managed WordPress hosting<\/a> plan, you usually don\u2019t need to update<\/p>\n\n\n\n WordPress by yourself as those get automatically installed for you.<\/p>\n\n\n\n Still, if something goes wrong, the automatic update will fail.<\/p>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n2. White Screen of Death (WSoD)<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n3. Internal Server Error<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n4. 404 Error<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n# BEGIN WordPress\n\nRewriteEngine On\nRewriteBase \/\nRewriteRule ^index.php$ - [L]\nRewriteCond %{REQUEST_FILENAME} !-f\nRewriteCond %{REQUEST_FILENAME} !-d\nRewriteRule . \/index.php [L]\n\n# END WordPress<\/pre>\n\n\n\n5. Error Connecting Your Database<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\ndefine( 'WP_ALLOW_REPAIR', true );<\/pre>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n6. Connection Timed Out Error<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n7. Site\u2019s Sidebar Appearing Below the Main Content<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n\n
8. Unable to Upload Images<\/h3>\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n9. Can\u2019t Access the Admin Area<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n10. WordPress Is Stuck in Maintenance Mode<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n11. Missed Scheduled Post Error<\/h3>\n\n\n\n
<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n12. WordPress Failed to Auto-Update<\/h3>\n\n\n\n