Hi Richard, - from which ACS versions did you upgrade? - this is DNS resolution being problematic, so please verify it works (from your laptop) (could also confirm it's there in dnsmasq, but actually testing the resolution is better) -- please note that you should have ALL of your public IPs added to the DNS in that form a-b-c-d.mydomain.name
Might be that your CPVM got a new public IP for which you don't have DNS resolution in place. Also verify (existing) settings that those are still there the way you like it: - consoleproxy.url.domain - secstorage.ssl.cert.domain (related, not required) - consoleproxy.sslEnabled=true - check your "keystore" table inside "cloud" DB - there you should see both the private key as well as all certs in the chain (server cert, and any intermediate/Root CA's certs). Let us know how it goes. Andrija On Thu, 25 Jul 2019 at 14:31, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Hi Richard, > > By default, CloudStack points the remote console to int-ern-al- > ip.your.domain. As a quick fix, you need to point this domain to the > external IP under which the console proxy is reachable. > > I think it's also possible to customise the domain name, so you don't > have to add a new DNS record whenever the console proxy is redeployed. > > Regards, > Gregor > > On Wed, 2019-07-24 at 23:57 +0000, Richard Persaud wrote: > > Hi, > > > > After upgrading to 4.11.3, I am not able to connect to the console of > > my VMs from a web browser. I get a DNS error – can’t resolve a-b-c- > > d.domain.name > > I can SSH directly into the VM. > > This did work prior. > > Any ideas of where to start troubleshooting? > > I am using dnsmasq > > Regards, > > > > Richard Persaud > > > -- Andrija Panić
