Can you check,
1. if the Console Proxy can ping the gateway of it's public interface and has internet access.
2. if you are able to reach the Console Proxy's public interface (over https) from the location you are trying to view the console (where you have the management server UI browser session open).

Having looked at the system VMs I moved them to another host and all started working again, moving them back and they are still working.

James

Hi Team,

I'm facing the same issue. After Moving the system vs to other Cluster also same issue.

Please suggest

1. if the Console Proxy can ping the gateway of it's public interface and has internet access.

yes I can

2. if you are able to reach the Console Proxy's public interface (over https) from the location you are trying to view the console (where you have the management server UI browser session open).

yes able to reach, but page showing 404 Not found No context found for request

Have you tried destroying and recreating the console proxy?

yes I did.Still no luck

hmm, interesting.

Can you confirm you are able to access the console proxy's public interface over https from the machine you are trying to open the console.

You can test this by doing a telnet <console_proxy_ip_address> 443

If this is working and you are still the problem persists then I'd need to take a look at the console proxy logs.

I'm able to connect https://CPVMIP.

Which log you are referring to cloud.out from CPVM?

Primarily I am looking for cloud.log located under /usr/local/cloud/systemvm/. It would also help if you can share cloud.log from under /var/log/.

Hi Somesh,

Due to security reasons I can't send logs now. I checked both the logs cloud.log and cloud.out . Couldn't see any error.

Is this because of DNS Service issue?

Regards,
Anoop Mohan

What do you mean when you say DNS service issue? Can you explain?

Just a thought, DNS resolving issue.

Is this still an issue?

If so, can you verify if you can access the internet from the console proxy VM over the public interface.

Rather a better thing to do is to run the diagnostic script and see if it reports any errors. Refer documentation (Install Guide, Troubleshooting sec) for details on how to run the script.

Sumesh,

When I run diagnostic scripts the one failing is DNS couldn't resolve download.cloud.com rest everything is fine. This will fail because, this is under private isolated network without internet

Both the SSVM and CPVM need to have internet connection else they won't function correctly.