Bobcares

Webhook 503 service unavailable error – Fixed

by | Oct 31, 2019

Webhooks allow you to receive real-time notifications. For every developer, it is a kind of cool stuff unless it appears with webhook 503 service unavailable error.

Quite often, the same error pops up while using the applications in real servers.

That’s why at Bobcares we periodically get requests to solve such Webhook errors as a part of our Server Management Services.

Today, let’s analyze the causes and see how our Support Team fix Webhook errors for our customers.

 

What is a Webhook?

Webhooks are calls from one server to another. To clarify, on some specific events, it will trigger a call.
For example, say we have two abc.com and xyz.com. Meanwhile, if you signup on abc.com, it will send a request to xyz.com. Site xyz.com may use the call to send an email or something like that.

In real life, many popular applications use Webhooks. One classic example is Stripe payment solution. It has a webhook that will automatically send an email to a customer whenever a payment fails to go through.

 

Cause and Fix for webhook 503 service unavailable error

The error is more like a general server error rather than with the app. To clarify, the 503 error occurs mainly due to an unresponsive backend server.

All events include some information that we need to process and respond to it. For instance, let’s take the example of a messenger bot. Messenger platform will notify our bot via webhook event. Events trigger when any customer sends a message to our business page. Meanwhile, we need to process the information and respond to the event. So as a response our bot will reply with an automated message to the customer based on the query.

In case our server where the bot is present is down, the event will return 503 error as below :

{
"code": 143,
"error": "Invalid webhook response status: 503 Service Unavailable"
}

We’ll see the possible causes and how our Support Team fixed it.

 

1. Server Connectivity Issue

While it may sound simple, it simply indicates that the server somewhere in the chain is down or unreachable for whatever reason. It may return error as below :

webhook 503 service unavailable error

Most modern Application does not reside on a single server. In other words, it is spread over multiple servers. Moreover, it may rely on any other 3rd party services too.

We start checking through all the workflows. The real challenge lies in finding the error source. We then fix the error causing the server unreachable. The common reasons include server firewall blocks, network errors, etc.

 

2. Host down

In many cases, the host of the application may be down. As a result, the error may happen.

We properly reboot all the systems. We also make sure that the webserver is up and running.

 

3. Application code or script bug

Additionally, some custom code within the application may also cause the 503 service unavailable error.

We usually dig the root cause or the file or code causing the problem. After that, we inform our client to consult the developer to fix the code.

 

[Having trouble in fixing webhook errors? – We’ll fix it for you.]

 

Conclusion

In short, the webhook 503 service unavailable error happens mainly because of server-side issues. Today, we saw how our Support Engineers fix errors related to webhooks.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF