No offline / online browsers shown by beEF panel

[kushagra13b]

Note : I've installed Kali Linux 2020.3 on a VirtualBox and I am using hotspot as an internet connection.

My IP address for kali Linux was 10.0.2.15 ; this is how I found it

I started my beEF Framework using beef-xss and then the usual login page opened up then I went to the UI Panel.
You can refer these images for details
How I started beef
Beef Login page
This is what I got in UI panel

So, I'm using 'BETTERCAP' to inject the a JavaScript file in the target. I've created a file named as beef-hook.js. I added my Kali Linux address in the source of script tag in beef-hook.js.

I got these logs till now.

Now I just start the bettercap and execute the commands to set the target and turn on the necessary modules.

Here are the modules which started running

Here is the ipconfig report of the target(Which is my windows 10 machine) . I did set the target IP address as 192.168.56.1 .

Then I typed arp.spoof on .

Now I went to the target's browser and tried opening a website which successfully opened up but the beef didn't showed anything under the "online browsers".

HERE ARE MY LOGS

I referred this but I wasn't able to locate web_ui_all.js file -

*#1975

I've ensured that I'm using the latest version of beEF .

You can refer this LINK for my config.yaml file.

This is what I am exactly trying to do (Youtube Link)

I will highly appreciate any suggestion coming my way.!

[Ooseum]

I am also having this problem, I wish someone can help us as this is really annoying to deal with. I am also using a Ethernet cord as internet. I also have the same ip that you mentioned "10.0.2.15" in my kali.

[mrRobot0203]

same. No idea

[wheatley]

@kushagra13b, @Ooseum & @mrRobot0203 apologies for the delay in response to this issue.
are you still requiring any further assistance with this particular issue.

[wheatley]

Closing due to inactivity, please reopen if this is still an issue.

[ArloM-dev]

Your VM is using your computer as a router, in virtualbox network settings change the "Attached to:" to bridged adapter, and then use the new ip. the vm is now connected directly too your router.