• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue LoadBalancer problem

Erwan

Regular Pleskian
Hi all,

We need to configure a new project with two servers under Plesk with an upstream load-balancer.
We have configured a first server (a main IP with administration interface + an IP for a test website).

Server :
- IP A : main, for Plesk admin
- IP B : for test website "test.com"

Everything works fine: access to the Plesk admin and access to the website.
We then change the pointing from IP B to the load-balancer. The goal is to pass in this one then to go towards the server and to obtain the Web site.
It works except that we arrive with the domain on the administration interface and not the website.
We had the configuration of the LB checked and everything is correct.

Do you have any idea where the problem is or a way to see what is wrong?

Thank you.

Erwan
 
I have no experience with load balancing but I have played around with high availability proxies a couple of times. Which is in essence, afaik, pretty much the same thing. And it all depend on what method is used by you load balancer to forward traffic. Because the method you're using might require changing some server configuration. Often proxies and load balancers rewrite the origin IP address and use specific headers for (such as X-Forwarded-For) for the client's IP address.

If the administration interface is served instead of the domain content then some how the http request got altered and your web server can't understand the request it gets.
 
Last edited:
Hello, I have the same problem, have you found a solution? I'm testing Digital Ocean and OVh load balancing but in both cases Plesk responds with the defualt page. Thank you
 
Luca,

My problem came from the configuration of the load balancer and the https.
Here is an OVH setting that works. The domain "matches" well at the Plesk level.

> https
> 443
> Datacenter: All
> Default farm: (choice)
> Certificate: choice of the certificate created beforehand in "SSL certificates"
> Advanced settings: check "Enable strict https support"
 
Hi all,
I come back to you because we have just put the load balancer into production. Everything works except this point: the root of the domain in http is not correctly redirected in https. The LB indicates that the server has no response for http (error 503) :

Code:
"https://www.mydomain.com" => ok
"http://www.mydomain.com" => not ok (503)
"https://mydomain.com" => 301 to "https://www.mydomain.com" => ok
"http://mydomain.com" => not ok (503)

In Plesk / Hosting settings, option "Permanent SEO-safe 301 redirect from HTTP to HTTPS " is checked.

Do you see a way to handle this?

Erwan
 
Back
Top