Getting 404 errors

**Joey Jo Jo** · 29-10-2014, 04:42 AM

We consistently get a batch of 404 errors every day. Haven't ever really noticed when it is happening but it is always our from our software hitting the AUS endpoint. We also get quite a few other errors in regards to connections to the API as well, such as "A connection that was expected to be kept alive was closed by the server.". Have not really dug into it too much because I am 99.999999% confident it is on the API side and we have other priorities.

**betdynamics** · 29-10-2014, 02:34 PM

Yes - I have exactly the same.

**Mr Magoo** · 30-10-2014, 12:46 PM

Yes, I've seen these 404s on several days now, it's always the AUS exchange too.

**Mr Magoo** · 02-11-2014, 10:48 AM

Where are you, Betfair developers? Have you stopped bothering to read your own forums? This here is an actual bug. It would be nice if you could respond, or even try to fix it.

**Lopiner** · 02-11-2014, 12:08 PM

On the UK exchange i have plenty of these "A connection that was expected to be kept alive was closed by the server."

**Mr Magoo** · 03-11-2014, 03:13 PM

The 'A connection that was expected to be kept alive was closed by the server' error is nothing to worry about, IMO. It's just a part of HTTP. Clients can try and re-use existing connections to the server, but the server is allowed to drop these idle keep-alive connections at any point. It's not a problem with Betfair's servers unless it is happening on every request.

The 404 errors continue for me, they are solely on the AUS exchange and are quite repeatable. Yesterday I updated my code to make it establish a new connection to the server and retry any 404 error. What I saw was that the new request also failed with a 404.

**BetfairDeveloperProgram** · 03-11-2014, 05:20 PM

Hi Mr Magoo,

This issue has been raised for further investigation.

We'll provide an update as soon as we have one.

Thanks

Neil

**BetfairDeveloperProgram** · 04-11-2014, 01:30 PM

Hi All,

We believe the issues reported were caused by a network issue that we identified yesterday which primarily affected the Australian exchange resulting in significant packet loss.

As a result we have now switched to our back up provider which should have resolved the majority of these issues.

However, please let us know if you continue to see further occurrences.

Kind Regards

Neil

**Mr Magoo** · 05-11-2014, 10:45 AM

Thanks for the response!

I'm still seeing lots of 404s from this morning, around 3:17am and 8:15am GMT.

Yesterday there were worse problems, lots of failures to connect / no route to host, around 4:30am - this could be the network problem you saw? It appears to be something separate to the 404 errors.

The '404 Not Found' is more puzzling because it implies that my program managed to connect to your servers, validated the SSL certificates and *then* it hit a problem on the server. So I'm not sure that a network error could really explain it. In any event, I'm afraid that the errors continue...

**BetfairDeveloperProgram** · 05-11-2014, 01:05 PM

Hi Mr Magoo,

If you can provide details of your error log (including timestamps) this would help us to see if we can tie these errors up with a specific issue at our end.

If you can send details to bdp@betfair.com that would be great.

Thanks

Neil

**Joey Jo Jo** · 07-11-2014, 03:29 AM

We are also still getting 404 errors amongst others. We also get timeout errors. Last batch was at 00:54 UTC which we were getting these errors -

Unable to connect to the remote server.
The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
The operation has timed out.

This happens everyday and has been for weeks.

**awinner** · 07-11-2014, 05:24 AM

errors

Im getting underlying connection closed errors on api-au.

**awinner** · 08-11-2014, 08:46 AM

404 error

sat 8/11 worked fine all day then the mystery error hit. It appears that the api just disappears.

This is what i got back from the debugger:
8/11/2014 6:31:39
"<html><head><title>Apache Tomcat/5.5.33 - Error report</title><style></style> </head><body><h1>HTTP Status 404 - /exchange/betting/json-rpc/v1</h1><HR size=\"1\" noshade=\"noshade\"><p><b>type</b> Status report</p><p><b>message</b> <u>/exchange/betting/json-rpc/v1</u></p><p><b>description</b> <u>The requested resource (/exchange/betting/json-rpc/v1) is not available.</u></p><HR size=\"1\" noshade=\"noshade\"><h3>Apache Tomcat/5.5.33</h3></body></html>"

**HarryHindsight** · 08-11-2014, 07:47 PM

Failure response received (502)

Received the above error in an app and on the visualiser.

Getting 404 errors

Getting 404 errors

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment