[RTFACT-14081] Artifactory may not be able to connect to Xray if System default proxy is on Created: 13/Apr/17  Updated: 01/Apr/19  Resolved: 04/Sep/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: None
Affects Version/s: None
Fix Version/s: 6.4.0

Type: Bug Priority: Blocker
Reporter: Matthew Wang Assignee: Uriah Levy
Resolution: Fixed Votes: 6
Labels: None

Issue Links:
Duplicate
Relationship
is related to RTFACT-17154 jcenter search is not using a configu... Open
is related to RTFACT-17895 During Xray onboarding the Artifactor... Open

 Description   

If Artifactory is running with a default proxy, it cannot reach Xray if the proxy cannot reach the internal network Xray.

There should be some way for Artifactory to bypass the proxy to reach Xray by its own configuration.

As of now, users have to disable the default proxy. This adds more labor to them, since when they add a repo, they have to add the proxy to that repository manually instead of in the default way.



 Comments   
Comment by Prathap Subramanian [ 08/Mar/18 ]

Hi JFrog,

Would really appreciate if this issue sees some traction. Having this bug fixed in artifactory will clear a blocker toward using Xray in an official capacity at Twitter.

Thanks,
Prathap

Comment by Gintas Grigelionis [ 16/Oct/18 ]

Could you please provide some information as to where the control for disabling the global proxy is? There are no controls on /artifactory/webapp/#/admin/configuration/xray after entering a ProX license, and I'm running 6.5.0

Comment by Gintas Grigelionis [ 23/Oct/18 ]

I received an explanation from support that the control is available after Xray is integrated, but I'd rather have one before, too: a text box to provide an IP address or a DNS name. Or at least an explanation on how to disable global proxy that would save a few clicks or some head scratching.

Generated at Wed May 22 00:40:22 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.