errors accessing the site administration

  • Resolved almendron

    (@almendron)


    1 year, 4 months ago

    Server: local.
    WordPress: 6.7.1
    Jetpack: 14.3
    PHP: 8.2.4

    Errors:
    ( ! ) Warning: dns_get_record(): DNS Query failed in C:\wamp64\www\artehistoria\wp-content\plugins\jetpack\jetpack_vendor\automattic\jetpack-status\src\class-host.php on line 149

    ( ! ) Warning: foreach() argument must be of type array|object, bool given in C:\wamp64\www\artehistoria\wp-content\plugins\jetpack\jetpack_vendor\automattic\jetpack-status\src\class-host.php on line 151

    Errors prevent access to the control panel options.

    Note: the error is intermittent.

    • This topic was modified 1 year, 4 months ago by almendron.
Viewing 15 replies - 1 through 15 (of 20 total)
1 2
  • Plugin Support Chatoxz (a11n)

    (@chatoxz)

    1 year, 4 months ago

    Hello there,
     
    Sebastian from Jetpack here. I hope you are doing well, and thanks for reaching out.

    For the first warning, the “dns_get_record(): DNS Query failed” warning indicates that the function was unable to retrieve DNS records for the specified domain, often due to an invalid domain name or a network issue. 

    For the second warning we will need to take a closer look. Could you please post your site URL here so that we can have a look?

    If you want it to remain private, you can also contact us via this contact form:

    https://jetpack.com/contact-support/?rel=support&hpi=1

    If you choose to reach out directly, please include a link to this thread.

    That said, these are warnings and should not be an issue when accessing your site. If you cannot get into your WP Admin dashboard, you should look at the error logs for more details.

    Let us know what you find out.

    Warm regards,

    Thread Starter almendron

    (@almendron)

    1 year, 4 months ago

    I work the local. I have three sites with the same theme. Also with the same plugins.
    The error only appears on one of them. I have deactivated all plugins except JetPack and activated the Twenty Twenty-Three theme. The error does not disappear.

    I can access the administration, but the error information pushes the menu down and the options cannot be accessed.
    The error information is displayed even if I select ‘false’ for WP_DEBUG.

    View full error log

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    Have you found the solution?

    I have found that the error has been reported by more people.

    Example: https://ww.wp.xz.cn/support/topic/dns_get_record-warning-on-localhost/

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    1 year, 3 months ago

    Hey there, @almendron,

    Thanks for the follow-up – we’re still investigating both your case and the one you linked.

    We tried to access the logs you linked above, but we got a Forbidden page; would you like to send us a file via email? You can use this contact form and mention this thread so we can connect the dots.

    That said, can you confirm the following for me?

    • are your site on Offline mode at all?
    • does the warning persists if you deactivate and delete Jetpack entirely, and then trying to reinstall it? To remove Jetpack, you can FTP into your site and delete the folder wp-content/plugins/jetpack. (If you’re not sure how to do this, ask your hosting company for help.) After that’s done, you can reinstall Jetpack by following these instructions.
    • have you reported this to your hosting provider? The intermittent nature of the issue would suggest that it could be due to a server settings that needs to be addressed.

    As my colleague mentioned above, it would be very useful for us to examine your site directly, so it would be great if you could share your URL.

    Let me know what you find out, and thanks for sorting this out with us!

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    Intermittent error: My mistake. On one of the sites I deactivated the plugin and I thought it was fixed. The error is permanent.

    I deactivate JepPack: error disappears
    Delete – Install – Activate: error returns

    are your site on Offline mode at all? Yes.

    have you reported this to your hosting provider? I work on local (localhost with wampserver).
    It is not a wampserver problem as the error only appears on two of the three sites.

    Forbidden page. I don’t get it. I upload the file with TXT extension: https://www.almendron.com/compartir/jetpack/debug.txt
    Please confirm that it is legible now

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    I have discovered the following: if I activate the ‘Query Monitor’ plugin, then the error disappears.

    This plugin was the only difference between the three sites. The error did not occur on the one where this plugin was installed.

    *********************************

    Correction: the error persists but is no longer displayed. The ‘Query Monitor’ plugin shows the two warnings.

    • This reply was modified 1 year, 3 months ago by almendron.
    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    1 year, 3 months ago

    Hi there, @almendron,

    Thanks for the follow-up – if I get this all right, the issue persists despite it’s not flagged by the Query Monitor plugin, am I correct?

    If so, we still would like to investigate it to understand what’s causing it since it seems to be related to Jetpack.

    We checked the new link you shared where there should be the error logs, but this time we got a Pagina de error:

    https://cloudup.com/c0UIe5aYsSp

    If it helps sharing the error logs, as we can’t access the pages you shared where the logs should be present, you could contact us via contact form. (If you choose to reach out directly, please include a link to this thread).

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    You are spelling the URL wrong. It’s not “/compartir/jetpack/debug.txtPlease“

    91.201.160.79:49878 - - [12/Feb/2025:13:55:06 +0100] "GET /compartir/jetpack/debug.txtPlease HTTP/2.0" 302 192 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36" 507 "0.012/s"

    but “/compartir/jetpack/debug.txt”

    https://www.almendron.com/compartir/jetpack/debug.txt

    Query Monitor enabled: the error is not displayed on the screen, but the plugin reports both errors.

    [07-Feb-2025 170143 UTC] PHP Warning  dns_get_record() DNS Query failed in Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php on line 149
    [07-Feb-2025 170143 UTC] PHP Stack trace
    [07-Feb-2025 170143 UTC] PHP   1. {main}() Cwamp64wwwblogwp-adminindex.php0
    [07-Feb-2025 170143 UTC] PHP   2. require_once() Cwamp64wwwblogwp-adminindex.php137
    [07-Feb-2025 170143 UTC] PHP   3. do_action($hook_name = 'admin_print_scripts') Cwamp64wwwblogwp-adminadmin-header.php148
    [07-Feb-2025 170143 UTC] PHP   4. WP_Hook-do_action($args = [0 = '']) Cwamp64wwwblogwp-includesplugin.php517
    [07-Feb-2025 170143 UTC] PHP   5. WP_Hook-apply_filters($value = '', $args = [0 = '']) Cwamp64wwwblogwp-includesclass-wp-hook.php348
    [07-Feb-2025 170143 UTC] PHP   6. AutomatticJetpackAssetsScript_Datarender_script_data('') Cwamp64wwwblogwp-includesclass-wp-hook.php324
    [07-Feb-2025 170143 UTC] PHP   7. AutomatticJetpackAssetsScript_Dataget_admin_script_data() Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-assetssrcclass-script-data.php86
    [07-Feb-2025 170143 UTC] PHP   8. apply_filters($hook_name = 'jetpack_admin_js_script_data', $value = ['site' = ['admin_url' = 'httplocalhostblogwp-admin', 'date_format' = 'l, j de F de Y', 'icon' = '', 'is_multisite' = FALSE, 'plan' = [...], 'rest_nonce' = '3165104b8d', 'rest_root' = 'httplocalhostblogwp-json', 'title' = 'Bitácora Almendrón', 'wp_version' = '6.7.1', 'wpcom' = [...]], 'user' = ['current_user' = [...]]]) Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-assetssrcclass-script-data.php146
    [07-Feb-2025 170143 UTC] PHP   9. WP_Hook-apply_filters($value = ['site' = ['admin_url' = 'httplocalhostblogwp-admin', 'date_format' = 'l, j de F de Y', 'icon' = '', 'is_multisite' = FALSE, 'plan' = [...], 'rest_nonce' = '3165104b8d', 'rest_root' = 'httplocalhostblogwp-json', 'title' = 'Bitácora Almendrón', 'wp_version' = '6.7.1', 'wpcom' = [...]], 'user' = ['current_user' = [...]]], $args = [0 = ['site' = [...], 'user' = [...]]]) Cwamp64wwwblogwp-includesplugin.php205
    [07-Feb-2025 170143 UTC] PHP  10. AutomatticJetpackPublicizePublicize_Script_Dataset_admin_script_data($data = ['site' = ['admin_url' = 'httplocalhostblogwp-admin', 'date_format' = 'l, j de F de Y', 'icon' = '', 'is_multisite' = FALSE, 'plan' = [...], 'rest_nonce' = '3165104b8d', 'rest_root' = 'httplocalhostblogwp-json', 'title' = 'Bitácora Almendrón', 'wp_version' = '6.7.1', 'wpcom' = [...]], 'user' = ['current_user' = [...]], 'connection' = ['apiRoot' = 'httplocalhostblogwp-json', 'apiNonce' = '3165104b8d', 'registrationNonce' = '9a47455013', 'connectionStatus' = [...], 'userConnectionData' = [...], 'connectedPlugins' = [...], 'wpVersion' = '6.7.1', 'siteSuffix' = 'localhostblog', 'connectionErrors' = [...], 'isOfflineMode' = TRUE, 'calypsoEnv' = '']]) Cwamp64wwwblogwp-includesclass-wp-hook.php324
    [07-Feb-2025 170143 UTC] PHP  11. AutomatticJetpackStatusHost-get_known_host_guess() Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-publicizesrcclass-publicize-script-data.php73
    [07-Feb-2025 170143 UTC] PHP  12. AutomatticJetpackStatusHost-get_hosting_provider_by_nameserver($domain = 'localhost') Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php273
    [07-Feb-2025 170143 UTC] PHP  13. AutomatticJetpackStatusHost-get_nameserver_dns_records($domain = 'localhost') Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php219
    [07-Feb-2025 170143 UTC] PHP  14. dns_get_record($hostname = 'localhost', $type = 2) Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php149
    [07-Feb-2025 170143 UTC] PHP Warning  foreach() argument must be of type arrayobject, bool given in Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php on line 151
    [07-Feb-2025 170143 UTC] PHP Stack trace
    [07-Feb-2025 170143 UTC] PHP   1. {main}() Cwamp64wwwblogwp-adminindex.php0
    [07-Feb-2025 170143 UTC] PHP   2. require_once() Cwamp64wwwblogwp-adminindex.php137
    [07-Feb-2025 170143 UTC] PHP   3. do_action($hook_name = 'admin_print_scripts') Cwamp64wwwblogwp-adminadmin-header.php148
    [07-Feb-2025 170143 UTC] PHP   4. WP_Hook-do_action($args = [0 = '']) Cwamp64wwwblogwp-includesplugin.php517
    [07-Feb-2025 170143 UTC] PHP   5. WP_Hook-apply_filters($value = '', $args = [0 = '']) Cwamp64wwwblogwp-includesclass-wp-hook.php348
    [07-Feb-2025 170143 UTC] PHP   6. AutomatticJetpackAssetsScript_Datarender_script_data('') Cwamp64wwwblogwp-includesclass-wp-hook.php324
    [07-Feb-2025 170143 UTC] PHP   7. AutomatticJetpackAssetsScript_Dataget_admin_script_data() Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-assetssrcclass-script-data.php86
    [07-Feb-2025 170143 UTC] PHP   8. apply_filters($hook_name = 'jetpack_admin_js_script_data', $value = ['site' = ['admin_url' = 'httplocalhostblogwp-admin', 'date_format' = 'l, j de F de Y', 'icon' = '', 'is_multisite' = FALSE, 'plan' = [...], 'rest_nonce' = '3165104b8d', 'rest_root' = 'httplocalhostblogwp-json', 'title' = 'Bitácora Almendrón', 'wp_version' = '6.7.1', 'wpcom' = [...]], 'user' = ['current_user' = [...]]]) Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-assetssrcclass-script-data.php146
    [07-Feb-2025 170143 UTC] PHP   9. WP_Hook-apply_filters($value = ['site' = ['admin_url' = 'httplocalhostblogwp-admin', 'date_format' = 'l, j de F de Y', 'icon' = '', 'is_multisite' = FALSE, 'plan' = [...], 'rest_nonce' = '3165104b8d', 'rest_root' = 'httplocalhostblogwp-json', 'title' = 'Bitácora Almendrón', 'wp_version' = '6.7.1', 'wpcom' = [...]], 'user' = ['current_user' = [...]]], $args = [0 = ['site' = [...], 'user' = [...]]]) Cwamp64wwwblogwp-includesplugin.php205
    [07-Feb-2025 170143 UTC] PHP  10. AutomatticJetpackPublicizePublicize_Script_Dataset_admin_script_data($data = ['site' = ['admin_url' = 'httplocalhostblogwp-admin', 'date_format' = 'l, j de F de Y', 'icon' = '', 'is_multisite' = FALSE, 'plan' = [...], 'rest_nonce' = '3165104b8d', 'rest_root' = 'httplocalhostblogwp-json', 'title' = 'Bitácora Almendrón', 'wp_version' = '6.7.1', 'wpcom' = [...]], 'user' = ['current_user' = [...]], 'connection' = ['apiRoot' = 'httplocalhostblogwp-json', 'apiNonce' = '3165104b8d', 'registrationNonce' = '9a47455013', 'connectionStatus' = [...], 'userConnectionData' = [...], 'connectedPlugins' = [...], 'wpVersion' = '6.7.1', 'siteSuffix' = 'localhostblog', 'connectionErrors' = [...], 'isOfflineMode' = TRUE, 'calypsoEnv' = '']]) Cwamp64wwwblogwp-includesclass-wp-hook.php324
    [07-Feb-2025 170143 UTC] PHP  11. AutomatticJetpackStatusHost-get_known_host_guess() Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-publicizesrcclass-publicize-script-data.php73
    [07-Feb-2025 170143 UTC] PHP  12. AutomatticJetpackStatusHost-get_hosting_provider_by_nameserver($domain = 'localhost') Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php273
    [07-Feb-2025 170143 UTC] PHP  13. AutomatticJetpackStatusHost-get_nameserver_dns_records($domain = 'localhost') Cwamp64wwwblogwp-contentpluginsjetpackjetpack_vendorautomatticjetpack-statussrcclass-host.php219
    Plugin Support lastsplash (a11n)

    (@lastsplash)

    1 year, 3 months ago

    Hi @almendron –

    Have you added the define( 'JETPACK_DEV_DEBUG', true ); line to your site’s wp-config.php? If not, please try that (instructions here). That should prevent the failing DNS lookup.

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    I have added define( 'JETPACK_DEV_DEBUG', true ); and the error persists

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    1 year, 3 months ago

    Hi @almendron –

    Thanks for giving that a try.

    I’ve asked our development team to take a look, and we’ll let you know here as soon as we have a response.

    Thanks for your patience so far.

    (Internal Reference #: JP-ISS-9550)

    • This reply was modified 1 year, 3 months ago by lastsplash (a11n). Reason: added internal reference
    Plugin Support Animesh Gaurav

    (@bizanimesh)

    1 year, 3 months ago

    Hey @almendron – since you are using Jetpack in offline mode, for now, could you please go to wp-config.php file and add these there:

    define('WP_DEBUG', false);
    define('WP_DEBUG_DISPLAY', false);

    If these are already added there. then please just change true value to false as mentioned above. And if you don’t see them there, then please add them just before the /* That's all, stop editing! Happy publishing. */ line.

    Once you turn off the offline mode, you may change these values to true later and check if the error still shows when you are not running Jetpack in offline mode.

    Reference for us: gh-9550-jpop-issues

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    Test number 1:
    Query Monitor plugin activated – WP_DEBUG and WP_DEBUG_DISPLAY false.
    Errors are not displayed on the screen. The plugin reports the two errors in the corresponding section.

    Test number 2:
    Query Monitor plugin deactivated
    WP_DEBUG and WP_DEBUG_DISPLAY: It does not matter whether it is ‘false’ or ‘true’. The result is the same: Errors are displayed on the screen. The error description pushes the menu down and the various commands are not accessible.

    JETPACK_DEV_DEBUG: It does not matter whether it is ‘false’ or ‘true’. The result is the same.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    1 year, 3 months ago

    Hi @almendron –

    We test this using another local development tool (Local) and could not reproduce the issue. One thing we noticed there is that the wp-config.php file has the WP_ENVIRONMENT_TYPE set:

    define( 'WP_ENVIRONMENT_TYPE', 'local' );

    I’d suggest setting that and seeing if you still get the issue.

    Let us know how it goes.

    Thread Starter almendron

    (@almendron)

    1 year, 3 months ago

    I have added what you have told me and the problem is not solved.

Viewing 15 replies - 1 through 15 (of 20 total)
1 2

The topic ‘errors accessing the site administration’ is closed to new replies.