# Webhook payload URL doesn't accept internal IP based value

**URL:** <https://meta.discourse.org/t/webhook-payload-url-doesnt-accept-internal-ip-based-value/247762>\
**Category:** Feature\
**Created:** [December 5, 2022, 9:33am UTC](https://meta.discourse.org/t/webhook-payload-url-doesnt-accept-internal-ip-based-value/247762 "2022-12-05T09:33:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dpb](https://avatars.discourse-cdn.com/v4/letter/d/e99b99/32.png) [@dpb](https://meta.discourse.org/u/dpb)\
**Post date:** [February 10, 2023, 11:52am UTC](https://meta.discourse.org/t/webhook-payload-url-doesnt-accept-internal-ip-based-value/247762/5 "2023-02-10T11:52:07Z")

</div>

Our self-hosted instance is affected by this, as well. We would like to host the service that receives the webhook only on the internal docker network; there’s no need for it to be reachable from outside.

Is there a way to allow internal webhooks?

If I understand the issue correctly, internal webhooks are not allowed such that a discourse admin, who is not entitled as a server admin, may not spy on network internals. This is not an issue on our self-hosted instance, though; our discourse admins would know about our internal structure anyway.

I would suggest a setting in the `app.yml` config to allow internal webooks, or to provide a whitelist of internal domains/IPs. This way, the server admin (not the discourse admin) remains in control of who may use webhooks for the internal network.

---

_[View the full topic](https://meta.discourse.org/t/webhook-payload-url-doesnt-accept-internal-ip-based-value/247762)._