We're running an IP Office R10 (500v2) with a separate virtual linux based app server (10.1.1.1). I was following the word doc linked in this article ( trying to figure out why Avaya Communicator is failing to connect. I changed the Host Name under the Network settings from within the 7071 page and rebooted. After the reboot I can't get to any web interface for the app server. Manager will allow me to connect but I don't see anything that jumps out at me that's wrong. I rebooted the box again and watched it boot up, the only thing that failed was httpd. From the Linux command line I tried starting httpd but it failed with an error that my certificate (a wildcard cert) didn't exist or was empty. I checked the directory it pointed me to and the certificate was not in there so I added the cert using winscp. Httpd started but no luck on the web interfaces so I rebooted again. This time it said WebManager failed to start but when the box came up I did a quick "service WebManager status" and it was running. 10.1.1.1/index.html comes up fine but anything else from 10.1.1.1 gives me the same error below. I've tried using the IP and the DNS name we setup
Error I'm getting in Chrome
10.1.1.1 normally uses encryption to protect your information. When Google Chrome tried to connect to 10.1.1.1 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 10.1.1.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 10.1.1.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.
Error I'm getting in Chrome
10.1.1.1 normally uses encryption to protect your information. When Google Chrome tried to connect to 10.1.1.1 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 10.1.1.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 10.1.1.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.
