Graphs do not display on pool monitoring web page on Firefox

I am using the latest (160) version of Firefox on Ubuntu 26.04. Pool monitoring pages (for example: pool.ntp.org: Statistics for 130.61.205.131 ) do not display the History graphs at all. Instead we see the message:

Please upgrade to a modern browser that supports Web Components to see the charts.

Recommended browsers: Chrome, Firefox, Safari, or Edge

I tested with other Ubuntu desktops and Android devices too. The problem is the same. Disabling Firefox addons has no effect too.

On other browsers, like Chrome, Edge, or Opera the graphs are displayed as expected.

The following errors in Firefox Web Developer Tools may help in investigating the problem:

Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src ‘self’ https://www.mapper.ntppool.org/mapper.js https://send.webform.dev/js/embed.js”. Consider using a hash (‘sha256-ieoeWczDHkReVBsRBqaal5AFMlBtNjMzgwKvLqi/tSU=’) or a nonce. sandbox eval code:17:34

Loading module from “https://www.ntppool.org/static/build/base-chart.vB9SrD8PD.js” was blocked because of a disallowed MIME type (“text/html”). 130.61.205.131

Content-Security-Policy: The page’s settings blocked the loading of a resource (default-src) at https://www.mapper.ntppool.org/mapper.js because it violates the following directive: “default-src ‘none’”

Hi @kadifeli Do you know if the https://www.ntppool.org/static/build/base-chart.vB9SrD8PD.js request was a 404 not found response?

Was this today or was it ~2 days ago? (If two days ago I see in the logs what happened, but if it happened shortly before you posted it’s less clear).

One the page pool.ntp.org: NTP Servers in All Pool Servers, pool.ntp.org it is still visible:

No. It was not a “404 error” as my first post indicates. It was “because of a disallowed MIME type”. I saw this error just at the time of my first posting.

However, the problem seems to be solved today. I think you fixed the MIME type or did something similar to solve the problem in the past 12 hours now.

I understood. The only way I could figure out a text/html mime type would have been returned is on a 404.

The only scenario (now fixed!) where that could happen is during a brief period (~10-60 seconds) during an upgrade if you are particularly unlucky. That did seem to happen to someone 3-4 days ago, so that’s why I was wondering about the time line.

If it happens again the HTTP headers from the response will be very helpful.