Prerequisites Checklist
Before the FenixPyre onboarding process can begin admin should make sure the following criterias and requirements are met
Once complete please contact FenixPyre support so we can schedule a call to begin the FenixPyre onboarding.
Firewall Settings
To ensure smooth communication between the FenixPyre Desktop Client and our SaaS servers, please make sure your firewall settings are updated with the below requirements.
Domain Whitelisting
Please ensure these domains are whitelisted in your Firewall to guarantee proper operation of the FenixPyre service on user client devices.
apis.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre Configuration
fenixshare.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre sharing portal
mtls.apis.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre mutual TLS
admin.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre admin dashboard
oauth.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre authentication
office.datanchor.io
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre Document Editors
wopi.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre Document Editors
anchormydata-com.us.auth0.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre authentication
agent-logs-stream.anchormydata.com
HTTPS (http over TLS 1.2/1.3)
443
FenixPyre Install Logs
IP Whitelisting
It is essential to configure your firewall to allow outbound connections to the following IP addresses used by our underlying service providers: Auth0 (for authentication), Cloudflare (for CDN and security), and Google Cloud Platform (for various APIs and services).
1. Auth0 (Authentication Service)
Auth0 handles user authentication processes.
IP Addresses to Whitelist (Grouped by Region):
United States (US) (For US Customers):
174.129.105.183, 18.116.79.126, 18.117.64.128, 18.191.46.63, 18.218.158.118, 18.218.26.94, 18.232.225.224, 18.233.90.226, 3.131.238.180, 3.131.55.63, 3.132.201.78, 3.133.18.220, 3.134.176.17, 3.19.44.88, 3.20.16.23, 3.20.244.231, 3.21.254.195, 3.211.189.167, 34.211.191.214, 34.233.19.82, 34.233.190.223, 35.160.3.103, 35.162.47.8, 35.166.202.113, 35.167.74.121, 35.171.156.124, 35.82.131.220, 44.205.93.104, 44.218.235.21, 44.219.52.110, 44.224.190.45, 44.246.144.93, 52.12.243.90, 52.14.149.14, 52.2.61.131, 52.204.128.250, 52.206.34.127, 52.33.36.223, 52.43.255.209, 52.88.192.232, 52.89.116.72, 54.145.227.59, 54.157.101.160, 54.200.12.78, 54.209.32.202, 54.245.16.146, 54.245.93.221, 54.68.157.8, 54.69.107.228
Europe (EU):
18.197.9.11, 18.198.229.148, 3.125.185.137, 3.65.249.224, 3.67.233.131, 3.68.125.137, 3.72.27.152, 3.74.90.247, 34.246.118.27, 35.157.198.116, 35.157.221.52, 52.17.111.199, 52.19.3.147, 52.208.95.174, 52.210.121.45, 52.210.122.50, 52.28.184.187, 52.30.153.34, 52.57.230.214, 54.228.204.106, 54.228.86.224, 54.73.137.216, 54.75.208.179, 54.76.184.103
Australia (AU):
13.210.52.131, 13.238.180.132, 13.55.232.24, 16.50.37.252, 16.51.137.244, 16.51.49.47, 54.153.131.0, 54.252.2.143, 54.79.31.78
Canada (CA):
15.222.97.193, 3.97.144.31, 40.176.144.225, 40.176.166.165, 40.177.34.170, 99.79.94.44
Japan (JP):
13.208.85.227, 15.152.185.222, 15.152.2.46, 15.152.28.221, 15.152.56.146, 15.152.95.63, 176.34.22.106, 35.74.30.168, 43.206.201.6, 46.51.243.250, 54.150.87.80, 54.248.192.141
United Kingdom (UK):
18.135.40.36, 3.10.89.10, 3.8.59.62
2. Cloudflare (CDN & Security)
Cloudflare is used for content delivery, performance optimization, and security for several endpoints.
IP Ranges to Whitelist (CIDR Notation): Cloudflare utilizes a large range of IPs. It is recommended to whitelist these entire ranges:
173.245.48.0/20 103.21.244.0/22 103.22.200.0/22 103.31.4.0/22 141.101.64.0/18 108.162.192.0/18 190.93.240.0/20 188.114.96.0/20 197.234.240.0/22 198.41.128.0/17 162.158.0.0/15 104.16.0.0/13 104.24.0.0/14 172.64.0.0/13 131.0.72.0/22
(For the most current list, refer to Cloudflare's official IP ranges page: https://www.cloudflare.com/ips/)
3. Google Cloud Platform (APIs & Services)
Various Google Cloud services are used for APIs and application hosting.
IP Addresses to Whitelist: The following specific Google IP addresses are currently known to be used:
34.168.41.125 34.49.147.218 34.58.168.108 34.49.85.80 34.49.231.16 34.120.34.82 34.49.2.34 34.102.184.168 34.120.207.202 35.227.235.21 34.36.159.126 34.95.74.209 34.172.254.182 34.120.144.215 34.49.5.35 34.49.28.53 35.244.198.68 35.241.21.239 34.149.5.18
Spam Filter Settings (Email Settings)
To ensure FenixPyre's emails are delivered during device registration and user authentication for secure sharing, adjust spam filters to allow these messages. Access permission may be necessary.
Confirm users can receive mail from [email protected], [email protected], [email protected] (sent from SendGrid by Twilio - em8537.anchormydata.com)
Whitelist FenixPyre's Client Software in your Antivirus/EDR/XDR
The FenixPyre Windows Agent installs various components such as filesystem drivers, background daemons, and local services. These components might be mistakenly flagged or blocked by your AV/EDR/XDR systems. To ensure seamless operation, consider adding FenixPyre services to the whitelist or trusted applications list in your security software.
Follow this guide to whitelist FenixPyre Client Software in your AV/EDR/XDR systems
Minimum System requirements
The FenixPyre Windows Agent is compatible only with 64-bit (X64) architecture processors. Support for ARM architecture processors is currently not available
Apart from that we also require the following requirements to be met.
The AppData folder, which stores important application data, must be located on local storage rather than network storage. This is critical for performance and reliability during the operation of FenixPyre.
FenixPyre Root Certificate Authority
FenixPyre uses a Private Certificate Authority which issues client certificates for each device using the FenixPyre Windows Agent. Since this Certificate Authority isn't trusted by default, TLS communications between the FenixPyre client on Windows and FenixPyre Cloud APIs may be blocked. To prevent issues, please whitelist the Root CA certificate or add it to the Trusted Root Certification Authorities.
Last updated
Was this helpful?