Network Allowlist Settings for Using Blaze on a Corporate Network
Corporate firewalls, proxies, web filters, or endpoint security products may block connections required for Blaze sign-in and normal use.
Share the destinations on this page with your IT team or internal help desk if you experience any of the following:
- The sign-in screen displays a message stating that Blaze cannot connect to the server
- Blaze works on another network, such as a mobile hotspot, but not on the corporate network
- Connecting to Salesforce, adding a Skill from GitHub, or updating Blaze fails
Required Network Settings
Allow Blaze to connect to the internet using the following settings.
| Item | Required setting |
|---|---|
| Direction | Outbound |
| Protocol | HTTPS |
| Port | TCP 443 |
| Allowlist type | FQDN (domain name), not IP address |
Blaze does not require any inbound ports to be opened. Because the IP addresses used by cloud services and download providers may change, allow the FQDNs below instead of fixed IP addresses.
Destinations required for Blaze
| Destination | Purpose |
|---|---|
auth.igness.ai | Blaze authentication |
id.igness.ai | Sign-in and identity flows |
blaze-api.igness.ai | Blaze API |
llm.igness.ai | AI features |
account.igness.ai | Account, organization, and device management |
These are the destinations used by the Blaze production environment. For normal use, start by allowing HTTPS access to all destinations in this table.
Destinations used for GitHub downloads
Blaze uses GitHub when adding Skills from public GitHub repositories. Blaze installations distributed outside the Microsoft Store also use GitHub to check for and download application updates.
| Destination | Purpose |
|---|---|
api.github.com | Check the latest Blaze version |
github.com | Download Blaze updates |
codeload.github.com | Download Skill ZIP archives from public GitHub repositories |
release-assets.githubusercontent.com | Download files from GitHub Releases |
objects.githubusercontent.com | Download files after a GitHub redirect |
github-releases.githubusercontent.com | Download GitHub update and release files |
To add Skills from GitHub, allow direct connections to codeload.github.com. Application update downloads may redirect to another domain, so in addition to github.com, allow the githubusercontent.com destinations listed in the table. If your organization’s policy supports wildcard entries, you may instead cover GitHub’s content delivery destinations with *.githubusercontent.com.
💡 The Microsoft Store edition does not require the application-update destinations. However, it still requires access to
codeload.github.comwhen adding Skills from GitHub.
Destinations used to connect to Salesforce
When connecting Blaze to a Salesforce org, also allow the destinations required by that org.
| Destination | Purpose |
|---|---|
login.salesforce.com | Sign in to a Salesforce production org |
test.salesforce.com | Sign in to a Salesforce sandbox |
Your org’s *.my.salesforce.com | Salesforce API access after sign-in |
Your org’s *.salesforce.com | Salesforce instance API access |
My Domain and instance URLs vary by Salesforce org. Where possible, allow only the specific FQDNs used by your Salesforce org instead of broad wildcard entries.
If Blaze still cannot connect
- Quit Blaze completely, then reopen it.
- Retry sign-in or whichever operation failed.
- If you use a VPN, follow your organization’s policy and compare the result while connected and disconnected.
- Review your security product’s block log for any rejected destinations not listed above.
If the issue continues, contact support and include the following information:
- The date and time when the error occurred
- The displayed error message or a screenshot
- Your operating system and Blaze version
- Whether the result differs between the corporate network and another network
- The blocked domain reported by the security product, if available
Do not send secrets such as verification codes, passwords, or access tokens.