does infinityfree has a fixed outbound public IP used by PHP cURL requests when my website connects to an external server, or is the outbound IP different or shared?
does infinityfree has a fixed outbound public IP used by PHP cURL requests when my website connects to an external server, or is the outbound IP different or shared?
Welcome to the InfinityFree community forum! Good to have you here.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
I couldn’t find anything in the knowledge base or on the forum that says whether outbound cURL requests from InfinityFree use a fixed IP, a shared one, or one that changes. I don’t want to guess, so I can’t answer that part yet.
What are you trying to do with it? If the external server needs to whitelist an IP, or a cURL request is failing, tell me which. For a failing request, please include the exact error text or the cURL error message. That would show whether the outbound IP is the actual problem or something else is going on.
I can’t say if it’s fixed, but given that the hosting ip’s are shared, I’d hazard a guess that the IP for any outbound connections is shared
The IP addresses are 100% shared. We host hundreds of thousands of websites completely for free, and using a different IP address for every single one is both crazy expensive and completely unnecessary.
I don’t know exactly how the external IPs are set up. I don’t think they change often. I know that they are not the same as your Website IP, and I think the best way to find the right IP is to use a bit of PHP code to grab it from an IP lookup tool, e.g.
<?php echo file_get_contents('http://ifconfig.me');
In any case, I recommend that you do not rely on IP whitelisting for security if you can avoid it. The IP addresses are not guaranteed to remain consistent, and are definitely shared with other websites. So using actual authentication is a lot more secure and much less likely to break.
Hello InfinityFree Support,
I am hosting my website on InfinityFree and need it to communicate with an external VPS running a licensing API.
The API is listening on TCP port 3008. My VPS provider has confirmed that the port is accessible from external computers, but a PHP fsockopen() test from my website to the VPS timed out with error 110.
Could you please confirm whether InfinityFree blocks outbound TCP connections to port 3008?
Are outbound connections to ports 80 or 8080 permitted for communicating with an external API? Does InfinityFree support PHP cURL requests to external HTTP APIs?
I would appreciate your recommended approach for securely connecting my website to this VPS.
Thank you.
Does not seem like a valid use case
Most outbound ports are blocked. Please use plain HTTP/S requests (so with port 80 and 443) as simple cURL requests are still allowed.
@KangJL outbound not inbound, please do not freak out when seeing “API”
It’s perfectly fine. Plenty of non-free software needs to interact with an external licensing server to see if you have a valid license and what features are available to you, and they refuse to work if they can’t tell.
But like @Meishin said: you can use PHP cURL to connect to external APIs, but only on standard HTTP and HTTPS ports. So port 80 is fine, but port 8080 and 3008 are blocked.
Hello InfinityFree Support,
I am integrating the NOWPayments sandbox API with my PHP website, tuckea.free.nf.
I created a PHP cURL connection test to https://api.sandbox.nowpayments.io/v1/status.
The test returns:
HTTP status: 0
SSL certificate problem: certificate has expired
Could you please help me determine whether the problem is caused by the CA certificate bundle or SSL configuration on the hosting server, or by the remote server’s certificate chain?
I need to maintain proper SSL certificate verification for a secure payment integration. I do not want to disable SSL verification.
Thank you.
Please pay careful attention to the error you get. It says certificate has expired. That’s not an error with the CA bundle (that would give you an “unknown issuer” error), it’s a problem of the certificate being returned having an expiration date that’s before the current server time.
The first thing to then check is to see what the SSL certificate of the host actually says. However, the host api.sandbox.nowpayments.io does not appear to exist at all, no DNS records appear to have been setup for it.
Hello InfinityFree Support,
I am integrating NOWPayments IPN notifications with my PHP website at tuckea.free.nf.
My payment handler is: https://tuckea.free.nf/nowpayments_ipn_secure_candidate_v2.php
When a Cloudflare Worker makes a server-to-server GET request to this endpoint, InfinityFree returns HTTP 200 with an HTML JavaScript challenge that loads /aes.js, instead of allowing the PHP endpoint to return its expected JSON response.
This may also be preventing NOWPayments IPN notifications from reaching my PHP handler correctly.
Is there a supported way to allow legitimate server-to-server POST requests to this PHP endpoint without the browser JavaScript challenge? If this is not supported on free hosting, please let me know what hosting option would support it.
Thank you.
All automated access to websites on free hosting is blocked. This includes IPN and other webbooks.
This only applies to free hosting, all premium plans from iFastNet do not have this restriction.