cURL "couldn't connect to host"

[AndyKay]

btw, I can get file_get_contents to work on ANY other URL with the host I'm using

[AndyKay]

I have another URL for the same API but using https:

https://123.456.789.123:444/something

[bradgrafelman]

AndyKay;10985171 wrote:

btw, I can get file_get_contents to work on ANY other URL with the host I'm using

Do those other working URLs attempt to connect on port 555?

[bradgrafelman]

AndyKay;10985172 wrote:

I have another URL for the same API but using https:

https://123.456.789.123:444/something

Again, same problem; the use of a non-standard port is likely going to get blocked by the server's firewall.

[AndyKay]

No other working URLs attempt to connect via a specific port.

So you think its the port number which is causing the problems then? I'll try get the company to change ports. What number do you suggest?

[bradgrafelman]

AndyKay;10985176 wrote:

What number do you suggest?

Unless they have valid reasons to choose otherwise (and they may very well have such reasons), I would think the standard ports for HTTP or HTTPS would be more reasonable for a public-facing interface.

[AndyKay]

bradgrafelman;10985174 wrote:

Again, same problem; the use of a non-standard port is likely going to get blocked by the server's firewall.

When you mention "blocked by the server's firewall" - do you mean my host server or the server I'm trying to connect to?

(I have minimal experience of ports) :queasy:

[bradgrafelman]

AndyKay;10985178 wrote:

When you mention "blocked by the server's firewall" - do you mean my host server or the server I'm trying to connect to?

The remote server you're connecting to obviously isn't blocking all incoming connections on that port if you yourself can access it from your own PC.

It's the server where your PHP code is running on that I was referring to above. In that case, the server's firewall might not allow the outgoing connection your PHP script is attempting to make on a non-standard port. Hence why I asked if you were executing this PHP code locally on your own PC or remotely on some other server.

[AndyKay]

Well thanks for your help with being able to narrow it down to the port number.
Its very weird that even if you specify which port to use (CURLOPT_PORT) it still doesnt work.

I'll email them and hopefully they'll reconfigure to not specify a port to use

P.S. how do I edit the above posts to remove the URL?

[AndyKay]

bradgrafelman;10985179 wrote:

The remote server you're connecting to obviously isn't blocking all incoming connections on that port if you yourself can access it from your own PC.

It's the server where your PHP code is running on that I was referring to above. In that case, the server's firewall might not allow the outgoing connection your PHP script is attempting to make on a non-standard port. Hence why I asked if you were executing this PHP code locally on your own PC or remotely on some other server.

Ah. OK. Thanks for that 🙂

I'm testing it on a couple of hosts - 1and1 and JustHost

[bradgrafelman]

AndyKay;10985181 wrote:

P.S. how do I edit the above posts to remove the URL?

The edit feature is disabled for newly-registered users, but I've edited the previous posts for you.

AndyKay;10985182 wrote:

I'm testing it on a couple of hosts - 1and1 and JustHost

Yes, a large majority of shared hosts are extremely likely to block connections on non-standard ports. More than likely their support would just tell you to purchase a VPS or whatnot as your needs have grown beyond the vanilla shared hosting scenario (translation: "We would like more of your money, please and thank you.").