Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 2517 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM 9 USER PORTAL IS ACCESSIBLE BUT RENDERS BLANK PAGE.

Sophos User3188

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)



This thread was automatically locked due to age.
Parents
  • 0

    It appears you are blocking JavaScript in your browser.  If you are running some type of adblock that does this, then disable it or allow the exception for your portal, or use another browser.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    Thanks for the suggestion but Safari is not blocking Javascript and while I have Bit Defender extensions, they are not activated.

    I have tried on multiple browsers, Safari for Mac, Chrome for Mac, Firefox for Mac, and finally Edge for Windows 10.  Each browser fails to render anything but a blank page even though the UTM does seem to serve up the initial portal page.

    The scripts that fail to load seem to be caused by the server in response to a bad response (400) from the browser.

    The balance of the scripts have been refused (I would think this is at the server end), as usually with Server/Client models

    it's the server that decides whether are not to serve the elements for the page.  Also there is a reason given on these scripts.

    "X-Content-Type-Options: nosniff" stating that it's Content-Type is not a script MIME type.  Again I tend to think that this coming from 

    the server due to an error in the HTML scripting in the page being served.  Also the server is returning a ReferenceError:Can't find variable Cfg.

    In the header of the page there is indeed an "unload" command wot Cfg.app as the target from some configuration variables.

    Thanks,  if you think of something else or see that I am missing something let me know.

    Here are screen prints re your questions..

Reply
  • 0 in reply to Amodin

    Thanks for the suggestion but Safari is not blocking Javascript and while I have Bit Defender extensions, they are not activated.

    I have tried on multiple browsers, Safari for Mac, Chrome for Mac, Firefox for Mac, and finally Edge for Windows 10.  Each browser fails to render anything but a blank page even though the UTM does seem to serve up the initial portal page.

    The scripts that fail to load seem to be caused by the server in response to a bad response (400) from the browser.

    The balance of the scripts have been refused (I would think this is at the server end), as usually with Server/Client models

    it's the server that decides whether are not to serve the elements for the page.  Also there is a reason given on these scripts.

    "X-Content-Type-Options: nosniff" stating that it's Content-Type is not a script MIME type.  Again I tend to think that this coming from 

    the server due to an error in the HTML scripting in the page being served.  Also the server is returning a ReferenceError:Can't find variable Cfg.

    In the header of the page there is indeed an "unload" command wot Cfg.app as the target from some configuration variables.

    Thanks,  if you think of something else or see that I am missing something let me know.

    Here are screen prints re your questions..

Children
  • +1 in reply to Sophos User3188

    Something I just caught here:

    In your screenshot you are using http:// with :443 

    I tried this on my User Portal and got a blank white page and nothing loaded on the page.  Those don't work.  Try https:// to start just for kicks.

    Once I just used my domain name with https:// it worked just fine.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • +1 in reply to Amodin

    That certainly worked.  Https:/[domain name of utm), brought up the user portal.  Thanks for the help.

Unfiltered HTML