How to Fix “Your Connection Isn’t Private” in BoldDesk
The browser message “Your Connection Isn’t Private” typically indicates that the browser cannot validate the website’s SSL (Secure Socket Layer) certificate chain. Common causes include incorrect device time, corrupted browser data, antivirus SSL inspection, or network/proxy SSL interception.
This article provides the most effective steps to restore access to the BoldDesk portal when this SSL validation error blocks the connection.
Symptoms and Common Error Indicators
You may observe one or more of the following:
- Browser warning page: Your Connection Isn’t Private
- Inability to load the BoldDesk portal URL (including a custom domain)
- Browser/network error:
ERR_CONNECTION_CLOSEDERR_CONNECTION_CLOSEDindicates the connection was terminated unexpectedly and is usually caused by network, firewall, proxy, SSL, or server connectivity issues, not authentication or role permissions.
If you’re encountering “Your Connection Isn’t Private” or you are unable to access the BoldDesk portal, here are the most effective troubleshooting steps:
Check System Date and Time
Incorrect system time can cause SSL certificate validation to fail. Ensure your system date and time are correctly configured.
-
On Windows
Go to Settings > Time & Language > Date & Time → Enable Set time automatically and Set time zone automatically → Click Sync now -
On macOS:
Go to System Preferences > Date & Time → Enable Set date and time automatically
Clear Browser Cache and Cookies
Corrupted cache can interfere with SSL validation. Clear your browser cache and cookies, then access the site again.
- Chrome: Settings > Privacy > Clear Browsing Data
- Firefox: Settings > Privacy & Security > Clear Data
- Edge: Settings > Privacy, Search & Services > Clear Browsing Data
Try Incognito Mode/Use Another Browser
Browser extensions may block secure connections. Open the portal in Incognito/Private mode to test. If the issue continues, try using a different browser.
Disable Antivirus HTTPS Scanning
Some antivirus tools interfere with SSL. Temporarily disable HTTPS scanning features to test if this resolves the issue.
Use a Secure Network/Different Network
Avoid public Wi-Fi unless using a VPN. Public networks may block SSL or redirect traffic. Check by connecting through another network to rule out any network-related SSL inspection or firewall restrictions.
- If the issue persists after following these steps, please consult your IT administrator to ensure that network-level SSL inspection policies or proxy settings are not causing the error. For additional assistance, kindly contact BoldDesk support.
- The
ERR_CONNECTION_CLOSEDerror indicates that the connection to the BoldDesk URL was unexpectedly terminated, typically due to network, firewall, proxy, SSL, or server connectivity issues rather than authentication or permission settings. As a troubleshooting step, try accessing the URL using an Incognito/InPrivate window, a different browser, or another network. If the issue is related to a domain change, note that updating the default domain deactivates the previous domain URL, while all existing tickets, data, and configurations remain unaffected.
Frequently Asked Questions
-
What does “Your Connection Isn’t Private” mean for the BoldDesk portal?
It means the browser cannot validate the SSL certificate presented by the BoldDesk portal URL (including a custom domain), usually due to a time mismatch, interception, or certificate trust issues. -
Why does fixing my device time resolve the issue?
SSL certificates include validity dates. If the device clock is incorrect, the browser may treat a valid certificate as expired or not yet valid and block the connection. -
What does
ERR_CONNECTION_CLOSEDindicate?
ERR_CONNECTION_CLOSEDusually means the network connection was terminated unexpectedly due to network, proxy, firewall, SSL inspection, or connectivity issues—not due to authentication or BoldDesk permission settings. -
Why does the portal work in Incognito/Private mode but not in normal mode?
Private mode often runs with fewer cached artifacts and may behave differently with extensions. This points to browser cache corruption or an extension interfering with SSL/TLS connections. -
Can antivirus software cause SSL errors when visiting a custom domain?
Yes. Antivirus HTTPS scanning (SSL inspection) can break certificate validation if it injects an untrusted certificate or misconfigures inspection rules. -
Why does switching networks help?
Some networks intercept SSL traffic, enforce proxies, or block certain certificate chains. Testing on another network helps confirm whether the cause is local device or network policy related. -
If my custom domain changed, is older domain access expected to fail?
Yes. When the default domain is updated, the previous domain URL is deactivated, while all existing data (tickets and configurations) remain intact.