Open G4rb3n opened 6 years ago
Hi G4rb3n,
I created an account just to answer your question.
I had a similar issue when configuring my sandbox to be accessible via the internet. The web interface over the interface looked exactly like yours.
What I did not realise at the time, was that I was running two separate instances of cuckoo web - One locally, the other visible via the internet.
For some reason, the first instance of cuckoo web (the local one) gets all the resources, whilst the second one is left empty.
The solution, in my case, was to stop both cuckoo web instances, and then start just one cuckoo web instance.
Hi G4rb3n,
I created an account just to answer your question.
I had a similar issue when configuring my sandbox to be accessible via the internet. The web interface over the interface looked exactly like yours.
What I did not realise at the time, was that I was running two separate instances of cuckoo web - One locally, the other visible via the internet.
For some reason, the first instance of cuckoo web (the local one) gets all the resources, whilst the second one is left empty.
The solution, in my case, was to stop both cuckoo web instances, and then start just one cuckoo web instance.
Hey , Thank you so much , Do you mean that the resources was occupy by the other ? , but the same problem was occurs when I start just one cuckoo web instance .
Hi G4rb3n,
Do you mean that the resources was occupy by the other ?
Yes - This is exactly what I mean :) If you run cuckoo web twice, the first instance gets access to the resources and the second is left outside.
but the same problem was occurs when I start just one cuckoo web instance .
Double check - It can be difficult to find an anomalous cuckoo web process. I ended up restarting my host to make sure that any "hidden" cuckoo web instances had been killed. Once the host was back up, I started a single cuckoo web instance and all appeared to be fine.
If this doesn't sort the problem, I'm not sure what will :(
Hi G4rb3n,
Do you mean that the resources was occupy by the other ?
Yes - This is exactly what I mean :) If you run cuckoo web twice, the first instance gets access to the resources and the second is left outside.
but the same problem was occurs when I start just one cuckoo web instance .
Double check - It can be difficult to find an anomalous cuckoo web process. I ended up restarting my host to make sure that any "hidden" cuckoo web instances had been killed. Once the host was back up, I started a single cuckoo web instance and all appeared to be fine.
If this doesn't sort the problem, I'm not sure what will :(
I reboot my host,and run just one cuckoo web,however,it's not OK,I think it's another reason. Anyway,Thank you again.
Why I reach 127.0.0.1:8000 after cuckoo.exe and cuckoo web runserver,the web interface is empyt ?
However,It's no problem when I run cuckoo submit .