Hello @ramona 👋🏼
Shauna here from Support! Is your help center set up using a custom domain?
Can you check and make sure it's been set up correctly using this doc 👇🏼
https://developers.intercom.com/installing-intercom/docs/set-up-your-custom-domain/p>
If it is and you're still getting the error - it might be good to reach out to us via the messenger with a screenshot of the 'console errors' you're getting & we can have someone dig into this for you 🔎
Hello,
I landed here also from a Google Search, as if you search in your site in google with `site:your.custom.domain` you will find out your site is not indexed due the problem with robots.txt
If you are using nginx (or ingress nginx) check your logs for:
“upstream sent too big header while reading response header from upstream”
If you find that message in your logs, you need to bump, in the annotation of your ingress (default is 4k)
nginx.ingress.kubernetes.io/proxy-buffer-size: "8k"
or http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size in a vanilla nginx configuration.
That will resolve the problem with the 502 error when hitting custom.domain/robots.txt
Reply
Join the Intercom Community 🎉
Already have an account? Login
Login to the community
No account yet? Create an account
Intercom Customers and Employees
Log in with SSOEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.