WARNINGS: DNS Query failed and invalid argument supplied for foreach

  • Resolved slywy

    (@slywy)


    1 month ago

    These errors appeared recently. Nothing in the site setup has changed (to my knowledge).

    Warning: dns_get_record(): DNS Query failed in?/usr/home/web/users/username/html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-status/src/class-host.php?on line?149

    Warning: Invalid argument supplied for foreach() in?/usr/home/web/users/username/html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-status/src/class-host.php?on line?151

    Deactivating Jetpack fixes the issue, but would how can it be fixed while keeping the plugin activated?

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @slywy

    The warnings you’re seeing may be related to DNS issues. Please check your DNS settings and ensure they are correctly configured. You can also try clearing your DNS cache. If the issue persists, it might be worth contacting your hosting provider to verify if there are any server-side DNS restrictions or issues.

    For the “Invalid argument supplied for foreach()” warning, ensure that the DNS query returns valid data.

    Since it looks like an warning related to Jetpack, it’d be useful to understand if there’s a conflict with other plugins. Can you please temporarily deactivate all your plugins and check if the problem gets fixed that way? If it works, then reactivate each plugin one by one to find out which one is causing problems.

    If the problem continues, please reply to this thread with more details. Keep in mind that since it’s a warning error, it should not affect your site’s functionality ??

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @slywy,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter slywy

    (@slywy)

    I haven’t been able to resolve it yet. The only way to make it go away so far is to deactivate Jetpack, which I like to use for a few things. The DNS checker shows no DNS issues.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @slywy,

    Thanks for checking the DNS status. Have you contacted your hosting and/or domain provider to ensure everything is well set up on their end, too?

    Did you also get the chance to check for any possible plugin conflict with Jetpack? The fact that the warning goes away when you deactivate Jetpack might signal that there’s something else clashing with our plugin. If you could kindly go through the test, we might be able to narrow down the source of the problem ??

    Since it looks like an warning related to Jetpack, it’d be useful to understand if there’s a conflict with other plugins. Can you please temporarily deactivate all your plugins and check if the problem gets fixed that way? If it works, then reactivate each plugin one by one to find out which one is causing problems.

    If the problem continues, please reply to this thread with more details. Keep in mind that since it’s a warning error, it should not affect your site’s functionality ??

    Let me know what you find out, and we’ll take it from there if necessary. Thanks for sorting this out with us!

    Thread Starter slywy

    (@slywy)

    It looks like WPForms Lite may be the problem . . . this started a couple weeks ago.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hey there, @slywy,

    That’s is progress! If you have found that the warning disappears upon deactivating WP Forms, the issue may lie in its code. If that is the case, I’d recommend reaching out to the plugin authors and see if they can address that. We’re happy to cooperate with them if we can help out!

    Thread Starter slywy

    (@slywy)

    There was an update to Jetpack today, and now it’s working.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @slywy,

    Thanks for the update! We’re very glad to hear the update fixed your problem ??

    The thread is now mark as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.