• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue domain requests are coming from the routing src ip

shreefentsar

New Pleskian
Server operating system version
debian
Plesk version and microupdate number
latest
I have dedicated server from OVH, that has around 40 ip
these 40 ip's are on 3 main routing.

Code:
ip route show
    default via x.y.z.254 dev eno0
    a.b.c.0/24 dev eno0 proto kernel scope link src a.b.c.161
    x.y.b.0/24 dev eno0 proto kernel scope link src x.y.b.74
    x.y.z.0/24 dev eno0 proto kernel scope link src x.y.z.238

so for example I have 16 ip on the routing a.b.c.0/24 ending by 160 to 175

and I have PLESK ( hosting control panel ( like whm/cpanel ))
when I assign any domain to any ip on the routing a.b.c.0/24
then it works good when I ping the domain or open the domain it's ok, but all the requests that's going out from that domain are going to be from the routing source ip whatever the dedicated ip that I assigned to it for example the domain is assigned to a.b.c.162, all the requests that are coming from it ( for example using cron or whatever the server in back-end ( php ) do are coming from a.b.c.161

how can I solve this problem?
 
just in case you came here in my same situation that you have PLESK and lot of ip's
when you add a new ip add it with that way
Code:
x.y.z.xxx/255.255.255.255
that way it will use itself when it's doing outgoing requests.
 
Was the question not how to have a domain running on a specific IP use exactly that same IP when requests are sent outbound from that domain?
 
And how does the code provided solve that? Will the server not still use the default IP address to respond to requests?
 
to explain more :
let's say we want to add this list of ip's:
10.10.10.160
10.10.10.161
and so on until
10.10.10.175
the default way to add it in Plesk using the mentioned OVH subnet mask
it was
10.10.10.175/28
or
10.10.10.175/255.255.255.240

this will result
1690730754128.png
so our network address that will respond or do outgoing requests is
10.10.10.160

but when we add it like that
10.10.10.175/32
or
10.10.10.175/255.255.255.255
this will be the result
1690730853059.png
and this will be our network address that will be used on outgoing requests :
10.10.10.175
 
Back
Top