502 Bad Gateway on API request

General
1

From yesterday i get this response on every API requests.
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.8.1</center>
</body>
</html>

My app id: 534C490F-4A57-DF32-FFC3-1B7DFDCF3C00

2

We had an issue which was discussed here:

http://support.backendless.com/t/redis-error

It should be resolved now.

Regards,
Mark

3

Thanks for your quick response. But problem still occurs in my case.

4

Could you please provide a sample API request which results in an error?

5

https://api.backendless.com/534C490F-4A57-DF32-FFC3-1B7DFDCF3C00/v1/files/web/scripts/greatmoments.js

6

That’s a hosted script - a little bit different than the problem we had fixed earlier. Our admin will look into it.

Regards,
Mark

7

I am waiting for your response and thanks in advance

8

The problem has been resolved. Please check.

Regards,
Mark

9

Sorry to inform now i get this
{“code”:17000,“message”:“No script runner is available”}

10

Now everything works just fine. Thanks for your responsiveness :slight_smile:

11

Not working everytime

12

Hi after few successful attempts it starts showing
{“code”:17000,“message”:“No script runner is available”}

in
most of the cases. I used this in a live app so its urgent to solve the
problem. Sometimes it works great but almost 70% cases it shows above
response.

13

We are getting intermittent 502 Bad Gateway on different requests as well. Are there any updates?

14

Hi,

We’re working on it. Sorry for the inconvenience.

15

Should be working now.

16

It’s been working on and off all day. But it is still very slow here - compared to the last few days

17

We moved a part of the system to a dedicated instance. There was an outage for a few minutes, but now it’s functioning normally and should work slightly faster. Please check again.

18

Getting 502 Bad Gateway problem, when integrating Backendless with Rails app and executing commands from console. Application Id: 73DA96E9-B130-3A37-FFD9-A531CFA7FD00. Where as running the same set of curl with Postman making it a success.

19

Prateek, please open a separate support topic so each issue can be tracked individually.

In there specify what exactly fails in console.

Regards,
Mark