Error HTTP 502 Bad Gateway
Accessing RTC 3.0.1 behind a reverse proxy, some request fails with message "HTTP 502 Bad Gateway".
These failures happen with requests that takes a long time, like the SCM component history or big workspace load.
It looks like a request timeout, but I don't know if the timeout is in the reverse proxy or in the RTC server.
The request timeout of the RP has been modified (30s => 60s) but the problem still occur.
Anyone can help ?
These failures happen with requests that takes a long time, like the SCM component history or big workspace load.
It looks like a request timeout, but I don't know if the timeout is in the reverse proxy or in the RTC server.
The request timeout of the RP has been modified (30s => 60s) but the problem still occur.
Anyone can help ?
One answer
Accessing RTC 3.0.1 behind a reverse proxy, some request fails with message "HTTP 502 Bad Gateway".
These failures happen with requests that takes a long time, like the SCM component history or big workspace load.
It looks like a request timeout, but I don't know if the timeout is in the reverse proxy or in the RTC server.
The request timeout of the RP has been modified (30s => 60s) but the problem still occur.
Anyone can help ?
To start with you can investigate if its a general problem or a problem spcific with your proxy by changing the hotst file in windows/system32/etc and map the name directly to the IP of your RTC server to circumvent the DNS change with the proxy. Then you will at least be one step closer to the source of the problem.