It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787

question asked: Apr 23 '12, 10:39 a.m.
question was seen: 4,571 times
last updated: Apr 23 '12, 10:39 a.m.

Related questions

FAQ - How this Forum works

Error HTTP 502 Bad Gateway

0
aurelien coueron (13●1●8●7) | asked Apr 23 '12, 10:39 a.m.
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 ?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Kim Soederhamn (1.5k●2●42●47) | answered May 01 '12, 4:51 a.m.
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.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.