Cannot access App Server Platform View

[davea2]

Hi

having a problem accessing the Platform View on a new install app server 9.1.12
I can get on

https://192.168.42.1:7070,

but if I try to go to

https://192.168.42.1:7071

i get (from Chrome)

192.168.42.1 normally uses encryption to protect your information. When Google Chrome tried to connect to 192.168.42.1 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 192.168.42.1, 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 192.168.42.1 right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.

I cannot get on with IE either.No option in either browser to override.

I have tried regenerating the certificate and rebooting the server, but it's still the same.

Any ideas? I am stumped in the port 7070 is OK!

Cheers

 

[critchey]

I had that issue happen once when I was playing around with the certificates and mucked something up. You can try using Mozilla since it uses a different certificate store then IE and Chrome use. If that works you will have to try delete some certificates and see if you can get it working on IE and Chrome.

The truth is just an excuse for lack of imagination.

 

[sizbut]

In Chrome, Ctrl+Shift+I and select the Security tab. It will tell you a bit more about what Chrome is objecting to. It will also let you view the certificate on the server so you can see if its a domain name or IP address problem or something up the certificate chain.

...or as you said you'd only just installed it, reinstall, test without your cert and then risk it again.

Stuck in a never ending cycle of file copying.

 

[davea2]

It seemed to think the Cert was corrupt or tampered with

I deleted them all, and again generated a new one and this time it seems OK. Odd.

Thanks for the pointers, glad a re-install was not necessary!