You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I am trying to sync my ATT&CK workbench with the ATT&CK website. It is currently hosting on a virtual machine in Azure.
When I tried to do this setup way earlier, I did not have any issue, but now when I try to run the python3 update-attack.py, I get this error "http://localhost/api/stix-bundles/?domain=enterprise-attack stix bundle download was unsuccessful"
I tried to troubleshoot the issue as to what has changed from the last time I tried this on my local virtual machine. I can make the following observations:
The version of workbench used is newer compared to the one I had worked with before.
There is a login capability for Workbench.
When I try to view the stix bundle page, I get the message Not Authorized. This message is only fixed when I login into the Workbench and then try again to view the page.
Is this a known Bug/error, please let me know. Also, the version of ATT&CK I was trying to use was the latest one (v12.1)
The text was updated successfully, but these errors were encountered:
Also, I can see that the CLI showing WorkBench messages, shows 401 for the stix bundle pull request. The screenshot is attached on the top. I am also suspecting any ports that are being blocked on the network by default.
Another thing I have noticed is the WorkBench credentials section in the site config.py file which clearly mentions that these will be used to pull STIX from workbench 1.2.0 or later. But I do not know where my credentials are.
Hi team,
So I am trying to sync my ATT&CK workbench with the ATT&CK website. It is currently hosting on a virtual machine in Azure.
When I tried to do this setup way earlier, I did not have any issue, but now when I try to run the python3 update-attack.py, I get this error "http://localhost/api/stix-bundles/?domain=enterprise-attack stix bundle download was unsuccessful"
I tried to troubleshoot the issue as to what has changed from the last time I tried this on my local virtual machine. I can make the following observations:
Is this a known Bug/error, please let me know. Also, the version of ATT&CK I was trying to use was the latest one (v12.1)
The text was updated successfully, but these errors were encountered: