-
-
Notifications
You must be signed in to change notification settings - Fork 445
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
IntelOwl behind restrictive proxy. #257
Comments
Hey @mboaisha, this issue is not related to IntelOwl but to your infrastructure. I should close this. However check this docs and let me know: https://docs.docker.com/network/proxy/#configure-the-docker-client |
I reconfigured Docker's proxy settings and now I get SSL errors.... I added the proxy's certificate to the host machine's store and it still would not work.... edit: Here is an example from an AbuseIPDB API call: Also started getting this error. Not sure where to proceed from here. |
The message you found is related to an open issue intelowlproject/IntelOwl-ng#61, nothing to worry about. The application still works correctly. Check this to resolve the SSL certificate issue: https://stackoverflow.com/questions/20267339/docker-behind-proxy-that-changes-ssl-certificate. As said before this is not related to IntelOwl issue so I am closing this. |
Docker:
Docker version 19.03.13, build 4484c46d9d
Docker Compose:
docker-compose version 1.27.4, build 40524192
So far IntelOwl is working well, looks like I am able to use "local" analyzers i.e. yara scans but not the ones requiring external API calls i.e. Pulsedive and AbuseIPDB.
I think it's something that has to do with the containers not having the proxy settings. Here is IntelOwl failing to get results from AbuseIPDB:
Is there a way I could get the containers to "talk" with the proxy? Not sure how to edit the
docker-compose.yml
file to "save" the proxy settings.The text was updated successfully, but these errors were encountered: