API didn't return a valid IPv4 addres about dynamic-dns-netcup-api HOT 5 CLOSED

Hello Lars,
same error here.
Changing
$publicIP = rtrim(file_get_contents('https://api.ipify.org'));
to
$publicIP = rtrim(file_get_contents('https://api64.ipify.org'));
is unsuccessfull.

Any idea?

from dynamic-dns-netcup-api.

@Stephan2612 Please post full error message.

And don't use api64…

• api4.ipify.org: IPv4 only
• api6.ipify.org: IPv6 only
• api64.ipify.org: IPv4/IPv6 dual stack

Anyways, I'm unable to reproduce the errors while trying to fetch these URLs with cURL. (And with different/empty --user-agent values.)

from dynamic-dns-netcup-api.

As you see cURL https://api.ipify.org doesn't do the job

from dynamic-dns-netcup-api.

@killerbees19
my full error message has looked exactly like that of kinoegit (of course with other domainnames ;)

Meanwhile, I have found the error, although I am wondering how it can happen while I am on holiday and no one has changed any configuration: Pi-hole was blocking api.ipify.org and ip4.seeip.org. Why? I don´t know.

Thank you, killerbees19, for your offer of help.

from dynamic-dns-netcup-api.

@Stephan2612
thanks, you're right! same here: AdGuard blocked https://api.ipify.org/. Seems to be a new and false entry in AdGuards DNS filterlist I reckon.
Issue solved

from dynamic-dns-netcup-api.