Users of Outreach.io are encountering a "Your Connection is Not Private" error when accessing branded URLs.
This problem is relevant to Outreach users who utilize branded URLs for their outreach campaigns.
- This issue occurs particularly for customers who cannot use Let's Encrypt as their certificate provider.
1. Set Up a Proxy:
Disclaimer: This workaround involves setting up a proxy, and it will be the responsibility of the user and their IT team to implement. Outreach does not provide direct support for proxy configurations.
Proxy Configuration: Users can set up a proxy server to act as an intermediary between their browser and the Outreach.io service. The proxy server can handle SSL/TLS termination, effectively bypassing the certificate issue. Users should consult their IT or network team for assistance in configuring and maintaining the proxy.
2. Use Another Sub-Domain:
If setting up a proxy is not feasible or preferred, consider using an alternative sub-domain for your Outreach.io branded URLs.
- Choose a different sub-domain (e.g., subdomain2.yourcompany.com) for your Outreach.io branded URLs.
- Ensure that this sub-domain has a valid SSL/TLS certificate from a certificate provider that is compatible with your environment.
- Update your Outreach.io settings to use the new sub-domain for your branded URLs.
The "Your Connection is Not Private" error typically occurs when the SSL/TLS certificate presented by the server is either invalid or not trusted by the user's browser. In cases where Let's Encrypt certificates cannot be used, this issue may arise due to incompatible certificate providers.