Issues connecting with DPI-SSL enabled

[BCSTech]

Our company utilizes DPI-SSL (SSL Inspection) on the perimeter firewall.  For quite some time we have had the issue occur where someone attempts to connect to a PC that it outside of our network and they are given an error message that they are unable to connect.  My workaround has been (as it occurs) to manually exclude the hostnames associated with the certificates being issued to the computer.  They all the same pattern of ".lmi-app**-**.logmein.com" (Examples:  *.lmi-app26-03.logmein.com / *.lmi-app24-02.logmein.com).  I've attempted to contact support to gain a listing of all hostnames that follow that pattern, but they say they cannot provide that info.  I'm unable to perform a double wildcard (*.*.logmein.com).  Any suggestions as to how to gain this list of hostnames?  Thanks in advance!

[GlennD]

Hi @BCSTech, 

I am looking into this for you at moment, have you tried placing the wildcard between "app" and ".logmein.com ?

[BCSTech]

Our firewall doesn't support double wildcard (*.*.logmein.com) or wildcards within the URL (connect.*.logmein.com).  I can only do a wildcard at the beginning of the URL (*.connect.logmein.com).

[GlennD]

Unfortunately, all of the information that we can share is already covered in our Allowlisting and Firewall Configuration support article. Perhaps your firewall vendor can assist?

[BCSTech]

Thanks for checking Glenn.  I've already contacted our firewall vendor.  They recommended I disable SSL inspection for any of the "*.lmi-app**-**.logmein.com" urls.  That is what I've been doing as our workaround.