In today’s world, communication is much faster. Faster websites also make users happy.

Here is the role of the Plesk reverse proxy server that helps you download a website faster.

It also improves the performance of the website by assigning customer requests to the appropriate back-end servers.

That’s why our support engineers offer reverse proxy as one of the server modifications for our customers.

Today we will see how our technical team will install Plesk’s reverse proxy and fix the related bugs.

What is reverse proxy?

Before we go into the details of the Plesk Reverse Proxy Server, we will first learn more about the Reverse Proxy Server and its functions.

The reverse proxy server acts as an identification tag between the client computer and the internal web servers. These web servers store current data for websites. This allows client requests to be forwarded to the appropriate internal server.

Load balancing is one of the most common applications of reverse proxy for web applications. It also helps customers protect their important information from hacker attacks. So it serves as extra protection against cyber attacks.

In addition, the reverse proxy ensures that network traffic between customers and servers runs smoothly. This is enough for every server owner to set up a reverse proxy. Fortunately, Plesk also offers possibilities to install a reverse proxy.

How we installed and enabled the Nginx reverse proxy on the Pleskserver

Let’s see how our support engineers installed Nginx as a reverse proxy on the Plesk client server. The exact sequence of commands executed on Plesk was as follows

1. Select Tools and Settings from the Plesk menu and click Updates and Upgrades.

2. Then click the Add/Remove Items button.

3. Then select the Nginx web server you want to install. Then press Next to start the installation.

4. After installation, we need to enable the Nginx reverse proxy service on Plesk. Before that:

  • We have chosen Tools & Settings > Service Management.
  • Finally, click on the button next to the reverse proxy server (nginx).

It took a while to set it up. And Nginx was installed on the server as a reverse proxy.

Troubleshooting – Problems after activating Nginx as proxy on server

Based on our experience with server management, we have found that many customers have all kinds of problems with the Plesk reverse proxy server.

Let’s see how our support team dealt with such mistakes.

1. Error on the website due to IP blocks

Recently one of our customers contacted us to repair his server. His pages had errors like 502 Bad Gateway. It started after Nginx was activated on the server.

This is where our support staff first had to find the exact question.

1. We first analyzed the log of a proxy, such as /var/www/vhosts/system/example.com/logs/proxy_error_log.

We found the following message,

Plesk Reverse Proxy-Common Errors and Right Fix to it

2. Again, we checked the system logs /var/log/messages. We’ve received another error regarding the IP block.

12. November 07:59:12 wh01 xxx: nginx failed, cannot open connection to INET [0.0.0.80].

3. So the next step was to check if the IP was blocked. Fail2ban is installed on the server and helps protect servers from brute force attacks.

4. Finally, we also checked the Fail2Ban logs to identify the problem and found the following entry in /var/log/fail2ban.log

2019-8-12 05:45:57.699 fail2ban.filter [10036] : INFO [plesk-apache-badbot] Found 0.0.0.

5. We have identified the cause of the problem as Fail2Ban, which blocks the IP address on the server.

In addition, after identifying the problem, our support engineers added the IP address to the trusted IP addresses. And that solved the problem.

2. ERR_CONNECTION_REFUSED.

In the same way the Plesk reverse proxy server can often create messages such as ERR_CONNECTION_REFUSED when accessing websites.

For a detailed diagnosis we have the following entry in /var/www/vhosts/domain.com/logs/proxy_error_log

Plesk Reverse Proxy-Common Errors and Right Fix to it

However, there was no listening process on port 80, which means the Nginx service did not work.

Finally, we restarted the Nginx service, which solved the problem.

Our Plesk experts can help you].

Conclusion

In short: Plesk Reverse Proxy helps to balance the load, improve security and speed up your website. Today we saw our support engineers install the Plesk reverse proxy on a Plesk server and fix the corresponding problems.plesk 502 bad gateway error,connect() failed (111: connection refused) while connecting to upstream plesk

Share: