on 10-01-2024 20:55
Cannot access Skipton Building Society for intermediaries website on wifi but can on mobile data (Vodafone). So it has to do with Virgin. Site address: https://www.skipton-intermediaries.co.uk/
Any solutions?
on 11-01-2024 01:02
@Cloudy_1 wrote:curl -I https://www.skipton-intermediaries.co.uk
curl: (28) Failed to connect to www.skipton-intermediaries.co.uk port 443 after 75054 ms: Couldn't connect to server
curl -I https://www.skipton-intermediaries.co.uk
curl: (28) Failed to connect to www.skipton-intermediaries.co.uk port 443 after 75040 ms: Couldn't connect to server
Consider contacting the site operator to confirm they are blocking your public IP Address and requesting it be delisted.
on 11-01-2024 12:42
This is a large financial institution. Anyone I speak to on client line is not going to know who the server operators are. Why would a large financial organisation block a public address of a major internet provider. It is all very confusing,
on 11-01-2024 12:42
Is anyone working for Virgin on this blog?
on 11-01-2024 13:17
@Cloudy_1 wrote:This is a large financial institution. Anyone I speak to on client line is not going to know who the server operators are. Why would a large financial organisation block a public address of a major internet provider. It is all very confusing,
They will have escalation paths to raise such an issue; if not then you will need to raise as a complaint with them.
The organisation has blocked your public IP Address and not those of other Virgin Media customers as evident from other posts — they do this to protect their network from malicious activity originating from the blocked IP Address.
on 11-01-2024 18:41
They could block based on user agent. Which is why I wouldn't have recommended sending HTTP requests to a bank's web server using curl.
on 12-01-2024 16:25
What do you suggest?
on 12-01-2024 17:30
@asim18 wrote:They could block based on user agent. Which is why I wouldn't have recommended sending HTTP requests to a bank's web server using curl.
Possible but not borne out by my experience of using curl against site; it seems likely that simple troubleshooting steps will fail to trip the site's safe guarding precautions against malicious activity.