Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 503. The service is unavailable #511

Closed
JAStanton opened this issue Sep 11, 2017 · 10 comments
Closed

Error 503. The service is unavailable #511

JAStanton opened this issue Sep 11, 2017 · 10 comments

Comments

@JAStanton
Copy link

My apps are calling https://codepush.azurewebsites.net/updateCheck (with a string of arguments) and I'm getting a spike of 503's. Just so you're aware :)

@atticoos
Copy link

atticoos commented Sep 11, 2017

We started to see this spike on Sept 9, and it continues today

@claykohut
Copy link

claykohut commented Sep 11, 2017

I've been seeing my builds occasionally hang / never finish loading on the codepush sync step recently -- any way I can confirm that its related to this and not something on my end?

@JAStanton
Copy link
Author

@claykohut My app aborts after N seconds if I don't think codepush will return in time so that my boot process of the app isn't dependent on if CodePush servers are alive. I recommend something similar.

@claykohut
Copy link

How many seconds are you using as N in that case, @JAStanton ?

@JAStanton
Copy link
Author

I wait 5 seconds for the download / apply step. If it doesn't happen by then I let my app continue to boot. I then apply any updates on next app launch.

@patniko
Copy link
Contributor

patniko commented Sep 12, 2017

Hi @JAStanton, we have been experiencing a few load issues with our production environments. A permanent fix should be implemented over the next 30 days as we finish up the re-architecture of our backend services, but for now we are monitoring the current problems and making adjustments to rectify them.

@max-mironov
Copy link
Contributor

Hey all, closing this as we don't see any problems with this currently, please let us know if you see this issue again.

@prayuditb
Copy link

prayuditb commented Dec 18, 2017

Hello everyone, I just got this error today. I use react-native-codepush.

Here is some of my code

const codepushConfig = {
  checkFrequency: codepush.CheckFrequency.ON_APP_RESUME,
};
...

componentDidMount() {
    codepush.sync({
      installMode: codepush.InstallMode.IMMEDIATE,
    });
  }

...
const myApp = codepush(codepushConfig)(MyApp);
12-18 23:27:39.854 13537 15879 I ReactNativeJS: [CodePush] Checking for update.
12-18 23:27:42.298 13537 15879 I ReactNativeJS: [CodePush] An unknown error occurred.
12-18 23:27:42.298 13537 15879 I ReactNativeJS: [CodePush] 503: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
12-18 23:27:42.298 13537 15879 I ReactNativeJS: <HTML><HEAD><TITLE>Service Unavailable</TITLE>
12-18 23:27:42.298 13537 15879 I ReactNativeJS: <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
12-18 23:27:42.298 13537 15879 I ReactNativeJS: <BODY><h2>Service Unavailable</h2>
12-18 23:27:42.298 13537 15879 I ReactNativeJS: <hr><p>HTTP Error 503. The service is unavailable.</p>
12-18 23:27:42.298 13537 15879 I ReactNativeJS: </BODY></HTML>

What should i do to fix this error?

@prayuditb
Copy link

prayuditb commented Dec 18, 2017

In my case, I got this error after terminating release process by pressing ctrl + c (because I forgot something). I think this error reproduced by unfinished release process.

To fix this error, you can try clear deployment history by running this command
appcenter codepush deployment clear -a <ownerName>/<appName> <deploymentName>

Warning, this command will clear all of your release histories

hopefully can help

@sergey-akhalkov
Copy link
Contributor

Hi @prayuditb, please take a look at #547 and let's move the discussion to the one common place.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants