• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue ISP Blocking

Anoop

Regular Pleskian
Server operating system version
Centos 79
Plesk version and microupdate number
18.0.44
We are managing more than 200 Plesk servers. And most of these servers are not available on jio network in in India. Anyone knows any idea on these cases.
 
If Plesk server is accessible on the same device with another ISP, you can troubleshoot the connection issue connected to Jio ISP and report it to them directly or report it to a data center where Plesk server is hosted. If you find that there are some Plesk specific issues, reply to this thread
 
If Plesk server is accessible on the same device with another ISP, you can troubleshoot the connection issue connected to Jio ISP and report it to them directly or report it to a data center where Plesk server is hosted. If you find that there are some Plesk specific issues, reply to this thread
i think, its a plesk server issue. Bcoz, am facing it on multiple plesk servers.
 
When you say they're not available, what do you mean exactly? What's the exact error they get when trying to access the sites?
 
When you say they're not available, what do you mean exactly? What's the exact error they get when trying to access the sites?
Server is blocked by a particular isp provider. Not opening websites on JIO ISP Provider in India. All these happening in Linux Plesk server only. Same issues reported from many places on plesk servers.
 
Do you get ERR_CONNECTION_TIMED_OUT, or 502 gateway error, or something else? Send a screenshot
 
Do you get ERR_CONNECTION_TIMED_OUT, or 502 gateway error, or something else? Send a screenshot
This error only on a particular isp or internet provider. All other providers have no issues.
 

Attachments

  • Screenshot_5.jpg
    Screenshot_5.jpg
    26 KB · Views: 8
  1. How long has this been happening? A day, a week, a month?
  2. Do you host all Plesk servers on the same subnet or different ones?
  3. Is Plesk the only type of server you host, or do you host any other?
 
  1. How long has this been happening? A day, a week, a month?
  2. Do you host all Plesk servers on the same subnet or different ones?
  3. Is Plesk the only type of server you host, or do you host any other?
1. Started from two weeks.
2. hosted on different subnet and different locations and data centers.
3. hosted plesk, cpanel, directadmin servers. But this issue happens only on plesk servers and plesk VMs
 
Two weeks is too long for a DNS propagation issue. How do you manage DNS? Is it handled by Plesk or externally, and is it handled the same for all Plesk servers?
 
Two weeks is too long for a DNS propagation issue. How do you manage DNS? Is it handled by Plesk or externally, and is it handled the same for all Plesk servers?
DNS is handled by plesk and this issue is for all plesk servers
 
It sounds like an issue with the Jio DNS servers. They're known to block many sites, but that'd depend on the content, I suppose.
  1. Get the Jio DNS servers. You can start with the ones here: DNS servers in India
  2. Then see if they resolve to your Plesk IP addresses:
    • On Windows:
      Code:
      nslookup domain.com <jio_ip_address>
    • On Linux:
      Code:
      dig domain.com @<jio_ip_address> +short
If it returns your server's IP address, then it's resolving properly, and must be an issue with Plesk. If it doesn't, then it's something on the DNS servers from Jio. In that case, nothing to do besides contacting them for clarification.

If it's Plesk, it might be a firewall thing. Log the exact time when someone gets this error and look it up in the domain access log /var/www/vhosts/example.com/logs/access_ssl_log or proxy_access_ssl_log to get the IP address.

Once you have the IP address, check the Fail2Ban and ModSecurity logs and see if it appears in either and use the respective guide:
Then try again and see if the error is resolved. You may want to disable Fail2Ban if it's blocking a lot of people.
 
Back
Top