I’m sorry all I know I’m annoying but why do I get this message so often:
Secure Connection Failed
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
What can you do about this?
The issue is most likely with the website, and there is nothing you can do to fix it. You can, however, inform the website administrator about the problem.
Error code: PR_END_OF_FILE_ERROR
I have firefox 157.0 (64 bits)
You don’t tell which URL you are trying to access, I’ll assume that’s MusicBrainz Website (https://musicbrainz.org).
When it happens, do you also lose access to https://metabrainz.org ?
Next time it happens, communicate your IP address to support@metabrainz.org so we can check what’s happening.
Yes i will. I wll make screenshots again.
It also happens on other browers so i dont think its a firefox thing. And yes only on MB
Thy for you reply. Have a nice weekend
Came here via https://github.com/majkinetor/musicbrainz-userscripts/issues/692
I don’t know of any userscripts for MusicBrainz that do HEAD to MusicBrainz so I used AI tool help me quickly search through all my starred MB related repos and as expected there are none:
Across all 387 userscripts in all 40 repositories (including chaban-mb/userscripts and all starred repos):
HEAD requests to musicbrainz.org?No. There are exactly zero (0) scripts that send HEAD requests to musicbrainz.org (whether to /recording/..., /release/..., or any other MusicBrainz URL).
HEAD requests anywhere at all?Across the entire collection of 387 scripts, only 4 scripts contain code making HTTP HEAD requests. All 4 strictly target external, third-party URLs:
| Repository | Script | Target URL / Purpose | Code Excerpt |
|---|---|---|---|
majkinetor/musicbrainz-userscripts |
String Theory |
External relationship links (e.g., Bandcamp, Discogs, official sites) in #external-links-editor via the manual “Check links” button. |
GMX({ method: 'HEAD', url, ... }) |
majkinetor/musicbrainz-userscripts |
Apollo Editor |
The same external link dead-checker in the release editor external links tab. | GMX({ method: 'HEAD', url, ... }) |
ROpdebee/mb-userscripts |
MB: Supercharged Cover Art Edits |
Cover Art Archive image thumbnails on archive.org (testing 1200px / 500px availability). |
fetch(url, {method: 'HEAD'}) |
vzell/mb-userscripts |
DisplayShortcutForRelationshipWithCustomFavicons |
External relationship domains checking for https://${domain}/favicon.ico. |
GM_xmlhttpRequest({ method: 'HEAD', url: faviconUrl, ... }) |
None of these 4 scripts send HEAD requests to musicbrainz.org.
See also reply by @majkinetor: Inquiry about user blocking due to 100 req/s · Issue #692 · majkinetor/musicbrainz-userscripts · GitHub
Regardless, @Tiske_Tisja
Without a list of all userscripts and browser extensions you are using it’s hard to find the culprit.
Can you open about:support in Firefox and paste the raw data here (in code block) as well as the list of enabled userscripts in your userscript manager?
And as @zas asked a log of network requests while on the page might also give clues.
This can only be resolved by watching network on Tiske’s computer for HEAD requests. My bot suggested that on issue, but the problem might be that it could be intermitient and opening dev. tools after the fact wont show it.
One solution would be to use local proxy that records all network actions and revise it after it happens the first time.
Tiske (or somebody knowledgable in vacinity) could setup this. It is not that complex, but requires somebody with IT know how. With this setup, all it would take is to send us a log file here first next time it happens.
Hi Guys,
Thank you all for yor help. I guess I’m going to have to live with this then. I dont understand what to do nor do I have someone who can help me with this.
Tiske, you can do process of elimination:
It will take some time (you didn’t tell how often it happens), but you can resolve it that way. Alternative is to install remote control tool such as Team Viewer and let some of us do it, if you are conformtable with it.
Also, use AI. For example, try this: ChatGPT - Block HEAD Requests. Note that I didn’t test it but I trust current models for trivial stuff like this. This will certainly make some other features not work but it is diagnostic tool and you might even find downsides acceptable. If it works, we can revise it later.
That is the point, sometimes it does not happen for days and then suddely a few times a day.
I’m gonna try it with another browser. Thank all for your help
This sounds promissing Tiske, and you can do it, we know it:
Use Firefox’s built-in HTTP logging through about:logging. Mozilla specifically provides it for capturing intermittent network problems and writing logs to disk.
Firefox Source Docs documentation
about:logging in Firefox.Sends us logs after it appears (as zip file, it will be huge depending on how much time passes after you started it until network breaks). After that, disable this option or file will grow indefintelly.
You can see on my profile. They are all there. Im not at home atm so i cant make a list for you
