Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Website block message customization not working

Hi!

We are migrating from UTM to XG using the migration tool. We generated the config and imported it into our spare SG. Until now, all good.

We were polishing the install, creating rules, customizations and so on, and we found a weird problem. We customised the web proxy error messages in "Web -> User notifications" (see picture below) and the preview shows what we want, but when we try to access a blocked website, the message it displays is completely different, and it's shown twice!

Also, it's trying to show a picture at the top and bottom, which are the "Custom images" I tried setting, but removed in the end. Somehow it still thinks it should display them although the box is clearly unchecked.

Note that I had to go to "Web -> Categories" and in every single category go to Advanced Settings and UNCHECK the "Override default notification page". It was checked by default in every category with a message that was displaying correctly, only once, but was really crappy without HTML or any colours.

Anyone can help us fix this?
Thanks!

Config:

Expected (preview):

Got:



This thread was automatically locked due to age.
Parents
  • EDIT: Be sure to take a backup before making any changes!

    I had this same issue... the case had to be escalated to Sophos' Global Escalations team. The technician ran the following commands from CLI Advanced Shell (SSH with Putty, then Option 5 (Device Management), then Option 3 (Advanced Shell):

    XG310_WP02_SFOS 17.5.9 MR-9# psql -U nobody corporate -c "delete from tblcustomizeddeniedmsg where categoryname not in ('Activex','Cookies','Applets','HTTPUpload');"
    DELETE 0

    XG310_WP02_SFOS 17.5.9 MR-9# cat /conf/httpclient/deniedmessage/deniedmessage.html

    XG310_WP02_SFOS 17.5.9 MR-9# rm -rf /conf/httpclient/deniedmessage/deniedmessage.html

    XG310_WP02_SFOS 17.5.9 MR-9# ln -s /cfs/deniedmessage.html /conf/httpclient/deniedmessage/deniedmessage.html

    The Web proxy service must then be restarted, or the XG appliance itself if restarting just the service fails...

    It looks like the technician
    -cleared out the customized "deny" messages from the psql database
    -checked the current corrupt "deny" message
    -removed the current corrupt "deny" message
    -restored from a clean backup copy of the default "deny" message

    Hope this helps - it worked for us...

Reply
  • EDIT: Be sure to take a backup before making any changes!

    I had this same issue... the case had to be escalated to Sophos' Global Escalations team. The technician ran the following commands from CLI Advanced Shell (SSH with Putty, then Option 5 (Device Management), then Option 3 (Advanced Shell):

    XG310_WP02_SFOS 17.5.9 MR-9# psql -U nobody corporate -c "delete from tblcustomizeddeniedmsg where categoryname not in ('Activex','Cookies','Applets','HTTPUpload');"
    DELETE 0

    XG310_WP02_SFOS 17.5.9 MR-9# cat /conf/httpclient/deniedmessage/deniedmessage.html

    XG310_WP02_SFOS 17.5.9 MR-9# rm -rf /conf/httpclient/deniedmessage/deniedmessage.html

    XG310_WP02_SFOS 17.5.9 MR-9# ln -s /cfs/deniedmessage.html /conf/httpclient/deniedmessage/deniedmessage.html

    The Web proxy service must then be restarted, or the XG appliance itself if restarting just the service fails...

    It looks like the technician
    -cleared out the customized "deny" messages from the psql database
    -checked the current corrupt "deny" message
    -removed the current corrupt "deny" message
    -restored from a clean backup copy of the default "deny" message

    Hope this helps - it worked for us...

Children
  • Hi, i would recommend not to post such postgres database commands in the community.

    You do not know, who will try to use such commands and afterwards, if you do a mistake, it could easily break your system.

    Those commands on the database / filesystem of the system should be only be done by the Sophos Support.

    __________________________________________________________________________________________________________________

  • Please note that this was a bug in an early version of the UTM-XG migration tool that was fixed months ago.

    If anyone is doing a migration and is running into this problem please do not run these steps.  Instead contact your partner to make sure that you have the most recent migration tool and run the migration again.  There are other fixes and improvements in the migration tools that you may want.