Skip to main content
Solved

How to extend Gateway timeout after 600s (10 min) - HTTP Error 504

  • September 27, 2024
  • 2 replies
  • 113 views

InfFilipV
Hero (Partner)
Forum|alt.badge.img+12

Hi,

Our customer is experiencing issues with long-running online jobs, which fail after 10 minutes due to a timeout. The Network tab in DevTools shows a 504 Gateway Timeout error.

Where can we configure or extend this timeout?


 

 

Best answer by hhanse


Hi,
It’s in the techdoc:

https://docs.ifs.com/techdocs/24r1/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/#general_parameters

 

nginx.ingress.kubernetes.io/proxy-send-timeout: "{{ .Values.global.httpSendTimeout | default 600 }}"

nginx.ingress.kubernetes.io/proxy-read-timeout: "{{ .Values.global.httpReadTimeout | default 600 }}"

 

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

2 replies

Forum|alt.badge.img+10
  • Hero (Employee)
  • 175 replies
  • Answer
  • September 30, 2024


Hi,
It’s in the techdoc:

https://docs.ifs.com/techdocs/24r1/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/#general_parameters

 

nginx.ingress.kubernetes.io/proxy-send-timeout: "{{ .Values.global.httpSendTimeout | default 600 }}"

nginx.ingress.kubernetes.io/proxy-read-timeout: "{{ .Values.global.httpReadTimeout | default 600 }}"

 


Dharmendra
Hero (Employee)
Forum|alt.badge.img+6
  • Hero (Employee)
  • 46 replies
  • October 1, 2024

Reply


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