Hi @taxick,
Thank you for the detailed report and screenshot.
The notice on the hCaptcha General page contains browser console messages collected while the sample hCaptcha widget is loading. This is intentional: JavaScript errors produced by another plugin or theme may also interrupt hCaptcha initialization or prevent it from working correctly.
In this case, all four messages shown in the notice are produced by Webpushr. They indicate that:
- registration of the primary Webpushr service worker failed;
- Webpushr attempted to use its alternative service worker;
- service worker registration ultimately failed;
- the browser could not access the Webpushr service worker URL.
We checked the URL from your report. At the moment it responds with 200 OK, has the correct application/javascript content type, and includes Service-Worker-Allowed: /. Therefore, the file is present and its basic server configuration appears correct.
However, during a browser test the request was rejected with ERR_BLOCKED_BY_CLIENT. Since your screenshot was taken in Brave, the most likely causes are Brave Shields, an ad/privacy blocker, or another browser security extension. Opening the URL manually does not fully rule this out, because browsers and extensions may treat a normal page navigation differently from a service worker request.
Please try the following:
- Temporarily disable Brave Shields and any ad-blocking/privacy extensions for this site, then reload the hCaptcha settings page.
- Test the same page in a clean Chrome/Chromium profile.
- In Developer Tools, check the Network panel for
webpushr-sw.js.php and the Application → Service Workers panel to see the exact blocked reason and whether Webpushr’s alternative worker was registered.
If the error remains after browser-side blocking has been excluded, we recommend contacting Webpushr support and checking whether a security plugin, firewall, or CDN rule is interfering with service worker registration.
We have also identified a display issue in hCaptcha: the four separate console messages are rendered on one line. We will correct the formatting so each message displays separately.
Hi @kaggdesign
You where right! It was Breve that block “webpushr-sw.js.php” and make the error.
I did try firefox are there was no error.
Sorry for the post. – All works now.
EDIT: EDGE make this info : Console log: Web Push Notifications powered by Webpushr
/ Thomas
Hi @taxick,
Thank you for confirming the cause, and no need to apologize.
The message shown in Edge:
Console log: Web Push Notifications powered by Webpushr
is an informational message produced by Webpushr itself. You can also see the original message in the browser’s Developer Tools console. It is not an error and does not indicate a problem with either Webpushr or hCaptcha.
The hCaptcha General settings page intentionally collects and displays all browser console messages generated while the sample hCaptcha widget is loading. This is important for diagnostics because JavaScript messages and errors from other plugins or themes may explain why hCaptcha initialization or verification is not working correctly.
Therefore, seeing this informational Webpushr message in Edge is expected and it can safely be ignored.