Monit frame is blank on ISPConfig 3.1.14p2

Discussion in 'Installation/Configuration' started by concept21, Aug 7, 2019.

  1. concept21

    concept21 Member

    After I have updated my system to ISPConfig 3.1.14p2, the ISPConfig control panel Monit frame becomes blank. If I run the Monit frame in a new tab, it do display correctly.
    It happens to Firefox, Opera and Google Chrome. Under Google Chrome, it displays this message:
    Requests to the server have been blocked by an extension.

    However, Monit was still working inside Firefox just before the ISPConfig update.
    How do I correct it?
    My OS is Ubuntu 18.04.3. :(
     
  2. Jesse Norell

    Jesse Norell Well-Known Member

    Is your ISPConfig running on https and monit url is plain http? Or what are their url's (sans all user/password credentials)?

    If ISPConfig is on HTTPS, you will get an HSTS header sent to your browser and it will no longer access the same origin on HTTP, but instead automatically upgrade those requests to HTTPS. If that is your case, probably putting monit on a different origin (eg. access via a subdomain name), or simply changing it to use HTTPS, should fix the issue.

    There is a maybe similar issue that has been reported for recent chrome versions, where it blocks accessing monit due to the username/password in the url. Maybe it only does that when it's loaded in an iframe, I'm not certain of the details. But a solution there would be to reverse proxy access to monit though a url on ISPConfig (eg. /monit/ reverse proxy's to the actual monit server). Possibly you could also switch monit to http basic authentication, so it prompts for a username/password, then have your browser remember the username/password.
     
    Last edited: Aug 7, 2019
  3. concept21

    concept21 Member

    Of course Monit url is https.
    I do not use password for Monit. I limit its access by IP only. :(
     

Share This Page