Since today other people and me are getting 504 Response / Timeout while using the Rest Routing API.
Yesterday everything worked fine. When I try to call the API via Browser I also get 504 Gateway Timeout.
Other APIs are working as expected. It's only the Routing API which fails with 504.
Requests are sent from Germany.
The status page shows that everything is up and running, but the Routing API is unreachable.
It started to work again as it should 3 minutes ago..
So I think the problem was solved by here.com ..
Related
We have been getting 503 Service Unavailable responses recently using the HERE API autosuggest endpoint. When it occurs, it can last for hours. Below is a typical request we get a 503 response from:
https://places.api.here.com/places/v1/autosuggest?q=Bradford&at=52.8,-1.4&addressFilter=countryCode=GB&result_types=address,place&app_code=########&app_id=###########
We have been using this service for a long while now and majority of the time the endpoint responds as expected. However, we are using it in a production environment, so any downtime (especially hours) is not good. Can we do anything when 503 occurs (E.g. calling a different endpoint)?
Thank you for any help or suggestions
Unfortunately no you cannot, outside of ensuring your application itself responds correctly to the error. You can also bookmark our status page (https://status.here.com/status) for more information when something goes wrong. I'm sorry the API was flakey for you recently, but hopefully this is just a temporary issue and doesn't return.
Not sure why this is occurring. I've been using this daily for months and it suddenly broke this morning. Its returning the following error.
CrawlerError: The page couldn't be opened (status: fail, url: https://history.com/this-day-in-history/, lastResourceError: {"errorCode":403,"errorString":"Error downloading https://history.com/this-day-in-history/ - server replied: Service Unavailable","id":1,"status":503,"statusText":"Service Unavailable","url":"https://history.com/this-day-in-history/"}, lastResourceTimeoutResponse: null)
Nothing in the code has changed, website is still up and running fine. Is there any reason why it might stop working suddenly?
This might mean that the website now recognizes you as a bot and is blocking your requests. I would check some articles in this docs section. We are also working on anti-scraping guide.
I have a couple Azure VMs behind a Basic Load Balancer with an HTTP URL Health Probe for the Backend Pool. To mark a server down, that URL returns Status Code 503 (Service Unavailable), but when I call that page from those VMs, the Status Code returned is 403. That still has the desired effect, I suppose, of marking the server down - but I dont understand why the code I set has changed.
This is from an ASP.NET web forms application on the VMs. I look at developer tools in the browser, and from my local machine or from a Dev server on our local network, that page returns Status Code 503, but calling that page from the VMs in Azure, the Status Code is 403.
Here's where I set the Status Code in that page:
Response.Clear()
Response.StatusCode = 503
Response.Flush()
I suppose I should mention that my local is a Windows 10 box, and the server VM is Windows Server 2016. Both are running IIS 10. The application is compiled with .NET Framework 4.6.
Here's the dev tools from my localhost:
Here's the dev tools from the server in azure:
Why the change? Anything I can do to stop this behavior?
So today I tried enabling Failed Request Tracing, but either something wasnt set up correctly, or the error was being handled elsewhere, and didnt result in any failed requests being logged.
Since I wasnt getting any failed requests logged, I opened up Process Monitor and could see that immediately after the call to my Health Probe page, I was getting a call to my custom HTTP Error page. That page must have been what was giving the 403 (dont know why, b/c that page works correctly for other HTTP Errors with a friendly error message and logging of the error to my custom error tracking solution).
I was going to change the Status Code to see if there was something special with the 503 that I was setting that was handled differently in IIS, but that got me thinking about how I was setting the status code...
In my research today, I saw this page https://www.leansentry.com/HowTo/AspNet-Response-Flush-Poor-Performance which cautions against using Response.Flush(). The code that I had implemented was in the Page_PreRender method, so there's not really a need to Flush there anyway.
I removed the Response.Flush and of course, my troubles went away.
The Health Probe page no longer triggers an Error from the Azure VM, and therefore, the status code that I get in my client browser is the 503 that I set in code.
So I guess this case is closed. I will need to figure out why the HTTP Error page was throwing a 403 instead of returning the friendly error message, but that should be easy enough...
I've got the Google Website translator widget on my site (www.ancient.eu.com). It used to work perfectly, but now I am not getting any translations. When I check the Chrome Console I see the following errors:
POST http://translate.googleapis.com/translate_a/t?anno=3&client=te&format=html&v=1.0&scid=e669185dd7423a09-043358cb90b67c5d-g813cc84edafdd3ce-12&logld=v10 502 (Bad Gateway 51001) element_main.js:248
XMLHttpRequest cannot load http://translate.googleapis.com/translate_a/t?anno=3&client=te&format=html&v=1.0&scid=e669185dd7423a09-043358cb90b67c5d-g813cc84edafdd3ce-12&logld=v10. Origin http://www.ancient.eu.com is not allowed by Access-Control-Allow-Origin.
Does anyone know what went wrong here?
Thanks for your help.
Jan
I have an application, written in C++.
This app dispatches a certain info to a script located on a remote website using HTTP POST requests. The app sends requests with a period from several seconds to several minutes.
The problem is that after about a half an hour of working without errors, the app starts to get a 408 Request timeout error from the web server. Then the app starts to retry posting but the server keeps on responding with 408 Request timeout.
An interesting observation: the error disappears after I access the website using a browser and the app works OK for about 30 minutes after that, then the issue comes back.
What could be the reason and is there any workaround to this?
PS: the app works on a usual PC with XP Workstation. The website is on GoDaddy web server.
thanks in advance
I know this is an old post but thought this might help someone since this problem cause me hours of frustration.
I was experiencing the same issue with a GoDaddy webserver. My Android app sent POST requests to the server and would work as expected but I started experiencing 408 Request timeout errors after 30 mins or so. I also noticed that the problem went away if I opened up a browser and opened my home page (PHP Wordpress site) from a PC or the Android device. The website was in test so web traffic was minimal and I was able to confirm this behaviour in the server logs fairly easily.
I logged a support call to GoDaddy but whilst their staff were responsive and helpful, they did not provide any useful information to explain the behaviour.
I was however able to work around the issue by simply executing a dummy GET request before my POST request and this 'woke up' the web server and it responded to all subsequent POST requests.