Skip to main content
Answered

Hey, we use intercom for our help center and currently our help center robots.txt file gives a 502 error code (https://help.whatagraph.com/robots.txt)Any idea on how to solve this?

  • February 1, 2023
  • 2 replies
  • 288 views

Hey, we use intercom for our help center and currently our help center robots.txt file gives a 502 error code (https://help.whatagraph.com/robots.txtAny idea on how to solve this?

Best answer by Shauna

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 🔎

View original
Did this topic help you find an answer to your question?

2 replies

Shauna
Intercom Team
Forum|alt.badge.img+4
  • Intercom Team
  • 159 replies
  • Answer
  • February 3, 2023

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 🔎


  • New Participant
  • 1 reply
  • July 20, 2023

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


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings