SOTI Pulse Logo

Error when accessing the web console

Solved Locked
RT
Raymond Turrrell
Bournville Village Trust

Hi all

I see the following error when accessing the web console lately...

mobile.abc.co.uk normally uses encryption to protect your information. When Google Chrome tried to connect to 350mobile.bvt.org.uk this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be mobile.abc.org.uk, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.

You cannot visit mobile.abc.co.uk right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.

We do have a wildcard certificate for our domain but I'm a little nervous about applying it and what impact that would have on our mobile devices. Is there a correct procedure for this?

certificate web-console hsts
6 years ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
6 years ago

Do you have similar problem if you use other browser to access your web-console?

Regarding the error message you mentioned, you might need to find IT with network security expertise to check further if there is any security problem in your corporate network infrastructure.  A search on the web seems to hit some recent reports on similar error messages from Chrome browser, but I am not sure if it is false alarm or related to any bug in recent Chrome release or not.

If you are using on-premises MobiControl server, and the SSL certificate (wildcard or not doesn't matter much) is a strong enough certificate from a reputable CA vendor, then it is, in general, advisable to have such SSL certificate installed properly and bind to your Web-Console and Deployment-Server extension services for better network security.  

Solution
RT
Raymond Turrrell
6 years ago

Thanks Raymond, it is internal. I'm going to try and use our certificate and hope it doesn't cause issue with deployment. 

Similar Discussions