Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 6 years ago.
Improve this question
Tonight we started getting curl errors with Google App Engine involved in resolving hostnames that are many including google.
Error: "Couldn't resolve host 'maps.google.com'" - Code: 6
Yes, Billing is enabled, and this has been working for months until just now.
Thought I would post to see if anyone knew anything.
This issue persists both when having the cURL extension (which uses Sockets service) enabled, as well as cURL lite (which uses URL Fetch service) enabled.
Google App Engine PHP5
Yes, Google fixed it even though they never admit but it works now.
It appears to me that Google has fixed this issue. After experiencing the same issue for the last 20+ hours, now all is working fine.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 days ago.
Improve this question
This is the message I get when I try to go into the site. I hosted a clone Netflix project website with firebase and it was working fine for the past week.
For the past few hours the website is not showing up and I'm sure that I haven't deployed any new versions ! However I tried deploying it again and its still not working . Anyone knows how to fix this or what caused this? Thanks !
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 1 year ago.
Improve this question
My react app is failing to load in the most recent version of Microsoft Edge (version 95), but it only happens on Windows systems. It prints an error in the console "Uncaught RangeError: Maximum call stack size exceeded" but no other errors are returned. This is a weird one, because it only happens on Windows devices (Windows 10 is what i tested in) and only in this specific version of Microsoft Edge. All other versions of Edge and all other browsers work fine, and Microsoft Edge 95 used on a Mac works fine. Additionally, this is not replicable with tools like browserstack for some reason, only on actual laptops.
Any help would be appreciated.
Sorry, it looks like this was a dependency issue on our end. A dependency we were using in our web app needed to be updated. Thanks for looking into this, Yu Zhou.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 4 years ago.
Improve this question
Two days ago everything was fine. Today, I get a 401 error when trying to update a version on one staging instance. It still works fine on our other staging instance and on our prod instance.
We are on the latest appengine sdk. Anyone know why we are getting the following error on only one instance?
WARNING: Error posting to URL: https://appengine.google.com/api/appversion/deploy?module=default&app_id=xxxxxxxxxxx2&version=213&
401 Unauthorized
Your version of the App Engine SDK is out-of-date. Please update your SDK at https://cloud.google.com/appengine/docs/standard/java/download#appengine_sdk and your Maven plugin, if necessary, according to the instructions at https://cloud.google.com/appengine/docs/standard/java/tools/maven
This is try #0
95% Rolling back the update.
Actually, I came across the answer. The ~/.appcfg_oauth2_token_java had the wrong credentials. I deleted that and tried again. It took me through the OAUTH flow and then it worked.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 8 years ago.
Improve this question
I am constantly getting today:
"The request's content type is not accepted on this URL."
for anything I try and anywhere I try it. Logging in to new cloud console and uploading file gives this error, creating folder gives that error, uploading from our software gives this error.
Is Google Cloud Storage down? Any help is appreciated.
PS.
This is not multi-part error problem since I am trying to upload also directly from google cloud console!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I'm experiencing a strange problem with file uploads to Blobstore (runtime: Java, appid: teamwork-client-services). POSTing a request with file data from client's browser to Blobstore service URL (retrieved via call to createUploadUrl()) causes a status 500 response with no explanation. Request gets never redirected to my server-side upload handler.
Just checked two other applications (one of them uses Python runtime). Got the same behavior. GAE System Status console shows 100% availability, but I'm not sure if Blobstore status is monitored there.
Could anyone help me figure out what's going on?
Thanks in advance.
Just letting you guys know - seems like the Google AppEngine team agnoledged the problem and solved it just now:
https://groups.google.com/forum/#!topic/google-appengine-downtime-notify/jWjCxoPOP8Y
We are experiencing the same thing, started happening today - we didn't change anything so we assume it is an internal breakage in one of the blobstore service mechanims