Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

webpages only open in basic form and in Browser Console there seem to be a lot of error message I do not understand

  • 2 replies
  • 1 has this problem
  • 2 views
  • Last reply by Lakselus

more options

10:46:17.834 SearchSettings: get: No settings file exists, new profile? DOMException: Could not open the file at /Users/alanpike/Library/Application Support/Firefox/Profiles/hnj6jviy.default-release/search.json.mozlz4 SearchSettings.jsm:108:18 10:46:18.484 BackgroundUpdate: _reasonsToNotScheduleUpdates: Failed to check for Maintenance Service Registry Key: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIUpdateProcessor.getServiceRegKeyExists]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: resource://gre/modules/BackgroundUpdate.jsm :: _reasonsToNotScheduleUpdates :: line 243" data: no] BackgroundUpdate.jsm:245 10:54:47.435 services.settings: main/doh-providers Signature failed InvalidSignatureError: Invalid content signature (main/doh-providers) RemoteSettingsClient.jsm:965 10:54:47.436 services.settings: main/doh-providers local data was corrupted RemoteSettingsClient.jsm:1000 10:54:47.436 services.settings: main/doh-providers Signature verified failed. Retry from scratch RemoteSettingsClient.jsm:674

10:46:17.834 SearchSettings: get: No settings file exists, new profile? DOMException: Could not open the file at /Users/alanpike/Library/Application Support/Firefox/Profiles/hnj6jviy.default-release/search.json.mozlz4 SearchSettings.jsm:108:18 10:46:18.484 BackgroundUpdate: _reasonsToNotScheduleUpdates: Failed to check for Maintenance Service Registry Key: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIUpdateProcessor.getServiceRegKeyExists]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: resource://gre/modules/BackgroundUpdate.jsm :: _reasonsToNotScheduleUpdates :: line 243" data: no] BackgroundUpdate.jsm:245 10:54:47.435 services.settings: main/doh-providers Signature failed InvalidSignatureError: Invalid content signature (main/doh-providers) RemoteSettingsClient.jsm:965 10:54:47.436 services.settings: main/doh-providers local data was corrupted RemoteSettingsClient.jsm:1000 10:54:47.436 services.settings: main/doh-providers Signature verified failed. Retry from scratch RemoteSettingsClient.jsm:674

Chosen solution

This could be a problem with High Contrast Mode on Mac.

See "New" in the release notes.

Firefox now automatically enables High Contrast Mode when "Increase Contrast" is checked on MacOS in the Accessibility settings.


Make sure you allow pages to choose their own colors.

  • Settings -> General: Fonts & Colors -> Colors: "Override the colors specified by the page with my selections above"

Try "Never" if the default "Only with High Contrast themes" isn't working.

Read this answer in context 👍 0

All Replies (2)

more options

Chosen Solution

This could be a problem with High Contrast Mode on Mac.

See "New" in the release notes.

Firefox now automatically enables High Contrast Mode when "Increase Contrast" is checked on MacOS in the Accessibility settings.


Make sure you allow pages to choose their own colors.

  • Settings -> General: Fonts & Colors -> Colors: "Override the colors specified by the page with my selections above"

Try "Never" if the default "Only with High Contrast themes" isn't working.

more options

Hello, Thanks so much for clear advice. Switching to 'never' has done the trick! I have wasted a lot of time to no avail so you have saved me a lot more. Alan