Issue with trying to access any links with port info despite turning off Whitelisting

[jrcscores]

Hi guys - This was working fine a few weeks ago, but suddenly stopped working with NO changes to either my code, or my Altervista set-up, by myself?

I turned off the whitelisting ages ago, and opened up server to server communication, but now my attempts to access eg:-

https://ipfs.moralis.io:2053/ipfs/Qm...waMVo/995.json

...result in forbidden (403's)...

If I open this link ANYWHERE else (other hosting options, and locally on my dev machine) it works just fine, but no longer works from my Altervista hosted site?

Can you please urgently look into any possible cause for this? (it's a live service that's now broken)...

...Maybe for some reason it's actually stuck in Whitelisting mode, despite not being set? - (I've tried setting it to Whitelist only, and setting it back to no external restrictions, and no luck?) - I have a test script that shows that this now fails:-

http://jrcscores.altervista.org/proxy_issue_test.php

Which is simply this:-

<?php
header("Access-Control-Allow-Origin: *");

$url = 'https://ipfs.moralis.io:2053/ipfs/QmQQ9W96zfMZ9q4o3CQfCmt2u3dgyHq6PsM8y1jyywaMVo/997.json';
$http_headers = array('Accept: application/json');
$ch = curl_init($url);
curl_setopt($ch, CURLOPT_HTTPHEADER, $http_headers);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);

var_dump($response_);
echo PHP_EOL . PHP_EOL . 'CURL Error : ' . curl_error($ch) . PHP_EOL;

...which now simply gives this, instead of the expected JSON string:-

bool(false) CURL Error : Received HTTP code 403 from proxy after CONNECT

[alemoppo]

Hello, the communication can only work through ports 80 and 443.
The URL has ":2053", so it can't be used to comunicate for security reasons.

Bye!

[jrcscores]

Well, that's great....

So a flat NO? - So I can't grab any content from links with that port? - no way of adding it? - whitelisting it? - It literally just contains JSON data, and it's the ONLY port that Moralis use, to do this on!

I'm sorry, but just a flat NO doesn't really help me out guys?!

The thing is, these NFT's *were* displaying the cross-referenced images fine before? - is this a new security change?

I really need a solution if possible, please?

Cheers...

[alemoppo]

It is not a new security change, it has always been this way on Altervista.

I don't know why your script worked in the past, maybe because the site was also delivered in port 443 or 80 but now returns an error.
There has always been this "limit" on Altervista (for example, you can find it in this forum - 2019).

Bye!