Automattic
Critical error reported when it probably is not an error?
Quick summary
My playground has only IPv6 exposed. On fediverse I reported a critical error and guessed it's related to the tests trying on IPv4. https://mastodon.grml.de/@robin/114562332015629964
Both urls delivered ok when tested. My desktop seemed to use IPv6 (checked with dnslookup).
But it seems the bug is not always present. Now for this bugreport I went to the dashboards health checks and the critical errors were gone.
So I'm not sure if this is a problem in the scope of the plugin or more the system that sometimes tries to use IPv4.
If it helps, the playground is https://happyrate.de
Steps to reproduce
Log in and run the site health from dashboard (Version 5.9.2)
Site owner impact
Fewer than 20% of the total website/platform users
Severity
Minor
What other impact(s) does this issue have?
No response
If a workaround is available, please outline it here.
No response
Hmm, I just tested your site and the dev-tools seem to have no issues, but I can't follow your site on Mastodon. Do you have a firewall or security plugin in place, that might block requests?
- ActivityPub: https://browser.pub/https://happyrate.de/?author=0
- WebFinger: https://webfinger.net/lookup/?resource=acct%3Ahappyrate.de%40happyrate.de
No dedicated firewall. Just my router (AVM FRITZ!Box 5690 Pro) that passes the requests to an nginx that runs in a proxmox container. The plugins are
@Rilgamon Does this continue to be a problem? I'm not sure the plugin makes any specific IPv6 vs IPv4 decisions, I'd expect that to be handled in WordPress' Request library.
@obenland No. I think this is an edge case. Server and client not ready for ipv6 only. Thats probably completly Out of scope of the PHP engine. I think its safe to close this.