[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

Hi Ronald, That is great. Creating the issue will allow you to get in touch with the right people in the right place. I see someone has already replied to your request. For further reference, Google Groups are best suited for general product discussion, product information or other general que

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

Thanks, opened an issue (hopefully in the correct section): 153412854 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegro

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

Judging from the error, there seems to be an issue with the debugger agents registering with the Controller to identify the application being debugged, the Debuggee. From the screenshots or error itself, it’s difficult to understand why this must be happening. It could be an issue with the Java1

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

Hi Thomas, here are some screens. The debugger is trying to refer to our internal git repo. The *source-context.json* (where does this come from?) also refers to our git. There ain't much more to see there, no logpoints or snapshots etc. Best, Ronald -- You received this message because you a

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

Hello Ronald, Do you have any deployed apps running? Cloud debugger (formerly known as stackdriver debugger) is indeed enabled by default. In cloud debugger , is a resource selected? Refer to the documentation to see what I mean. You can

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

When trying to disable the Cloud Debugger API I receive a warning that " *cloudapis.googleapis.com*" will be disabled as well. That doesn't sound right. Is the Cloud Debugger enabled by default / required for the GAE? If so, what exactly does it do and why does it throw 503s from time to time? :|

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

Thanks for your quick response. It's not that we get a 503 for some requests we fire but that the whole stack trace does not belong to us. We do not use the Cloud Debugger anywhere! I see that the Cloud Debugger API is active and in the metrics section I see google.devtools.clouddebugger.v2.Con

[google-appengine] Re: IOException: Server returned HTTP response code: 503 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register

This doesn't sounds like an issue connected with Cloud Debugger . Because, A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request. A discussion about the similar topic (*Server