Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

Firefox showing 404 for some local scripts and styles

  • 3 replies
  • 1 has this problem
  • 1 view
  • Last reply by FredMcD

more options

Hi,

I am seeing 404s with some local scripts and styles. The website uses a custom CA and self signed certs which have been added to Firefox.

The scripts and styles are definitely there and are being loaded correctly in Chrome.

Browser: Firefox Quantum 60.0 (64-bit) OS: macOS 10.13.4

Hi, I am seeing 404s with some local scripts and styles. The website uses a custom CA and self signed certs which have been added to Firefox. The scripts and styles are definitely there and are being loaded correctly in Chrome. Browser: Firefox Quantum 60.0 (64-bit) OS: macOS 10.13.4

Chosen solution

Sorry, turns out it was a server issue. Chrome had it cached so I wasn't seeing the same results.

Read this answer in context 👍 0

All Replies (3)

more options

Many site issues can be caused by corrupt cookies or cache.

  • Clear the Cache and
  • Remove Cookies

Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.

If there is still a problem, Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Did this help?

While you are in safe mode;

Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches.

How to disable Hardware Acceleration {web link}

more options

Chosen Solution

Sorry, turns out it was a server issue. Chrome had it cached so I wasn't seeing the same results.

more options

As long as it's fixed. Please flag your last post as Solved Problem so others will know.