> ## Documentation Index > Fetch the complete documentation index at: https://help.agentsy.pro/llms.txt > Use this file to discover all available pages before exploring further. # Domain and SSL Issues > Troubleshoot custom-domain connections, DNS records, HTTPS certificates, redirects, and browser errors for your Agentsy AI Experience. # Domain and SSL Issues If your custom domain does not open your Agentsy AI Experience, displays a certificate warning, or redirects visitors to the wrong page, use this guide to narrow down the cause. Most domain problems fall into one of four categories: **DNS configuration**, **domain connection status**, **HTTPS/SSL certificate readiness**, or **redirect and browser behavior**. > [!NOTE] > > This guide is for troubleshooting an existing custom-domain setup. For initial configuration, see [Custom Domains and DNS](/integrations-and-developers/custom-domains-and-dns) or [Custom Domains](/branding-and-website/custom-domains). ## Before you begin Have the following information ready: * The exact custom domain or subdomain you want to use, such as `ask.example.com`. * Access to the DNS management area at your domain provider. * Access to your Agentsy AI Experience settings. * The DNS record type, name, and target shown in your Agentsy configuration, if available. * The full error message or a screenshot of the problem. > [!WARNING] > > Do not copy DNS targets from examples, another customer's setup, or a third-party tutorial. Use the record values provided for your own Agentsy configuration. Changing unrelated DNS records can interrupt email, websites, and other services. ## 1. Identify the symptom Start with what the visitor actually sees. | Symptom | Likely area to investigate | Start here | | - | - | - | | Domain does not resolve or shows a DNS error | Missing, incorrect, or not-yet-propagated DNS record | [Check DNS records](#2-check-your-dns-records) | | Domain opens a different website | Conflicting DNS records, forwarding, or incorrect destination | [Check redirects](#5-check-redirects-and-website-routing) | | Browser reports an insecure connection or certificate error | HTTPS certificate not ready or hostname mismatch | [Check HTTPS](#4-check-https-and-ssl-certificates) | | Domain works for some visitors but not others | DNS propagation or cached records | [Allow for DNS changes](#3-allow-for-dns-propagation) | | Agentsy subdomain works but custom domain does not | Custom-domain DNS, verification, or certificate setup | [Check the connection](#6-compare-the-agentsy-address-with-the-custom-domain) | | Domain opens but visitors are sent to sign-in unexpectedly | Access configuration or application routing | [Check redirects](#5-check-redirects-and-website-routing) | ## 2. Check your DNS records Open your DNS provider's management panel and compare the domain's current records with the values specified in Agentsy. 1. Confirm that you are editing the **correct domain** and DNS zone. 2. Check the **record type** required by your setup, such as `CNAME`, `A`, or another record specified by Agentsy. 3. Check the **host/name** field. Providers may represent the root domain as `@`, while a subdomain might use a name such as `ask`. 4. Compare the **target/value** exactly with the value shown in Agentsy. 5. Look for conflicting records or forwarding rules for the same hostname. 6. Save corrections, then allow time for DNS changes to become visible. > [!TIP] > > If you use a subdomain such as `ask.example.com`, review records for that subdomain rather than changing records for the main `example.com` website. ### Common DNS mistakes | Mistake | What to check | | - | - | | Entering the full hostname where the provider expects only the subdomain | Check whether the provider automatically appends your domain | | Using an outdated DNS target | Compare against the current value displayed in Agentsy | | Leaving a conflicting record for the same hostname | Review existing `A`, `AAAA`, `CNAME`, and forwarding entries as applicable | | Updating DNS at the wrong provider | Confirm which nameservers are authoritative for the domain | | Changing unrelated records | Restore unaffected website or email records if they were modified | ## 3. Allow for DNS propagation DNS changes are not always visible immediately. Different networks and resolvers may temporarily return different results because of caching and record time-to-live (TTL) settings. If you recently changed a record: * Confirm the new value is saved at the authoritative DNS provider. * Check whether the domain resolves from another network or device. * Avoid repeatedly changing records while waiting; doing so can make diagnosis harder. * Recheck the domain after DNS caches have had time to refresh. > [!NOTE] > > DNS propagation does not have one guaranteed completion time. A record may appear quickly in one location and take longer in another. If the authoritative record is wrong, waiting alone will not fix it. ## 4. Check HTTPS and SSL certificates HTTPS protects the connection between visitors and your AI Experience. A browser warning can indicate that the certificate is not yet available, does not match the hostname, or cannot be validated. ### If you see a certificate warning 1. Verify that the hostname in your browser is exactly the one configured in Agentsy. 2. Confirm that its DNS records point to the correct destination. 3. Check the domain's connection or verification status in Agentsy, where available. 4. Allow for certificate provisioning after a newly completed domain connection. 5. Test the HTTPS URL again in a current browser. Do not bypass a certificate warning to enter credentials or sensitive information. > [!WARNING] > > Do not instruct visitors to ignore browser security warnings. If the warning persists, investigate the certificate and domain configuration before sharing the link publicly. ### Common HTTPS symptoms | Browser behavior | Possible explanation | | - | - | | Certificate does not match the website | The certificate may not cover the requested hostname | | Secure connection cannot be established | Certificate provisioning or TLS connection issue | | HTTP works but HTTPS fails | HTTPS may not be ready for the custom domain | | HTTPS works on one hostname but not another | The second hostname may require separate configuration | Agentsy's domain infrastructure may manage certificate issuance for supported custom-domain setups. Do not assume that purchasing a separate certificate or manually uploading one is necessary unless your configuration explicitly requires it. ## 5. Check redirects and website routing Sometimes the domain resolves and HTTPS works, but visitors arrive at the wrong page. Check the following: * **Domain forwarding:** Look for forwarding rules at your domain registrar or DNS provider. * **Website redirects:** Review redirects configured on any existing website or proxy service using the hostname. * **Hostname differences:** Test the exact configured hostname, including whether you are using `www`, the root domain, or a subdomain. * **Access settings:** Check whether the AI Experience is public, private, or invite-only. * **Visitor navigation:** Test the logo, home-page link, registration flow, and chat entry point as a signed-out visitor. If a visitor clicks the AI Experience logo and unexpectedly lands on a sign-in page, the issue may be an application navigation or access-control problem rather than DNS. See [Sign-In Problems](/troubleshooting-and-support/sign-in-problems) and [Public and Private Access](/create-and-configure/public-and-private-access). ## 6. Compare the Agentsy address with the custom domain If your AI Experience has an Agentsy-provided address, test both addresses separately. | Test result | What it suggests | | - | - | | Agentsy address works; custom domain fails | Focus on custom-domain configuration, DNS, and HTTPS | | Both addresses fail | Investigate publication, access settings, or a broader service issue | | Both open, but only one redirects incorrectly | Compare hostname-specific redirects and routing | | Both open, but chat fails | See [Assistant Response Issues](/troubleshooting-and-support/assistant-response-issues) | > [!NOTE] > > This comparison is a diagnostic clue, not definitive proof of the cause. A working Agentsy address does not automatically confirm that every custom-domain setting is correct. ## 7. Test the visitor experience after a fix Once the domain loads, verify the full experience rather than stopping at the home page. * Open the exact custom-domain URL in a private or incognito browser window. * Confirm the page loads over HTTPS without security warnings. * Check the brand name, logo, and expected landing-page content. * Start a conversation or follow the guest-chat entry flow. * Verify that registration or invitation behavior matches the configured access mode. * Click the logo and navigation links to check for unexpected redirects. * Test on a mobile device or a second browser. For additional checks, see [Testing Your Assistant](/create-and-configure/testing-your-assistant) and [Mobile Experience](/branding-and-website/mobile-experience). ## 8. When to contact support If the issue continues after checking the domain, DNS, and browser behavior, prepare a concise report with: | Information | Example | | - | - | | Affected domain | `ask.example.com` | | Expected result | Opens the public AI Experience landing page | | Actual result | Browser displays a certificate mismatch warning | | First observed | Date and approximate time, including time zone | | Recent changes | Updated a DNS record or enabled a custom domain | | Reproduction steps | Open the URL in a private window and follow the redirect | | Supporting evidence | Screenshot, browser error text, relevant DNS record details | Share DNS record names and public targets when relevant, but **never share passwords, private API keys, authentication tokens, or other secrets**. For guidance on submitting a reproducible issue, see [Report a Bug](/troubleshooting-and-support/report-a-bug) or [Contact Support](/troubleshooting-and-support/contact-support). ## Domain troubleshooting checklist * [ ] I confirmed the exact domain or subdomain configured in Agentsy. * [ ] I checked the authoritative DNS provider and required record values. * [ ] I checked for conflicting records and forwarding rules. * [ ] I allowed time for DNS caches to update after any changes. * [ ] I tested HTTPS without bypassing security warnings. * [ ] I compared the custom domain with the Agentsy-provided address. * [ ] I tested visitor navigation, registration, and chat access. * [ ] I collected error details before contacting support, if needed. ## Related articles * [Custom Domains and DNS](/integrations-and-developers/custom-domains-and-dns) * [Custom Domains](/branding-and-website/custom-domains) * [Public and Private Access](/create-and-configure/public-and-private-access) * [Sign-In Problems](/troubleshooting-and-support/sign-in-problems) * [Assistant Response Issues](/troubleshooting-and-support/assistant-response-issues) * [Report a Bug](/troubleshooting-and-support/report-a-bug) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.