-
Notifications
You must be signed in to change notification settings - Fork 8
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
Error during checking on updates #2
Comments
Hi @hattter, sorry for the slow reply, yes, should still work. Not sure what would cause that 'Unexpected error'. Have you reached out to support? Any luck? |
No, and I don't really know what questions could I ask, as the support site just works, and I can download everything there;) |
Ok i think i found the cause. This url: https://support.paloaltonetworks.com/Updates/DynamicUpdates/245 In responses with errors after logging in I had my email and empty company name, now it is correct. I think this number should be in the config file, but I don't really know what this is. It may be some variable;) If You confirm that its constant (and can name it), I can submit a fix with this option in config file. Unless You have a better solution... |
I think you’re right about the number causing the problem and needing to be in the config file. The number is your company account number. It used to simply redirect to the default company, but I guess that changed. I have tried without the number hoping it would redirect to your default company, but it doesn’t in my testing. So I propose 2 changes:
I can work on this if you like, or you can submit a fix. Up to you. Thanks for researching the problem! |
I've made a pull request with my fix, so You can use it. I think we can close this issue. |
Hi, i tried your code:
Effect is about the same without -p parameter.
After little investigation I found out, that the last requested page does not contain the pattern with data json:
"data":({"Data":.*?"Total":\d+,"AggregateResults":null})
or anyhing like it. However the response contain this:
I belive something is wrong on my end, but I don't know what... The credentials are ok, and it seems it logged in successfuly. I have noticed that You just few days age updated this script so it should work fine. Can You confirm that you can still use this script without problem?
The text was updated successfully, but these errors were encountered: