Error initializing dialog. Check that your gate endpoint is accessible. Further information on troubleshooting this error is available here.

[Ankush010203]

Issue Summary: Error initializing dialog. Check that your gate endpoint is accessible. Further information on troubleshooting this error is available here.

Cloud Provider(s): Azure

Environment: testing

Feature Area: Spinnaker

Description: we have install spinnaker on the ubuntu vm but we are getting mentioned error

Steps to Reproduce:

Additional Details:

---

Please delete the instructions below this line prior to submitting

Instructions:

• An issue is not a place to ask questions. Please use Slack or Stack Overflow.
• Before you open an issue, please check if a similar issue already exists or has been closed before.
• Make sure you have read through the Spinnaker FAQ and Halyard FAQ to provide as much information as possible.

Descriptions:

• Issue Summary: A brief description of what you're seeing.
• Cloud Provider: AWS, GCP, Kubernetes, Azure, Cloud Foundry, etc.
• Environment: As much information about your Spinnaker environment and configuration that might be relevant to the issue. For example: "I am running Spinnaker using the Amazon images to deploy into AWS and GCP."
• Feature Area: Notifications, Pipelines, UI, Jenkins, etc.
• Description: The behavior you expect to see, and the actual behavior.
• Steps to reproduce: Ideally, an isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem). If not possible, as much information as possible to see this behavior.
• Additional Details: Additional information such as screenshots and exception logs.

[Ankush010203]

We are using http://:9000 url what should be the necessary steps

[Ankush010203]

any reply on this

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale

[spinnakerbot]

This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

[spinnakerbot]

This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.