Warning: inet_pton(): Unrecognized address in /nfs/c04/h06/mnt/59305/domains/exp

Hi @cameeyeopen,

Is it only happening when you’re trying to access your site from the phone’s browser? If so, could you please try with another mobile/browser?

In case this is happening regardless of the device and browser, could you check if the IPv6 Support is enabled for your site:

• Go to the Wordfence Tools page
• Click the Diagnostics tab
• In the Other Tests section, click the link that reads Click to view your system’s configuration in a new window (near the bottom of the page). This will open a Wordfence System Info page.
• On that page, search for the IPv6 Support parameter and check the associated value

I would also suggest you contact your hosting provider to check with them the server’s configuration, in particular the IPv6 setup.

Hi @cameeyeopen,

Since I haven’t heard back from you I am assuming that the instructions helped you solve your issue so I am marking this topic as resolved.

If however, for whatever reason, you are still experiencing this issue and it is not resolved please respond to the post, which will move it back up the queue, and mark this topic as “not resolved”.

Thank you.

I’m seeing this behavior also. It only happens when you access the site with an IPv6 address. IPv4 works fine. I think it’s related to the preblocking option where Wordfence blocks or checks IPs before WordPress loads.

Having done more digging – very weird issue. Two web sites – nearly identical (same company, different subsidiaries in different cities). Same hosting platform/config, same firewall configurations (enhanced).

With option to load wordfence before WordPress, we get a ton of these unrecognized addresses. But with it off, one site gets two of these errors. THe other site works fine. Can’t tell if it’s some bad entry in a dynamic blacklist or something else. The errors only happen with IPv6 access (which is a LOT more common now that Charter and Spectrum have rolled it out for much of their residential base. ) But we’re stumped on how to get rid of these errors. We can’t hide the warnings because they happen before WordPress is loaded (which hides all PHP warnings). Our php.ini on this hosting platform is weird so we can’t easily hide them from there.

This has been an ongoing thing – we’ve seen these errors hit before, then a plugin update fixes them.