- #HOW TO WHITELIST A WEBSITE ON PORT 80 AND 443 HOW TO#
- #HOW TO WHITELIST A WEBSITE ON PORT 80 AND 443 UPDATE#
Service for is provided through Fastly and is subject to change without warning.
#HOW TO WHITELIST A WEBSITE ON PORT 80 AND 443 UPDATE#
If you have an existing configuration that uses port 80, you can update it to use port 443, the default New Relic connection. While some agents can be configured to use both port 80 and port 443, we recommend that you choose the port 443 (default). Some New Relic agents also offer port 80, an unsecured channel open to all HTTP traffic. Recommendation: Use port 443, a secured channel for encrypted HTTPS traffic. Use the IP connections for account data in the US or European Union region as appropriate:Ĭollector*.:443 (recommended) To add the following IP connections to the allow list, follow the specific procedures for the operating system and the firewall you use. New Relic agents require your firewall to allow outgoing connections to the following networks and ports. To enhance network performance and data security, New Relic uses a CDN and DDoS prevention service with a large IP range. Synthetics code editor autocompletion functionality Static New Relic assets behind AWS CloudFront CDN New Relic One catalog assets behind AWS S3
If your organization uses a firewall that restricts outbound traffic, follow the specific procedures for the operating system and the firewall you use to add the following domains to the allow list. It also doesn't cover Nerdpacks or other features that communicate with external services that have additional domain requirements.
This list doesn't cover domains that New Relic connects to that can be blocked without affecting your usage of the product. Blocking domains can cause issues with individual product features or prevent pages from loading altogether. Update your allow list to ensure New Relic can communicate with a number of integral domains that are listed in this section. Your browser must be able to communicate with a number of domains for New Relic One to work properly. In addition, TLS 1.2 is required for most domains, except:įor future updates to required and supported protocol versions, follow the Security Notifications tag in New Relic's Explorers Hub. For more information, see New Relic's Explorers Hub post about TLS 1.2. Our preferred protocol for all domains is TLS 1.2. To ensure data security for our customers and to be in compliance with FedRAMP and other standards for data encryption, Transport Layer Security (TLS) is required for all domains. To monitor the performance of your network, see Get started with network performance monitoring.
#HOW TO WHITELIST A WEBSITE ON PORT 80 AND 443 HOW TO#
This doc describes how to ensure our agents and integrations can access New Relic's domains.
0 kommentar(er)
