Severe INFINITE LOOP detected when using remote proxy

[Jones Michael]

Hi ZAP Team,

I have a remote zap instance in AWS in which I attempt to access locally from my laptop.  When I attempt to access the ZAP API http://IPADDRESS:8090/UI via browser I get this response:

Failed to read http://IPADDRESS:8090/UI within 20 seconds, check to see if the site is available and if so consider adjusting ZAP's read time out in the Connection options panel.

In the ZAP GUI under History tab, there is an infinite loop of requests being made (i.e. 504 Gateway Timeouts) in which the only way to stop it is by killing the zap server/instance



  
1905
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20001
  
181
  

  
false
  



  
1906
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20002
  
181
  

  
false
  



  
1907
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20001
  
181
  

  
false
  



  
1908
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20001
  
181
  

  
false
  



  
1909
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20001
  
181
  

  
false
  



  
1910
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20001
  
181
  

  
false
  



  
1911
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20002
  
181
  

  
false
  



  
1912
  
Tue Feb 07 12:56:55 EST 2017
  
GET
  
http://IPADDRESS:8090/UI
  
504
  
Gateway Timeout
  
20001
  
181
  

  
false
  



  











.

.

.

.

.

.

.

.

.

The same error message I receive in the browser is the same error message I see under ZAP GUI history response tab:

Failed to read http://IPADDRESS:8090/UI within 20 seconds, check to see if the site is available and if so consider adjusting ZAP's read time out in the Connection options panel.

I've adjusted my timeout settings as the response suggested but no luck.  My local proxy settings are using 0.0.0.0:8090 so I'm not sure for one why I can't access API/UI remotely and experiencing this.  Any idea what's going on?

[thc...@gmail.com]

Hi.

That's a known issue:
https://github.com/zaproxy/zaproxy/issues/2318

Best regards.

On 07/02/17 18:06, Jones Michael wrote:
> Hi ZAP Team,
>
> I have a remote zap instance in AWS in which I attempt to access locally
> from my laptop. When I attempt to access the ZAP
> API http://IPADDRESS:8090/UI via browser I get this response:
>

> *Failed to read http://IPADDRESS:8090/UI within 20 seconds, check to see if the site is available and if so consider adjusting ZAP's read time out in the Connection options panel.*

> *Failed to read http://IPADDRESS:8090/UI within 20 seconds, check to see if the site is available and if so consider adjusting ZAP's read time out in the Connection options panel.*

[Jones Michael]

Ahh K...tkx for sharing...any update on when there will be a fix?  I was hoping it was something I was doing from my end but looks like its a real problem

[thc...@gmail.com]

There's no exact date but will try to fix it before 2.6.0.

Best regards.

[Prakash S]

Hi, Im trying it now. and facing same issue.

Does this issue is resolved?

[thc...@gmail.com]

Yes, but you need to enable the option "Behind NAT" for ZAP to properly
detect the requests:
https://github.com/zaproxy/zap-core-help/wiki/HelpUiDialogsOptionsLocalproxy#behind-nat

Best regards.

On 24/09/18 14:31, Prakash S wrote:
> Hi, Im trying it now. and facing same issue.
> Does this issue is resolved?
>
> On Tuesday, 7 February 2017 23:36:15 UTC+5:30, Jones Michael wrote:
>>
>> Hi ZAP Team,
>>
>> I have a remote zap instance in AWS in which I attempt to access locally
>> from my laptop. When I attempt to access the ZAP API
>> http://IPADDRESS:8090/UI via browser I get this response:
>>

>> *Failed to read http://IPADDRESS:8090/UI <http://IPADDRESS:8090/UI> within 20 seconds, check to see if the site is available and if so consider adjusting ZAP's read time out in the Connection options panel.*

>> *Failed to read http://IPADDRESS:8090/UI <http://IPADDRESS:8090/UI> within 20 seconds, check to see if the site is available and if so consider adjusting ZAP's read time out in the Connection options panel.*