New update looks to be broken about attack-navigator HOT 4 CLOSED

Hi @JimmyAstle - thanks for bringing this to our attention. The Navigator should be available now, but I'm not convinced that the issue is fully patched. I'm going to leave this issue open until we're positive the issue is resolved.

Thanks again!

from attack-navigator.

@jburns12
Just tried this with the update and I think I am getting a different error:

vendor.3d20af49696ada3796ea.bundle.js:1 ERROR Error: fetch error: connection timeout
    at fetchTimeout.then.catch.e (main.5f1dd1c9fee06079d0b5.bundle.js:1)
    at t.invoke (polyfills.eda932d1fd6342a9adeb.bundle.js:1)
    at Object.onInvoke (vendor.3d20af49696ada3796ea.bundle.js:1)
    at t.invoke (polyfills.eda932d1fd6342a9adeb.bundle.js:1)
    at n.run (polyfills.eda932d1fd6342a9adeb.bundle.js:1)
    at polyfills.eda932d1fd6342a9adeb.bundle.js:1
    at t.invokeTask (polyfills.eda932d1fd6342a9adeb.bundle.js:1)
    at Object.onInvokeTask (vendor.3d20af49696ada3796ea.bundle.js:1)
    at t.invokeTask (polyfills.eda932d1fd6342a9adeb.bundle.js:1)
    at n.runTask (polyfills.eda932d1fd6342a9adeb.bundle.js:1)

from attack-navigator.

Thanks @dm-mitre...I'll check this out.

from attack-navigator.

It looks like the issue was a docker memory error on the TAXII server side. Although fixing that seems to have removed the problem, the Navigator is currently running off of static STIX/json until we have more time to debug and make sure this doesn't occur again.

Thank you both for your help!

from attack-navigator.