I made POST requests to my endpoint url by postman, and got the hook normally.
The normal event hooks are fine, but only the de-auth hook is missing.
I found the only difference between the two kinds of hook is the IP source.
normal event hook: 3.X.X.X
de-auth hook: 18.X.X.X
We checked the firewall, and we don’t blocked the 18.X.X.X.
I tested the ngrok with my application, it can get the de-auth hook.
But, when I change the de-auth endpoint to my hostname, it can’t get any de-auth request.
It seems to be weird…
Maybe the telecom company is the problem? (Our company is at Taiwan)
Can you help us to check or provide the status code of the de-auth hook?
Or, any idea about this circumstance?
I’m sure I am installing the production version of my app in the “Submit” page.
I use the ngrok service in “Deauthorization Notification Endpoint URL”, I get all type hook notifications.
But when I change to our own hostname, I can only get the normal event hook.
Only the de-auth hook is missing.
If you are able to get the deauth webhook with your local ngrok environment, then something is not configured properly on your end in your production environment. Make sure your production deauth url is not behind a VPN or firewall.