-
Notifications
You must be signed in to change notification settings - Fork 102
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
urlscan Issues #211
Comments
I just checked As the error says, you have to set |
Sorry I overlooked this line.
A possible cause is a typo. |
The key has been set correctly, as it will return results if typed directly in bash. But always fails when invoked with a cronjob (though all other queries work without issue). |
This must be a environmental issue - the cronjob works locally, but not in production. |
did you ever resolve this issue, i am having the same results. Runs with no issues when run manually but i get the following error when run via cron job: 023-06-16 00:10:06.073119 �[31mE�[0m [1725259:7440 error_notification.rb:12] �[31mMihari�[0m -- Exception: �[31mMihari::ConfigurationError: Urlscan is not configured correctly�[0m |
@Canon5616 Sorry, I never got it to work. |
There are two ways to set urlscan.io API key. The first one is set it via analyzer: urlscan
query: ...
api_key: your_api_key_goes_here |
Thanks Ninoseki , adding in the api key to the yml file worked. Not sure why my cron job doesnt like the URLscan environment variable but is fine with the rest. Thanks again! |
Hi there,
Seeing some unusual behaviour where all queries using
urlscan
refuse to work (when called via cron), generating the following error:What I think is happening, is that
urlscan
the binary atusr/lib/urlscan
is being executed, rather than the the mihari module itself. I have tried this on two separate machines and am getting the same error. The API key has been set correctly, and all other queries work without issue.Oddly, running the query directly returns results as expected. I have tried a few things and struggling -- any ideas?
The text was updated successfully, but these errors were encountered: