search

beefproject / beef

The Browser Exploitation Framework Project
https://beefproject.com
9.56k stars 2.1k forks source link

Beef on kali - Unable to connect when starting beef #1718

Closed lipe-oliveira closed 1 year ago

lipe-oliveira commented 5 years ago

On terminal: [] Please wait for the BeEF service to start. [] [] You might need to refresh your browser once it opens. [] [] Web UI: http://127.0.0.1:3000/ui/panel [] Hook: [*] Example:

● beef-xss.service - beef-xss Loaded: loaded (/lib/systemd/system/beef-xss.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2019-04-24 20:18:54 -03; 4s ago Process: 11367 ExecStart=/usr/share/beef-xss/beef (code=exited, status=1/FAILURE) Main PID: 11367 (code=exited, status=1/FAILURE)

abr 24 20:18:54 behl beef[11367]: from /usr/lib/ruby/vendor_ruby/ex…d)>' abr 24 20:18:54 behl beef[11367]: from /usr/local/lib/site_ruby/2.5…ire' abr 24 20:18:54 behl beef[11367]: from /usr/lib/ruby/vendor_ruby/ug…d)>' abr 24 20:18:54 behl beef[11367]: from /usr/local/lib/site_ruby/2.5…ire' abr 24 20:18:54 behl beef[11367]: from /usr/local/lib/site_ruby/2.5…ire' abr 24 20:18:54 behl beef[11367]: from /usr/share/beef-xss/core/loa…d)>' abr 24 20:18:54 behl beef[11367]: from /usr/local/lib/site_ruby/2.5…ire' abr 24 20:18:54 behl beef[11367]: from /usr/share/beef-xss/beef:44:…in>' abr 24 20:18:54 behl systemd[1]: beef-xss.service: Main process exited, co…ILURE abr 24 20:18:54 behl systemd[1]: beef-xss.service: Failed with result 'exi…ode'. Hint: Some lines were ellipsized, use -l to show in full.

[*] Opening Web UI (http://127.0.0.1:3000/ui/panel) in: 5... 4... 3... 2... 1...

On Web UI: Unable to connect

Firefox can’t establish a connection to the server at 127.0.0.1:3000.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

I can't start beef, could anyone help me to solve this problem?

blairjames commented 5 years ago

Hey Felipe! Have you?

How are you launching beef? (dock, launcher, application's menu, cli) Try running: "systemctl stop beef-xss.service;beef-xss" If your still having issues could you please paste output from: 'systemctl restart "beef-xss.service";cat /etc/os-release;uname -a;journalctl -en 200 | grep -i "beef" '

lipe-oliveira commented 5 years ago

application's menu.

JessWill commented 4 years ago

Hi @FelipeBelchior4646 , has this been resolved for you? I will be closing this ticket in 1 week if there is no reply. Thank you!

rykainrs commented 4 years ago

So I'm having the same issue.

Unable to connect

Firefox can’t establish a connection to the server at 127.0.0.1:3000.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

beef-xss.service - beef-xss Loaded: loaded (/lib/systemd/system/beef-xss.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2019-11-09 11:13:36 UTC; 3s ago Process: 4161 ExecStart=/usr/share/beef-xss/beef (code=exited, status=1/FAILURE) Main PID: 4161 (code=exited, status=1/FAILURE)

Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/exec…cJS>' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/exec…ed)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0…uire' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/ugli…ed)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0…uire' Nov 09 11:13:36 ry beef[4161]: from /usr/share/beef-xss/core/loade…ed)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0…uire' Nov 09 11:13:36 ry beef[4161]: from /usr/share/beef-xss/beef:44:in…ain>' Nov 09 11:13:36 ry systemd[1]: beef-xss.service: Main process exited, code…ILURE Nov 09 11:13:36 ry systemd[1]: beef-xss.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full.

[*] Opening Web UI (http://127.0.0.1:3000/ui/panel) in: 5... 4... 3... 2... 1... root@ry:~/Desktop/BeeF-Over-Wan# systemctl restart "beef-xss.service";cat/etc/os-release;uname -a;journalctl -en 200 | grep -i "beef" bash: cat/etc/os-release: No such file or directory Linux ry 5.2.0-kali2-amd64 #1 SMP Debian 5.2.9-2kali1 (2019-08-22) x86_64 GNU/Linux Nov 09 11:09:16 ry systemd[1]: Started beef-xss. Nov 09 11:09:17 ry beef[4076]: /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:23:in include': wrong argument type Class (expected Module) (TypeError) Nov 09 11:09:17 ry beef[4076]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:23:inblock (2 levels) in <top (required)>' Nov 09 11:09:17 ry beef[4076]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:22:in class_eval' Nov 09 11:09:17 ry beef[4076]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:22:inblock in <top (required)>' Nov 09 11:09:17 ry beef[4076]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:21:in each' Nov 09 11:09:17 ry beef[4076]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:21:in<top (required)>' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:09:17 ry beef[4076]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8.rb:22:in<top (required)>' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:130:in require' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:130:inrescue in require' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:34:in require' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs/ruby_racer_runtime.rb:108:inavailable?' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:53:in each' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:53:infind' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:53:in best_available' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:47:inautodetect' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs.rb:5:in <module:ExecJS>' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/execjs.rb:4:in<top (required)>' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:09:17 ry beef[4076]: from /usr/lib/ruby/vendor_ruby/uglifier.rb:3:in<top (required)>' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:09:17 ry beef[4076]: from /usr/share/beef-xss/core/loader.rb:29:in<top (required)>' Nov 09 11:09:17 ry beef[4076]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:09:17 ry beef[4076]: from /usr/share/beef-xss/beef:44:in

' Nov 09 11:09:17 ry systemd[1]: beef-xss.service: Main process exited, code=exited, status=1/FAILURE Nov 09 11:09:17 ry systemd[1]: beef-xss.service: Failed with result 'exit-code'. Nov 09 11:13:35 ry systemd[1]: Started beef-xss. Nov 09 11:13:36 ry beef[4161]: /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:23:in include': wrong argument type Class (expected Module) (TypeError) Nov 09 11:13:36 ry beef[4161]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:23:inblock (2 levels) in <top (required)>' Nov 09 11:13:36 ry beef[4161]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:22:in class_eval' Nov 09 11:13:36 ry beef[4161]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:22:inblock in <top (required)>' Nov 09 11:13:36 ry beef[4161]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:21:in each' Nov 09 11:13:36 ry beef[4161]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8/conversion.rb:21:in<top (required)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:13:36 ry beef[4161]: from /var/lib/gems/2.5.0/gems/therubyracer-0.12.2/lib/v8.rb:22:in<top (required)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:130:in require' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:130:inrescue in require' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:34:in require' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs/ruby_racer_runtime.rb:108:inavailable?' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:53:in each' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:53:infind' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:53:in best_available' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs/runtimes.rb:47:inautodetect' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs.rb:5:in <module:ExecJS>' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/execjs.rb:4:in<top (required)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:13:36 ry beef[4161]: from /usr/lib/ruby/vendor_ruby/uglifier.rb:3:in<top (required)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:13:36 ry beef[4161]: from /usr/share/beef-xss/core/loader.rb:29:in<top (required)>' Nov 09 11:13:36 ry beef[4161]: from /usr/local/lib/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:54:in require' Nov 09 11:13:36 ry beef[4161]: from /usr/share/beef-xss/beef:44:in
' Nov 09 11:13:36 ry systemd[1]: beef-xss.service: Main process exited, code=exited, status=1/FAILURE Nov 09 11:13:36 ry systemd[1]: beef-xss.service: Failed with result 'exit-code'. Nov 09 11:15:18 ry systemd[1]: Started beef-xss. root@ry:~/Desktop/BeeF-Over-Wan#

Please someone help me. It really would mean a lot.

jcrew99 commented 4 years ago

@rykainrs I am having a little bit of trouble re-creating this but it seems like it might be a couple of things. Can you please confirm the beef version you are using, your ruby version and fill the rest of this out? https://github.com/beefproject/beef/blob/master/.github/ISSUE_TEMPLATE.md Were you able to use it properly before or has it never worked on that install?

jcrew99 commented 4 years ago

I am closing this due to inactivity, let me know if this happens again.

Bharat109 commented 4 years ago

beef-xss.service - beef-xss Loaded: loaded (/lib/systemd/system/beef-xss.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2020-05-08 13:20:51 IST; 4s ago Process: 120328 ExecStart=/usr/share/beef-xss/beef (code=exited, status=1/FAILURE) Main PID: 120328 (code=exited, status=1/FAILURE)

Bharat109 commented 4 years ago

Please help

krag18 commented 4 years ago

I'm having the same issue.

"beef-xss.service - beef-xss Loaded: loaded (/lib/systemd/system/beef-xss.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-05-12 01:39:16 UTC; 115ms ago Process: 1581 ExecStart=/usr/share/beef-xss/beef (code=exited, status=1/FAILURE) Main PID: 1581 (code=exited, status=1/FAILURE)"

It was active and running with no access to the site. Now it's failed as well. I've tried everything described in earlier answers to the issue.

blairjames commented 4 years ago

For an interim solution if you have docker: "docker run --rm -p 3000:3000 janes/beef"

Browse to the UI URL : http://127.0.0.1:3000/ui/panel Use the default credentials to login initially. I have tested this as working 20200513. Dockerhub: https://hub.docker.com/r/janes/beef

jcrew99 commented 4 years ago

@Bharat109, @krag18 I had a lot of trouble re-creating this error so i can try and debug it. Since its Kali's packaged version of beef its hard to tell what the issue is although it definitely seems like a dependency issue. Can any of you please describe your Kali environment or any steps that you have taken to change it? If there is a specific version that you are using that would be helpful too.

krag18 commented 4 years ago

I resolved the issue.

The package beef-xss was the issue for me. Like you said, probably some dependency issue. I purged everything and git cloned beef and installed from there.

Kali 2020.2 Linux 4.19.93-Re4son-v8l+ aarch64 GNU/Linux (ARM) Installed on a Raspberry Pi 4B.

Ruby version: ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [aarch64-linux-gnu]

Bharat109 commented 4 years ago

@jcrew99 :- I a new with linux ,so please tell me what information you want and which command should i provide.. I install beef directly via apt install beef I am using kali 2020.1 with x64 bit

jcrew99 commented 4 years ago

@Bharat109
Thats fine, it seems like its just out of the box kali on the 2020 versions. I'll do testing with the releases and see if i can find the issue/a list of ones effected. Right now can you please do as krag18 has done and remove beef-xss and git clone the repo so you can keep going with beef? You should be able to follow the installation wiki: https://github.com/beefproject/beef/wiki/Installationhttps://github.com/beefproject/beef/wiki/Installation

Otherwise if i remember correctly off the top of my head it should be 

apt-get remove beef-xss

or to get rid of everything(non-recoverable)

sudo apt-get purge beef-xss

then 

git clone https://github.com/beefproject/beef.git

and go into the repo,

for dependency's and then

to start beef. Feel free to keep going with the wiki for more information.

Bharat109 commented 4 years ago

@jcrew99 Thanks i used the above method mentioned by you .. But the main problem is my butcher link is working on my same OS , but if i send butcher URL to other OS in same VM its not working .. Network is not an issue , as both VM can ping each other .

Bharat109 commented 4 years ago

@jcrew99 Just for your information , I have used the same beef installation command and it is working fine on the 2019 Kali ... but same is having issue on 2020 Kali. apt install beef-xss.

I hope this will be helpful to you in resolving issue .

ammo-cloud commented 4 years ago

has anyone figured this out im getting failed to execute default web browser with beef-xss

bcoles commented 4 years ago

has anyone figured this out im getting failed to execute default web browser with beef-xss

failed to execute default web browser means that the browser could not be opened for some reason. Try navigating to the BeEF web interface using your web browser.

jackdwalker commented 3 years ago

@ammo-cloud @Bharat109 @krag18 - please let us know if you're still having issues and we can continue to look into it, otherwise we're going to close this off. If you do have issues, please let us know your environment information, steps to reproduce your issue, and any logs you can provide us.

Bharat109 commented 3 years ago

@jackdwalker beef working fine for me 2019 Linux. Linux 2020 still an issue.

Al0ne-collab commented 3 years ago

Hi everybody. I got an error. The beef-xss service cannot be started. I tried all of them if there were any articles on google, but none of them worked. Service improved when I switched on and off kali linux but i got the error when starting beef-xss again. I am using kali linux 2020.2 beef i was installed but I was getting the verification error, so the username and password I wrote was not correct. I could not enter the panel. I applied some code to solve this. as a result a service error occurred. welp

bcoles commented 3 years ago

Hi everybody. I got an error. The beef-xss service cannot be started. I tried all of them if there were any articles on google, but none of them worked. Service improved when I switched on and off kali linux but i got the error when starting beef-xss again. I am using kali linux 2020.2 beef i was installed but I was getting the verification error, so the username and password I wrote was not correct. I could not enter the panel. I applied some code to solve this. as a result a service error occurred. welp

beef-xss is the name of the service pacakged with distributions such as Kali, Parrot, and BackBox. Try checking the dmesg logs and journalctl -u beef-xss logs for logs related to the service.

Al0ne-collab commented 3 years ago

@Bharat109 Thats fine, it seems like its just out of the box kali on the 2020 versions. I'll do testing with the releases and see if i can find the issue/a list of ones effected. Right now can you please do as krag18 has done and remove beef-xss and git clone the repo so you can keep going with beef? You should be able to follow the installation wiki: https://github.com/beefproject/beef/wiki/Installationhttps://github.com/beefproject/beef/wiki/Installation

Otherwise if i remember correctly off the top of my head it should be

apt-get remove beef-xss

or to get rid of everything(non-recoverable)

sudo apt-get purge beef-xss

then

git clone https://github.com/beefproject/beef.git

and go into the repo,

for dependency's and then

to start beef. Feel free to keep going with the wiki for more information.

Hi everybody. I got an error. The beef-xss service cannot be started. I tried all of them if there were any articles on google, but none of them worked. Service improved when I switched on and off kali linux but i got the error when starting beef-xss again. I am using kali linux 2020.2 beef i was installed but I was getting the verification error, so the username and password I wrote was not correct. I could not enter the panel. I applied some code to solve this. as a result a service error occurred. welp

beef-xss is the name of the service pacakged with distributions such as Kali, Parrot, and BackBox. Try checking the dmesg logs and journalctl -u beef-xss logs for logs related to the service.

I did what your friend said and as a result beef-xss was deleted from kali and i cannot install beef-xss with say bundle install

bcoles commented 3 years ago

I did what your friend said and as a result beef-xss was deleted from kali and i cannot install beef-xss with say bundle install

Please don't post on closed issues. If you have an issue, create an issue. Your issue is unrelated to the original issue.

I don't know what "say bundle install" means. Some form of logs or output would be useful.

Another option is to clone BeEF from the GitHub repository:

cd $HOME
git clone https://github.com/beefproject/beef
cd beef
bundle install

Then, to run BeEF: ./beef

Note that you will not be able to use the beef-xss service if you take this approach.

Al0ne-collab commented 3 years ago

I solved my problem. by typing them: sudo apt-get remove beef-xss

then:

sudo apt-get install beef-xss

thats solved the beef-xss package problem.

Aravindha1234u commented 3 years ago

I guess you wont want to remove and install it back. I had a similar issue and How did i fix this 

cat /lib/systemd/system/beef-xss.service

Check service configuration file and you can see that User=beef-xss which wont be existing in you machine some time.

change to 

User=root
Group=root

and then systemctl daemon-reload

service beef-xss restart

That it Issue wont be fixed, I hope this will be Working and hope issue gets fixed

shayansaha85 commented 3 years ago

I changed my username and password in the config.yaml file. But after executing the command "./beef" I am getting error

21:23:02][*] Browser Exploitation Framework (BeEF) 0.5.0.0-alpha-pre [21:23:02] | Twit: @beefproject [21:23:02] | Site: https://beefproject.com [21:23:02] | Blog: http://blog.beefproject.com [21:23:02] |_ Wiki: https://github.com/beefproject/beef/wiki [21:23:02][*] Project Creator: Wade Alcorn (@WadeAlcorn) -- migration_context() Traceback (most recent call last): 9: from ./beef:171:in

' 8: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:918:in method_missing' 7: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:897:insay_with_time' 6: from /usr/lib/ruby/2.7.0/benchmark.rb:293:in measure' 5: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:897:inblock in say_with_time' 4: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:919:in block in method_missing' 3: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:912:inconnection' 2: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/connection_handling.rb:283:in connection' 1: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/connection_handling.rb:327:inretrieve_connection' /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:1125:in retrieve_connection': No connection pool for 'ActiveRecord::Base' found. (ActiveRecord::ConnectionNotEstablished)

shayansaha85 commented 3 years ago

Please help me out how to tackle this issue. Thanks in advance.

bcoles commented 3 years ago

I changed my username and password in the config.yaml file. But after executing the command "./beef" I am getting error

21:23:02][*] Browser Exploitation Framework (BeEF) 0.5.0.0-alpha-pre [21:23:02] | Twit: @beefproject [21:23:02] | Site: https://beefproject.com [21:23:02] | Blog: http://blog.beefproject.com [21:23:02] |_ Wiki: https://github.com/beefproject/beef/wiki [21:23:02][*] Project Creator: Wade Alcorn (@WadeAlcorn) -- migration_context() Traceback (most recent call last): 9: from ./beef:171:in ' 8: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:918:in method_missing' 7: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:897:insay_with_time' 6: from /usr/lib/ruby/2.7.0/benchmark.rb:293:in measure' 5: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:897:inblock in say_with_time' 4: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:919:in block in method_missing' 3: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/migration.rb:912:inconnection' 2: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/connection_handling.rb:283:in connection' 1: from /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/connection_handling.rb:327:inretrieve_connection' /var/lib/gems/2.7.0/gems/activerecord-6.1.3.2/lib/active_record/connection_adapters/abstract/connection_pool.rb:1125:in retrieve_connection': No connection pool for 'ActiveRecord::Base' found. (ActiveRecord::ConnectionNotEstablished)

@hayansaha85 This is an unrelated issue. #2093

Notepadboy commented 2 years ago

Hey it looks like i have the same error i guess because this comes every time i try to open

[i] GeoIP database is missing [i] Run geoipupdate to download / update Maxmind GeoIP database [] Please wait for the BeEF service to start. [] [] You might need to refresh your browser once it opens. [] [] Web UI: http://127.0.0.1:3000/ui/panel [] Hook: [*] Example:

● beef-xss.service - beef-xss Loaded: loaded (/lib/systemd/system/beef-xss.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2021-09-30 14:13:35 EDT; 3s ago Process: 4369 ExecStart=/usr/share/beef-xss/beef (code=exited, status=1/FAILURE) Main PID: 4369 (code=exited, status=1/FAILURE) CPU: 1.695s

Sep 30 14:13:35 kali beef[4369]: [14:13:34][] Browser Exploitation Framework (BeEF) 0.5.0.0 Sep 30 14:13:35 kali beef[4369]: [14:13:34] | Twit: @beefproject Sep 30 14:13:35 kali beef[4369]: [14:13:34] | Site: https://beefproject.com Sep 30 14:13:35 kali beef[4369]: [14:13:34] | Blog: http://blog.beefproject.com Sep 30 14:13:35 kali beef[4369]: [14:13:34] |_ Wiki: https://github.com/beefproject/beef/wiki Sep 30 14:13:35 kali beef[4369]: [14:13:34][] Project Creator: Wade Alcorn (@WadeAlcorn) Sep 30 14:13:35 kali beef[4369]: -- migration_context() Sep 30 14:13:35 kali systemd[1]: beef-xss.service: Main process exited, code=exited, status=1/FAILURE Sep 30 14:13:35 kali systemd[1]: beef-xss.service: Failed with result 'exit-code'. Sep 30 14:13:35 kali systemd[1]: beef-xss.service: Consumed 1.695s CPU time.

[*] Opening Web UI (http://127.0.0.1:3000/ui/panel) in: 5... 4... 3... 2... 1...

iamtheef commented 2 years ago

Seems like the server is starting normally when I do ./beef but then the UI page is unreachable. Any ideas?

bcoles commented 2 years ago

Seems like the server is starting normally when I do ./beef but then the UI page is unreachable. Any ideas?

What does "unreachable" mean? You can view what process is listening on a port with lsof.

lsof -i :3000

You can check if a port is open with nmap or netcat:

nmap -p 3000 127.0.0.1
nc 127.0.0.1 3000
iamtheef commented 2 years ago

@bcoles Thanks for the quick response! Seems like the port 3000 is open and the beef server runs ok but when I try to visit the UI page it times out. Edit: checked the port for overlapping processes, and there is no sign of that.

bcoles commented 2 years ago

@bcoles Thanks for the quick response! Seems like the port 3000 is open and the beef server runs ok but when I try to visit the UI page it times out.

That is an unusual issue.

Is it accessible from local host?

curl http://127.0.0.1:3000/ui/panel

Is there any output in terminal?

iamtheef commented 2 years ago

Nope. No output with curl call either.

bcoles commented 2 years ago

Nope. No output with curl call either.

That is exceptionally unusual. Please create a new issue and complete the issue template.

iamtheef commented 2 years ago

That is exceptionally unusual. Please create a new issue and complete the issue template.

Will do! Thanks @bcoles

Nekroz-Tech commented 2 years ago

Hey @blairjames I am having the same problem, when I start beef, my browser is unable to conect. This happens after I change the password on config.yaml even after reinstall, it continues to do the same problem, do you know how to fix it? It could help me a lot!

wandas1212 commented 1 year ago

Hey @blairjames I am having the same problem, when I start beef, my browser is unable to conect. This happens after I change the password on config.yaml even after reinstall, it continues to do the same problem, do you know how to fix it? It could help me a lot!

have you been able to fix it??? i am facing same problem here for couple of days now but still not able to fix it, can you help me out?? i am working on a project and really need that, i am trying to Automate a script to automatically hack all networks on a network, everything is working fine but this is really giving me lots of problems, you can also contact me on @wandas1212 on telegram if you interested in the project or want to share any good thing with me, wandasheets1212@gmail.com is also my email.

sayedarman commented 1 year ago

┌──(root㉿DESKTOP-V2GM15G)-[~] └─# sudo beef-xss -h [i] GeoIP database is missing [i] Run geoipupdate to download / update Maxmind GeoIP database [] Please wait for the BeEF service to start. [] [] You might need to refresh your browser once it opens. [] [] Web UI: http://127.0.0.1:3000/ui/panel [] Hook: [*] Example:

Failed to connect to bus: Connection refused Failed to connect to bus: Connection refused

[*] Opening Web UI (http://127.0.0.1:3000/ui/panel) in: 5... 4... 3... 2... 1...

bcoles commented 1 year ago

2486