Configuring network firewall or proxy server settings

If you're trying to use Krisp on a corporate network, which is behind a proxy or a firewall, you may need to add some additional configurations to make Krisp work properly.

If you're using Krisp Windows version, it will detect system proxy settings automatically and will try to connect to the internet using those configs. However, if you are using Krisp Mac, or if your proxy is configured as block all/allow list, then you would need to allow the servers that Krisp connects to.

 

Ports

Krisp is using standard port 443 for https connections.

 Port  Purpose
Outbound TCP 443                   Required to connect to our backend services.

 

Domains

To ensure connectivity the wildcard rule of *.krisp.ai and port 443 would be recommended.

If for some reason you decide not to use the wildcard, you would need to allow specific domains listed below. You would need to check the list often so as not to miss an update.

Domain Purpose
krisp.ai Used for accessing the main website.
api.krisp.ai * Used for connection to Krisp servers and syncing configuration.
account.krisp.ai * Used for connection to Krisp servers and syncing configuration.
help.krisp.ai Used for accessing the Krisp help center.
cdn.krisp.ai * Used for showing the onboarding videos, downloading app installers, etc.
analytics.krisp.ai * Used for sending analytics data.
upload.krisp.ai * Used for sending problem reports.

* required for the app or some of its features to work properly

 

Google hostnames

We use ReCaptcha to protect the website from malicious activities. It's a Google service, and you won't be able to sign in/sign up if your system fails to use it. For accessing it, the below-mentioned Google hostnames should be allowed.

  • gstatic.com
  • google.com/recaptcha/
  • recaptcha.net

Besides that, you need to also allow the IPs mentioned here. Make sure to periodically check those as they may occasionally change.

Check this article for more information about ReCaptcha.

 

Additional information

Crash reporting: https://{subdomain}.sentry.io/{endpoint}

Was this article helpful?
9 out of 13 found this helpful

Have more questions? Submit a request