Skip to content

Commit 0b97053

Browse files
authored
Update custom-proxy.md
1 parent a14f8c6 commit 0b97053

File tree

1 file changed

+3
-3
lines changed
  • src/connections/sources/catalog/libraries/website/javascript

1 file changed

+3
-3
lines changed

src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ To set up a custom domain, you need:
1515
- Access to the CDN settings
1616
- A security certificate for the proxy domain
1717

18+
> info "Custom Proxy Troubleshooting"
19+
> If you experience issues configuring a custom proxy, contact your organization's IT department for help. Segment does not have access to the resources you need to configure a custom proxy.
20+
1821
This guide explains how to set up a custom domain in CloudFront. You can apply these principles to almost any modern CDN that supports proxies.
1922

2023
You need to set up two important parts, regardless of the CDN provider you use:
@@ -100,6 +103,3 @@ To add a CNAME record to your DNS settings:
100103
- **Value**: Tracking API CloudFront Distribution Domain Name
101104
3. Save your record. This might take some time to take effect, depending on your TTL settings.
102105
4. Run `curl` on your domain to check if the proxy is working correctly.
103-
104-
#### Troubleshooting
105-
Please note that setting up a custom proxy is something that is configured entirely by you and your engineering team. While we are always here to help support and brainstorm ideas should you come across any technical issues, troubleshooting custom proxy errors is challenging from the Segment side of things due to limited visibility into your codebase and not having access to your custom setup.

0 commit comments

Comments
 (0)