| This thread was migrated from an old forum. It may contain information that are no longer valid. For further assistance, please post a new question or open a support ticket from the Customer Support portal. |
Hi Team,
I am unable to login to Kony enterprise cloud account through Kony vizualizer 8.2. Getting below error. Please assist.
- HTTP GET on https://manage.kony.com/console/health_check failed . Details - Connect to manage.kony.com:443 [manage.kony.com/52.22.148.84, manage.kony.com/18.205.141.182] failed: Connection timed out: connect
- No Kony Fabric server running at the URL mentioned.
Thanks,
Hi ,
Based on the issue description which you shared we have understand that the Health Check got Failed.
Please share us the cloud account details, to check the issue.
Also, please share your MF URL
Thank you,
Hi @Avmiw Rutledge ,
In addition to what S***** has requested, can you also confirm whether you or your organization have purchased on-premises licensing vs. Kony Clouds? If you have only purchased on-premises licensing, you would be expected to connect to a Fabric installation that you or or your organization is managing and it would need to be accessible from the machine on which you have installed Visualizer. Note that this could also require additional configuration such as proxy, firewall, and/or VPN if the Fabric URL is not accessible over the public internet by default.
Thanks,
`
Hi Team,
We have Kony enterprise cloud license and its working fine when logging in with Kony Viz installed on other systems in same network.
Also, We are getting this error on clicking login button before entering cloud account username & password.
Thanks,
Hi @Avmiw Rutledge ,
If your organization has purchased licensing, can you please open a support case (via https://basecamp.kony.com/s/caselistview) so we can discuss and troubleshoot with you in more detail?
In the support case, can you please make sure to provide the following:
- the version of Visualizer Enterprise that you are using
- a screenshot showing the error
- the email address associated with your user account (we see that there may be several email addresses that you have registered and belonging to a different set of Cloud accounts)
- the Cloud account ID for the Cloud account you are using when you encounter this issue (you can refer to the attachment for locating the Cloud account ID)
Thanks,