Trying to access your WordPress site, but seeing a 403 Forbidden error? Well, that means the page you are trying to access is forbidden due to some reasons which you need to figure out. The same also comes mentioned in the 403 error message stating “You don’t have permission to access / on this server”.

In order to resolve the problem, the first thing that you can try is to delete the file from the server and access the WordPress site again. If error 403 forbidden resolves after deleting files, that means the .htaccess file was corrupted. Thereafter, you can regenerate the. htaccess file by logging in to your WordPress, navigate to Settings > Permalinks. If it doesn’t work out, then you must try the series of steps as we have described in this article. Let’s get started with the error 403 – Forbidden basics.

What is 403 Forbidden Error? 

403 forbidden error is a type of HTTP status code that means accessing the page or source is forbidden due to some reasons.

The web server generally uses Forbidden error 403 to communicate with the web browser. It means that the webserver is able to understand the request that the web browser has made, but is unable to fulfill it. In that aspect, we can consider Forbidden error 403 as an HTTP status code that the webserver uses in order to communicate with the web browser.

What Made 403 Forbidden Error Occur in WordPress? 

Reasons that cause error 403 Forbidden to occur while accessing the WordPress site. Following are the leading ones:

  • You don’t have the file permissions.
  • Corrupted .htaccess file.
  • An issue with the plugin that you are using at your WordPress site.

How Error 403 Forbidden  Appears On WordPress Screen! 

Just as with other HTTP status codes, this error code appears on-screen in different forms. Here are different variations that you may get to see.

  • Forbidden (written in bold) – You don’t have permissions to access  / on this server.
  • 403 – forbidden error – You are not allowed to access this address.
  • Error 403 – Forbidden.
  • 403 – Forbidden: Access is denied.
  • 403 Forbidden – NGINX.
  • 403 Forbidden – access to the source on the server is denied.
  • You are not authorized to view this page.
  • It appears you don’t have permission to access this page.
  • 403. That’s an error. Your client doesn’t have permission to get the URL / from the server.
  • HTTP error 403 – Forbidden – you do not have permission to access the document or program you requested.

Now let’s learn how to deal with error 403 forbidden most effectively.

How to Fix 403 Forbidden Error on WordPress Site? 

Dealing with forbidden error 403 is simple. You can try to modify the file permissions, create a clean and new .htaccess file and try to deactivate/reactivate the plugins. For detailed instructions run through the following troubleshooting steps.

Step 1. View and modify the file permissions 

Each folder or file on your WordPress site’s server has the ability to control who can read, write and execute the files. A unique 3 digit number indicates the level of permissions for these 3 categories. Here is the detailed description for the above categories.

Read – Permission to access or view data in the file.

Write – Permission to add or delete the files in a folder.

Execute – Permission to run the file or execute as a script.

So, in case if these file permissions are messed up or something is not as it then most likely you will end up facing 403 forbidden error WordPress. To fix it, you must view and modify the file permissions by connecting via FTP/SFTP.

For your understanding, we have used the free FileZilla FTP program as it is one of the most commonly used FTP clients for WordPress sites. Here are the steps.

  1. Ensure to connect securely to the server.
  2. To view the file permissions, right-click on the WP config file and see the file permissions.
  3. Now right-click on the folder that contains your WordPress files.
  4. Choose the File Attributes in the drop-down list.
  5. Change file attributes window will open, enter 755 or 750in the Numeric value box.
  6. Checkmark the box against Recurse into subdirectories and also select Apply to Directories Only option.
  7. Click Ok.
  8. Now you should repeat the same steps to apply correct permissions for files.
  9. Click the Numeric value box and enter 644 or 640.
  10. Select Recurse into subdirectories and click Apply to files only.
  11. Click Ok.
  12. Next, you must make sure to manually adjust the permissions for your WP-config.php file to 440 or 400.

These steps should resolve the 403 forbidden error if it occurs due to incorrect file permissions.

Step 2. Create a clean and new .htaccess file in WordPress 

Another reason causing  403 forbidden error WordPress is your WordPress site’s .htaccess file. It is a basic configuration file that most web servers like Apache uses to perform relevant operations. However, minor hiccups can cause troubles like popping up of error 403. To fix it, you must try to generate a clean .htaccess file by following the steps below.

  1. First of all, you must connect to your server via File Transfer Protocol.
  2. Now locate .htaccess file.
  3. Make sure to download a copy or create a backup of the file on your local computer.
  4. Now you can delete the .htaccess file from your server.
  5. See if you can now access the WordPress site and follow the below instructions to force WP to generate a new and clean .htaccess file.
  • Open WordPress.
  • Click Settings on the left inside panel and click Permalinks on the dashboard.
  • Click Save Changes at the bottom.

If creating a new .htaccess file and rectifying the file permissions couldn’t resolve the 403 forbidden error, then WordPress plugins could be the culprit. Deactivating and reacting to the plugins might help.

Step 3. Deactivate and reactivate the WordPress plugins 

There might be some chances of bugs in the WordPress plugins or compatibility issues between plugins causing error 403. With some simple trial and error, you can identify the problematic plugin and fix it.

In short, you will need to deactivate all the plugins and reactivate them one by one until you reach the real culprit plugin. You can perform this action directly from the WordPress dashboard and by visiting the plugins area.

However, if you face any difficulty accessing the WordPress dashboard then you must connect to your WordPress site server via FTP. Once you have connected to the FTP follow the below steps.

  1. Locate and open the WP – content folder.
  2. Right-click on the plugins folder and click rename in the drop-down list.
  3. Keep a name that’s easy to remember.
  4. By renaming, you have disabled the plugins at your site and now you can re-access your site, if you can access it, that means one of the plugins is causing 403 forbidden error.
  5. Now start deactivating plugins one by one and eventually during the process you will find a plugin that’s causing the issue.
  6. While renaming the file name you will see the plugins saying the Plugins file does not exist and to fix it you must use the FTP program to rename the folder back to plugins.
  7. In the end, click Activate in front of each plugin and make sure to do it one by one.

Step 4. Temporarily disable the Content Delivery Network (CDN) 

There are several instances when error 403 forbidden happened on the assets like images, JavaScript, CSS. In that case, you must try to temporarily deactivate the Content Delivery Network or CDN. Doing it should resolve the problem, or else you will need to reach out to your WordPress hosting provider.

To Conclude 

So that’s how you can easily deal with 403 Forbidden error. The most likely reason for error 403 is incorrect file permissions (read, write or execute) which you can resolve by modifying via FTP. Beyond that generating a clean and new .htaccess file can work really well in fixing the forbidden error 403. If you are still facing any issue, and don’t want to be in a mess to fix it on your own, then you should connect with our experts at WordPress help. We will help you get rid of error 403 forbidden in no time.

The WordPress Syntax Error is a very general problem that usually occurs, when any kind of mistake has been made by the user. When you make any certain changes in your WordPress site like edited codes with incorrect PHP syntax, updated existing theme, or any plugin files, then also you can face it. However, you are not the only person to receive the parse error in WordPress. There are many more who have reported the same problem. So, don’t freak out! The blog-post teaches you the right way to sort it out. Read to learn!

Actual Reasons Behind Occurrence Of WordPress Syntax Error

The WordPress Syntax Error can be caused by one of the below-listed points:

  • Putting incorrect lines in PHP scripts.
  • Most of the time it happens due to incorrect coding structure.
  • Maybe the punctuations are missing or improperly used in the WordPress site.
  • Invalid variables and wrong function names may also lead to Syntax Error.
  • Either one of the following: Semicolons, curly brackets, or quotations are missing or not properly used in the PHP code.

You can see something like this on the home page of the WordPress website if there is the WordPress Syntax Error:

Parse error: syntax error, unexpected T_FUNCTION in /home/content/94/4245094/html/wp-content/plugins/my-calendar/my-calendar-styles.php on line 465.

Effectual Guidelines To Fix WordPress Syntax Error

Here are the guidelines that will help you out in quick-fixing the WordPress Syntax Error. Let’s give a glance at the underneath provided steps and follow accordingly:

Guideline 1: Disable The New Plugin Or Theme

If the Syntax Error appears once you have recently installed new plugins or edited themes, there’s the possibility that they’re the ones causing the issue. More often this error doesn’t allow you to log into WordPress. That’s why we suggest you use File Transfer Protocol to remove the plugin or theme that you have just changed. Disabling all your plugins is one of the easiest feasible ways to get rid of the Syntax Error In WordPress.

An incorrect updating of a plugin is often the real cause of the Syntax error. If you still have access to your admin area, then simply go to “Plugins” to select the “Deactivate” tab from the action menu. Doing this will instantly disable all your plugins. If that solves the problem, great! You are good to go ahead with flawlessly accessing your WordPress site. If it doesn’t work, jump to the next fixing guideline.

Guideline 2: Fix The Corrupted File From File Manager

Let’s first identify the source of corrupted files and then fix them from the File Manager. Here is what you should perform:

  • First of all, open the “File Manager” option and then navigate to the folder in which the corrupted file is saved. The folder can easily be accessed by navigating to public_html > wp-content > themes > twenty seventeen in the given sequence. If you skip even one, you won’t land on the exact file.
  • Afterward, place a double-tap on the corrupted file and locate the line that is creating trouble. First, launch the ‘index.php’ file and then edit the 72nd line.
  • Once you open that line, you can see a very important part is missing. Maybe a semicolon is missing or not used accurately.
  • In such a condition what you have to do is place the semicolon on the 72nd line as fast as you can.
  • Thereafter, click the “Save” button
  • Now, click “Close” and reload your site.

This time you will surely be able to access your site without any kind of interruption. However, in most cases, simply removing the line can also sometimes eradicate the Syntax Errors. For some instances, there is a comment that is missing and thus is being difficult to translate code. Hence, deleting the complete line will surely fix the error.

However, always be careful if you opt for the option to delete a single line as it may trigger another problem. A line that’s responsible for computing a variable’s value should not be deleted as later it is used.

How To Avoid The WordPress Syntax Error?

Avoiding the Syntax Errors is as easy as annihilating the error but only if you have at least a little bit of knowledge about the PHP. You only have to do is give a serious glimpse of the code for any syntax mistakes. You can check automatically by running it through a PHP code validator. Otherwise, you can check your codes before applying them to a website or converting them into a plugin. Some tips to avoid the most common syntax mistakes:

  • Make sure opening tag and closing tag is placed in each document
  • The extra code shouldn’t be inserted in between a function

Dial 24/7 Online WordPress Support Number For Additional Help

We hope the aforementioned information has helped you in resolving the WordPress Syntax Error. If you still experience the same problem even after followed-up the fixing steps, put a single call at WordPress Support NumberWe will help you with that as well without taking too much time of yours. We are experts in dealing with such types of technical errors. So, feel free to connect with us and get the handy solution at your doorstep.

Coming across a 401 error is common to many of us. However, it turns out to be a big headache sometimes. For instance, if you are running a business and depending upon the website to get new customers, it may not be good news for you. The reason being, you know that the visitors may not be able to order your product from your website. Other reasons can be an inability to subscribe to your service or may miss out on the information about your business on the website. In other words, error code 401 is bad news for a business person on whose website the error message is displayed.

This means you may lose out on the business prospects. It’s an evil omen? In such cases, you might wonder that it would have been good if you could have understood the cause for the error 401 and you could fix it. If you are thinking so, you are on the right path. This article would guide you to work on various prime factors for the error and fix it.

Understanding 401 error

401 unauthorized error may give an impression of a monster in your mind and turning out to be a big hurdle for your business. It is just an HTTP status code. In most scenarios, the error is shown when the server receives an authentication request. That is, invalid credentials have been received on a particular web page of your website. It is usually coupled with a WWW-authenticate header that is in charge of authorization.

In simple terms, the person receiving the error is providing insufficient information to authenticate himself. Connect with the server and hence, he is coming across the error. For example, vital credentials such as username and password are required to login into a certain website. If an appropriate username and password are not provided then, the authenticity is declared as invalid and the error is displayed. The various types of error are 401 unauthorized error; access and authorization denied, and unauthorized HTTP error 401. The error message that is displayed may depend on the request provided to the server.

401 unauthorized error

401 error code due to URL problem

The website must be designed in such a way that there is no interlinking problem between the URL and the website. To elaborate, many times it so happens that the URL is changed frequently by the owner of the website. Hence, the user finds it difficult to locate the website through the old URL. Also, frequent changing of the web pages of the website to enhance the look may not be a good idea always. More importantly, it also affects the ranking of the search engine results.

Even a small change in the URL in the form of a letter may make your website difficult to find for the old customers. The reason being they may be only aware of the old URL and not about the recent changes you have made in the URL. When these factors occur, the server displays the 401 error message.

HTTP error 401 due to login

DNS malfunctioning & firewall issues For login credential problems, there should be a facility for changing the password. This would help to access the website in case of an invalid password. This is one of the reasons why the error message is displayed. Unless valid credentials are fed into the system, the server may not give access to the website. There is also a possibility that an admin related issue occurs on your website.

This means, your website may be asking the user to log in when it will not be needed. A reason can be that, mistakenly, a login page may be created where it is not required at all. The error response can also be due to DNS malfunctioning wherein the domain name system fails. This type of malfunctioning is rare. In certain cases, the website is protected by robust firewalls. Hence, an error message is observed even if a small element of malicious activity is identified. It is also possible that the plug-in within the user’s browser or the website plug-in may be triggering the error.

Comparing 401 error vs other 400s error

There are different types of errors that can be displayed in the 400 range. This indicates that there is some problem on the client-side. A 401 error should not be confused with a 403 error. A 403 error appears only when the user tries to enter the website which is forbidden for him to enter. Conversely, a 401 error may not be related to prohibiting anyone but related to authentication problem access to the website.

Troubleshooting 401 error causes and how to fix error 401?

If your customer is not able to view your website or login into the website, the following ideas can help him:

Refreshing the website:

Ask your customer to refresh the website

Using the latest URL:

Provide your customers with the latest URL. There is a chance that he may be using the wrong or old URL.

Clearing cache:

It must’ve so happened that the website browser must have stored local copies of the old website (URL). This will be different from the live version and hence, the error message will be displayed. Clearing the cache of the website browser helps to get rid of the problems many times. Hence, ask your user to clear up the history and cache. This also helps in decreasing the website loading time and offers a smooth experience to the user.

Clearing cache:

Clearing cookies:

HTTP cookies, functions like cache, helps to cut down web loading time by storing data. Corruption or problems in cookies can lead to an authentication error. Hence, ask your user to clear up the history and cookies, and then, open the website.

Clearing cookies:

Flushing DNS:

Whenever a DNS error occurs, flushing of DNS is required to fix it. Unless this is done, the server will continue to show the error message. Although this is a very rare event related to DNS, it is not difficult to repair

Flushing DNS:

Plug-in problem:

Whenever issues related to plug-ins occur, ask your user to deactivate the plug-in in the web browser. The issue related to the plug-in has to be sent to the support team. It can also be triggered due to any kind of misconduct found by the firewall or antivirus. In such cases, the antivirus or firewall blocks the plugin, as it finds it suspicious due to a plug-in problem. In such cases, the browser itself fails to open or crashes every time you try to open it. The problem can also be due to the compatibility issue arising between the plug-in and the web browser.

Plug-in problem:

Server-level protection:

Get rid of server-level protection through the cPanel if the problem is due to htaccess/htpasswd.

Overcoming password problems:

Sometimes it so happens that the user forgets the password and tries to enter all the possible passwords he could remember. When this happens, the website firewall suspects unusual activity and links it with a malicious form of attack. That’s when it disables the user from further entering the password. Usually, in most of the secure forms of authentication, the users are allowed to enter password thrice. Post three attempts, the website is locked down for a shorter period. The website is usually locked for 24 hours and the user can try to reset the password post 24 hours. Another option is, he can enter the correct password if he remembers it.

Overcoming password problems:

Conclusion:

There can be various reasons why the 401 error code is displayed. The error can be due to URL problem login credentials; DNS malfunctioning; firewall issues; login issues, or DNS problems. For the same, it is necessary that troubleshooting is done to understand the nature of the problem. Although there are many reasons for the error to occur, there is always a way to fix as described above.

Many times, the problem gets sorted out when you clear history, cache, and cookies, and refresh the website. To sum up, sometimes the problem can be fixed very easily, whereas at certain times it may be difficult to find the problem and fix it. But you should not give up as it may affect your business. 401 error can be generated due to some maintenance problem; login or plug-in issues and it cannot be resolved. In the case of WordPress plug-in issues, you can always Contact WordPress Support. Usually, the login issue could be due to the compatibility issue arising between the plug-in and the web browser.

 

Being a WordPress website developer, the situation can be too much terrible for you when you are suddenly unable to access your site for any reason. You can be sometimes preventing from being accessing your WordPress website just because of the Error Establishing A Database Connection WordPressThis is the most common as well as a serious problem most users come up-front usually when WordPress is not able to make a proper connection to the database.

A number of important things can get affected if the connection is lost between WordPress and Database. That’s why; it is required to immediately take an action for solving the error by establishing a database connection in WordPress. In this guide, you will learn the right ways to fix the error. Thus, read it out!

Possible Reasons For The Error Establishing A Database Connection WordPress

There can be a handful of reasons due to which the ‘Error Establishing A Database Connection In WordPress’ occurs. Some of them are listed underneath, check-them out by giving a glance:

  • Wrong database details in your WordPress Settings.
  • Using the corrupted WordPress files could also trigger such a database connection error.
  • Because of the corrupted database.
  • When the database server is down, then also such an error arises.
  • If there is too much traffic on your Website.

WordPress Requires the Following Information To Connect With Database:

  • Name.
  • Username.
  • Password.
  • Server.

Solutions To Quick-Fix The Error Establishing A Database Connection WordPress

Since we value your precious time, that’s why without any delay we are going to describe the effectual solutions in the below so that you can in the pinch fix the Error Establishing A Database Connection. Let’s take a brief look at once and follow the provided directives in an appropriate manner:

Solution 1: Check Your Database Login Credentials

WordPress is one of the prominent open-source content management systems usually uses a database to store all your productive content and other website detail. Though, it is also the fact that for making a connection to the database, the correct login credentials are highly required.

Therefore, if you enter an incorrect either database username or password, the Error Establishing A Database Connection will definitely arise. This is the reason why we suggest you here to first check your database details like your name, username, and password, and database host for 100% correctly inserted. However, you can confirm all this information directly from your WordPress hosting account dashboard. Here is what to do:

  • You just have to log in to your hosting account
  • Then, select the “Databases” option from the left-panel
  • Now, give a single click on “MySQL Databases” link.
  • You will be then directly landed to the database management page. From there, you can find out your database name and the username.
  • And then you will find the database users and links to change the password.
  • You can anytime change the database information in your wp-config.php file whenever it is required.
  • Afterward, visit your WordPress website to check if the Database Connection Error has solved.

If you still see the same error, then this means something else is wrong. Continue reading to find the next solving guide.

Solution 2: Check Your Database Host Information

If it is confirmed by your end that the complete information related to database is correct, then in the next you also have to make sure that you are using the correct database host information. Numerous WordPress hosting companies use localhost as your database host.

However, some managed WordPress hosting companies use specific servers to host databases. In such condition, your database host information will not be localhost. For that, you should contact your WordPress hosting company to ensure about your database host information.

Solution 3: Check If Database Server Is Down

If everything seems to be correct but unfortunately still facing the Error Establishing A Database Connection WordPress, then this time most probably your database server (MySQL server) is down. This could happen most of the time because of heavy traffic on a server.

Generally, your host server cannot handle the load specifically the time when you are on shared hosting. Your site will really go slow and for some users it may even result the database connection error. Therefore the best thing you should do is get on the phone or live chat with your hosting provider and urge them for your MySQL server to be responsive.

Solution 4: Update WordPress Site URL

Another possible solution you are suggested to do is try updating the WordPress site URL using phpMyAdmin. Here is how:

  • Simply access phpMyAdmin from your hosting account dashboard, and select your WordPress database to check the URL for update.
  • Afterward, place a click on the “SQL” menu on the top and enter the following MySQL query. UPDATE wp_options SET option_value=’YOUR_SITE_URL’ WHERE option_name=’siteurl’

Never ever forget to mention your own site URL and change wp_options to your own table name as you may have changed the WordPress table prefix. If now you are able to connect the database, the problem has resolved. But if yet won’t connect, continue fixing using the next solving guide.

Solution 5: Rebooting Web Server

Users on dedicated servers, local servers, and virtual private servers (VPS) can simply try rebooting their Web servers. This will soon restart your web and database server which may fix some temporary glitches including the Error Establishing A Database Connection.

Contact WordPress Support Team To Quick-Fix Database Connection Error

We hope this guide helps in solving the Error Establishing A Database Connection WordPress.  If in case the error is yet persisting, feel free to reach us via 24/7 Online WordPress Support Number. We are a team of highly proficient and well-educated engineers who know better how to deal with customers’ queries. Thus, with no confusion connect with us and get your problem solved in just a second.

 

 

 

Error 521 is an error that is specifically related to Cloudflare that will pop up when the WordPress site’s server will refuse to connect to Cloudflare.

Cloudflare is a CDN that allows you to increase the security and performance of the website so there is a possibility that you might be using it.

You should know that Error 521 is not specifically for Cloudflare and it could also be for the web server.

It means that when the request was directed to Cloudflare and when Cloudflare sent a request to the server- it was incapable of connecting. You will see the error when the server fails to respond.

If your WP website is blocking Cloudflare’s request, then you will come across this error and it could be either Cloudflare’s or the server’s fault.

Error 521

Know how to fix Cloudflare error 521

There are some methods that you can use to fix Error 521

  • Check the webserver

If the issue is from the webserver’s end, then you should if it is working or not. If it is not working, then it is obvious that you will see this error. If you have a number of websites that are hosted on your server then you can see whether the other websites are working or not.

You can also check the status page of the hosting provider. You will get to see all the data in one place. Therefore, if one of the servers fails to work, then you will get to know about it from there.

You will get to know if the webserver is down or it is due to a faulty CDN. You will also get an option to test the webserver in some web hosts from where you can test the webserver.

In the same way, most of the managed hosting or VPS/Dedicated server will offer you an option to check the website. Check the same thing with the terminal, but you should know that this is for advanced users.

  • Switch HTTP to HTTPS

Cloudflare enables the SSL certificate and when you don’t have the certificate, the entire HTTP requests get redirected. Even if you enter HTTPS://xyz.com, it will be redirected to http://xyz.com because of the protocol.

When the SSL is enabled, Cloudflare redirects the websites to HTTPS.

When you enable the SSL, Cloudflare redirects the websites to HTTPS. However, if the definite domain in your WordPress has been set to HTTP then it will be an infinite loop. Cloudflare will try to redirect the URL to HTTPS while the website will try to send the URL to HTTP which will display Cloudflare error 521.

You can fix it by changing the HTTP to HTTPS by going to the WordPress settings. When you navigate to the general settings, you will come across an option to change the URL. You can do it and reload the page. You can also try to reload the website to check if it is working or not.

If it is still not working, then you need to ensure that you don’t have the redirection plugin which is the reason behind this issue. You can deactivate the plugin and then check if Error 521 has been resolved or not.

  • Switch Full SSL to Flexible SSL

When it comes to the SSL certificate, there are a number of options that you can choose from. The first option is the full SSL and the other one is the flexible SSL.

  • If you are using full SSL then you can change it to the flexible SSL with the help of the following steps:
  • Sign in to the dashboard and then click on ‘Crypto’
  • Look at the sidebar where you will see an option to select the SSL
  • Change it from full to flexible
  • Wait till it gets activated and then reload the website
  • .htaccess File

If you have come across some errors in the past then you might have seen that the .htaccess file is involved a couple of times.

You must be aware of the fact that we can’t regenerate the file in order to fix Error 521. You can resolve the error by following the steps mentioned below:

  • Open the file manager from the cPanel
  •  You will come across the .htaccess file but if you don’t see it then you can go to the settings and click on ‘Show hidden files’
  •  Open the file and then click on ‘Code’ edit tab and edit the file

Ensure that no IP address is blocked. Confirm the IP address from Cloudflare.com/ips and no IP address from the list should be blocked.

Conclusion

We hope that with the help of the above-mentioned steps, you will be able to get rid of Error 521. You can reach out to WordPress Support if there is anything else that you require help with.

 

500 internal server error can take place on any web server and is not just limited to a WordPress website. This error usually occurs when a key configuration file like .htaccess file has not been configured properly. It will be displayed to you as:

  • The server is experiencing an internal error or misconfiguration and was unable to finish your request
  • Connect with the server administrator at [address given] to inform them of the time this error happened, and the actions you performed just before this error.
  • More info regarding this error is available in the server error log

How do I fix 500 server error? 

If you come across a 500 Internal Server Error then your primary step should be to check your error logs to determine which file resulted in this error. This will help you to decide whether the best step is to reinstate a backup to bring the site back online or to resolve the issue with the file activating the error.

Locate the Error Logs 

On WP Engine, Your error logs for every environment can be found in your user portal on the WordPress engine. Click on the environment where you faced the error and then choose “Error Logs” from the left-hand side.

Any PHP errors that are formed by your website will show up with the timestamp, IP address and file path which caused the error.

As per on the basis of the information in the error log, you can select to either edit the .htaccess file to resolve the error, or to restore a Backup point to go back to the last point when the website was functioning without an issue.

Edit .htaccess or other website files 

If you select to fix the error by editing a file on your website then you can do this with the help of SFTP. You can initiate by accessing your SFTP client and connecting to your site. Once you form a connection, you can find the right file to make changes to.

Handle timeout error

A timeout can also result in an error message. It is not a web server error but somewhat an interrupted connection to an external source. Are PHP scripts set to access resources from other servers on your website? It could be a possibility that the resource is no longer accessible or server communication is down due to an internal factor. One way to eliminate this source of error is by not making your site dependent on external resources. If this is not likely then you can upsurge the time limit of your script. It also makes sense to implement competent error handling so that errors in the PHP script can be noticed in a much more accurate way.

We hope that we were able to help you out with the 500 server error. If there is something else you require assistance with then do get in touch with the WordPress Support and the experts will assist you in the best possible way.

 

 

 

Before getting to the solution to get rid of the 502 bad gateway error, let’s understand that what it actually is. The HTTP status codes that start with “5” are related to errors that arise when there is a miscommunication between different servers. The reason behind the occurrence of the error might differ but most of the time it happens from the end of the server.

When you get a 502 bad gateway error, it means that the primary server sent an invalid reply to the other server that ended up acting as a proxy or gateway. As all the requests are forwarded through a number of gateways on the net, it can be quite a task to find the root cause of this error. You have nothing to worry about as that is exactly why we are here for you.

Different names of 502 Bad Gateway Error

Before getting to the ways to fix this error, let us see the different names that 502 bad gateway can take up to trouble you.

  • Temporary Error (502)
  • 502 Error
  • Error 502
  • HTTP Error 502 Bad Gateway
  • 502 Server Error: The server encountered a temporary error and could not complete your request
  • 502 – Web server received an invalid response while acting as a gateway or proxy server
  • HTTP 502
  • Bad 502 Gateway
  • 502 Service Temporarily Overloaded
  • 502 Bad Gateway Nginx
  • 502 Proxy Error
  • 502. That’s an error
  • A blank screen

Ways to get rid of 502 bad gateway error 

Even though 502 bad gateway error is related to the issues arising from the server’s side. It can also happen due to misconfiguration or a problem from the side of the client. Therefore, we will be sharing the ways to fix it keeping both the possibilities in mind.

Refresh the page 

This is the easiest way to see if the error is a complicated one or not. Wait for a few minutes and then refresh the page and in most cases, if the error is temporary then it will get fixed by refreshing. You can also see if the website is down or not.

Clear cache and cookies 

This error could also be caused if you have a lot of clutter in the form of cookies and cookies. All you need to do is go to the browser settings and clear the cache and then see if the error persists or not.

Use a different browser 

You can try a different browser or try the private window to see if you are facing the 502 bad gateway due to a browser related issue or not. If it works properly in another browser or the incognito tab then there is a problem with your browser and you can try to update it then see again.

Delete the DNS 

You might be facing the 502 bad gateway error due to a DNS problem such as an incorrect IP address value. If this is the case then you can flush the DNS to flush the error along with it. You can also try to temporarily switch your default DNS server to Google Public DNS. If you have recently changed the hosting of your WordPress site then it can take up to a day to function properly.

Try on another device 

If you have tried a number of solutions to get rid of 502 bad gateway error but none of them seem to work in your favor then. You can try to test the connection on a different device that is connected to a different network. This will provide you with clarity whether the problem is with the device or not.

Check the themes and plugins 

An issue with a certain theme or a plugin can also result in 502 bad gateway error therefore you must check them once. If you still have access to the WordPress dashboard then you should navigate to plugins and then just click on ‘Deactivate’ from ‘Bulk Actions’. Enable the plugins one by one and make it a point to refresh the page after every plugin activation. If you come across the 502 bad gateway error after activating a certain plugin then you know the problem. Another way to find out is by deactivating all the plugins for some time and if the website works after it then you can try to deactivate one by one to find the problematic one.

Check CDNs 

You might be facing the 502 bad gateway error because of CDN (content delivery network) or DDoS (distributed denial of service) mitigation services. This indicates that there is a problem with CloudFlare’s side and in order to resolve it, you should get in touch with their customer support team. As an alternative measure, you can also disable Cloud Flare but keep in mind that the DNS propagation might take a few hours.

We hope that we were able to help you fix the 502 bad gateway error. If you still face any issues then feel free to get in touch with WordPress Support and the experts will help you to handle it.