How to troubleshoot and debug Azure Web PubSub event handler locally

When a WebSocket connection connects to Web PubSub service, the service formulates an HTTP POST request to the registered upstream and expects an HTTP response. We call the upstream as the event handler and the event handler is responsible to handle the incoming events following the Web PubSub CloudEvents specification.

When the event handler runs locally, the local server is not publicly accessible so we need some tunnel tool to help expose localhost publicly so that the Web PubSub service can reach it.

Use localtunnel to expose localhost

localtunnel is an open-source project that help expose your localhost publicly. Install the tool and run the follow command (update the <port> value to the port your event handler listens to):

lt --port <port> --print-requests

localtunnel will print an url (https://<domain-name> that can be accessed from internet, for example, And --print-requests subcommand prints all the incoming requests so that you can see later if this event handler is successfully invoked.

There are also other tools to choose when debugging the webhook locally, for example, ngrokloophole, TunnelRelay or so.

Test if the event handler is working publicly

Some tools might have issue returning response headers correctly. Try the following command to see if the tool is working properly:

curl https://<domain-name> -X OPTIONS -H "WebHook-Request-Origin: *" -H "ce-awpsversion: 1.0" --ssl-no-revoke -i

https://<domain-name> is the path that your event handler listens to. Update it if your event handler listens to other path.

Check if the response header contains the webhook-allowed-origin header. This curl command actually checks if the WebHook abuse protection request responses with the expected header.

Next steps

Use these resources to start building your own application: