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.
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?
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?