Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System proxy settings not set using global configuration #884

Closed
magnumchoucroute opened this issue Oct 16, 2020 · 3 comments · Fixed by #888
Closed

System proxy settings not set using global configuration #884

magnumchoucroute opened this issue Oct 16, 2020 · 3 comments · Fixed by #888
Assignees
Labels
category:bug Issue is related to a bug

Comments

@magnumchoucroute
Copy link

Describe the bug
Proxy setting define in Global Configuration is not is not take into account

plop

Work environment

  • Client OS: Win10
  • Server OS: CentOs 7
  • Browse type and version: Chrome anD Firefox
  • Cortex version: cortex-3.1.0-RC1-1
  • Cortex Analyzer/Responder name: TorProject
  • Cortex Analyzer/Responder version: 1.0

To Reproduce

  1. Set Proxy into Global Configuration
  2. Run a cortex analyzer which use online query

Error log from Cortex using TorProject analyzer
[info] o.t.c.s.ProcessJobRunnerSrv - Job Z2s7MnUBTHsOEp4HtthD: requests.exceptions.ConnectionError: HTTPSConnectionPool(host='check.torproject.org', port=443): Max retries exceeded with url: /exit-addresses (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7efee5bb40f0>: Failed to establish a new connection: [Errno 110] Connection timed out',))
[info] o.t.c.s.AuditActor - Job Z2s7MnUBTHsOEp4HtthD has be updated (JsDefined("Failure"))
[info] o.t.c.s.JobSrv - Job Z2s7MnUBTHsOEp4HtthD has finished with status Failure

Possible solutions
?

Additional context

@dadokkio
Copy link
Contributor

Hi @magnumchoucroute can you please check if proposed pull helps with the issue?

@jeromeleonard jeromeleonard linked a pull request Nov 17, 2020 that will close this issue
@jeromeleonard
Copy link
Contributor

Hello @magnumchoucroute

  • Are you running the analyzer with docker or with the process on the Cortex host ?
  • Can you confirm that with Cortex 3.1.0 that has been released recently ?
  • Did you setup the proxy in the Global configuration after have enabled the analyzer ? if yes you need either to configure the analyzer or disable en re-enable it to take proxy configuration into account.

Thank you.

@jeromeleonard jeromeleonard added the status:waiting-for-reply Waiting for reply from user label Nov 18, 2020
@jeromeleonard jeromeleonard removed the status:waiting-for-reply Waiting for reply from user label Jan 26, 2022
@jeromeleonard
Copy link
Contributor

no feedback, closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bug Issue is related to a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants