Custom Domain ignored in various places dealing with 3rd party services
Danilo Alonso
Examples:
- When I check off to create a webhook, EP uses the server's IP instead of custom domain.
- When a notification comes in, IP is used instead of custom domain.
This breaks the loop-back cycle with 3rd party integrations completely.
I secure my EP by blocking direct access to the server. It's only accessed via CF proxy on port 80 / 443. I only allow CF IPs to hit port 80 and 443. This means that GH webhook servers can never access my server and thus fail.
What should happen is: If a user sets a custom domain, network features that interact with the EP instance should only ever use Custom Domain, and never the IP.
As I understand, you guys internally use the server's IP to register its existence, and that's OK. Everything else should use Custom Domain.