unable to browse default instance as https url

[Vikas Putcha]

Hello All,

I'm new to GCP and got struck with a strange issue with my nodejs application.

https://vikas-tradeassist.appspot.com <-- not accessible

http://vikas-tradeassist.appspot.com <-- is active.

same code base is working fine if i deploy it as separate service.

Just before i landed in this state, my application had some package dependency issue. before that even https was working fine. 

I resolved error, deployed multiple time, but no luck.

can anyone point me in right direction, how i can resolve this issue, without deleting entire project.

Thanks,

-VIkas.

[Julie (cloud platform support)]

Sounds like there an issue with the SSL configurations with your custom domain so please verify a managed certificate has been provisioned if you are using the one provided by Google (which happens automatically after setting up your custom domain and update the DNS records) or if you are using wildcard mapping or you have your own SSL certificate please check your own certificate configuration. 

If the above looks correct please specify the package dependency issue before the HTTPS issue began as it is currently unclear if it is related to this issue. 

[Vikas Putcha]

Though not aware of the root cause, the issue is resolved now, i'm able to access https url too.

Looks like there is some wait time, if there is build issue, irrespective of its resolution. it would be nice if i could know how i could flush and restore the traffic by configuration.

Thanks,

-Vikas.

[Julie (cloud platform support)]

It unclear what you mean by build issue so please specify when the wait time occurs and how long and if any other services are involved (ex. Cloud Build, Task queues etc). Please note that that when instances and services are spinning up there will be a wait time and that is expected behavior.  Its also unclear if you are requesting instructions on restarting your app engine services but that is usually not recommended due to downtime. Please provide more details on your use case as well as your app.yaml if the issue is with service/instance spin up (after removing all sensitive and personal information such as emails addresses, project id, passwords, keys etc) as your exact request in difficult to address without the context.