UTM 9 USER PORTAL IS ACCESSIBLE BUT RENDERS BLANK PAGE.

UTM 9 USER PORTAL IS ACCESSIBLE BUT RENDERS BLANK PAGE.

FIRMWARE VERSION.  9.711-5. (FREE VERSION FOR HOME USE)

I've configured the user portal through the UTM 9 interface and am able to reach the portal through my browser (Safari 15.5).  As the title of the tab or main

window is titled "USER PORTAL".  Using the developer tools included with Safari, none of the .js files are executing.  The messages I receive on the Java Script console are:

[Error] Refused to execute UTM:443/.../jape_20_util.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/jape/jape_30_dom.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/jape/jape_40_widget.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/jape/jape_50_form.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/jape/jape_60_grid.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/jape/jape_99_common.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_blacklist.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_change_password.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_clientless_vpn.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_hotspot.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_pop3.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_ras.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM0:443/eup/eup_50_settings_pop.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_smtp.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_smtp_log.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_50_soa.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http:/UTM:443/eup/eup_50_whitelist.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://UTM:443/eup/eup_60_init.js as script because "X-Content-Type-Options: nosniff" was given and its Content-Type is not a script MIME type.

ReferenceError: Can't find variable: Cfg

"UTM" replaced the address of my utm

I have also called up the page with Chrome for MAC and Firefox for MAC as will as on my iPad running OS 15.5, using Safari as the browser.  I also called up the page using Microsoft EDGE Version 84.0.522.52 (Official build) (64-bit) and still the UTM rendered a blank page.

I have search for some related MIME settings on the browsers as will as on the UTM but not found anything helpful.

I haven't used to portal for a while.  I know when I did, the portal came up correctly so I don't know in which version it stopped rendering the pages.

At firt blush I believe that this is something that Sophos would need to fix on a subsequent update.  It would be great if that were

not the case, and it can be fixed by the end user.

CONSOLE OUTPUT USING SAFARI (15.5)