Jump to content

Google.com blocked and Issues with Nebula


jschoppert
 Share

Recommended Posts

Just an update to my own post, just got this from Julia at Malwarebytes Support "We have just pushed out the database with the fix, so update the database an make sure all is now ok."  

I have tested it with Premium and Android and it seems to have fixed the issue with *.google.com.

Jason

ud.png

Link to post
Share on other sites

1 minute ago, Ausy said:

Cant even access nebular to add exceptions, it will not load, this is terrible and brought down our whole working environment....

Ausy, I am still having the issue with Nebula even though the Premium users seem to be fixed ... you would think they (Malwarebytes) would put the businesses license holders first for the amount of money that we pay!

Jason

Link to post
Share on other sites

1 minute ago, jschoppert said:

Ausy, I am still having the issue with Nebula even though the Premium users seem to be fixed ... you would think they (Malwarebytes) would put the businesses license holders first for the amount of money that we pay!

Jason

Indeed, fingers crossed it will fixed by the morning when staff return. I've closed nebular as Im fed up looking at it whirling round. and round.....

  • Like 1
Link to post
Share on other sites

For those with Nebula issues, I had to refresh a couple times but if your patient you are able to navigate it albeit slowly. Just takes a bit of time to load at the moment. The issue is resolved with my EDR clients. Just pushed an agent update with the new DB, all is well.

Link to post
Share on other sites

It was frustrating to see the fix available for individual clients but not be able to access the Nebula dashboard for any of our clients.   It took another hour for the fix to make it out to our clients, even though we still couldn't load the Nebula dashboard.   I stopped checking after that, but another hour went by (15 minutes or so ago now) and I see Nebula is back up and running.

Just FYI, in retrospect, we could have pushed a manual update using our RMM product using the following command on the endpoint:

"C:\Program Files\Malwarebytes Endpoint Agent\UserAgent\EACmd.exe" --updateprotection

 

We didn't do that, because we didn't know about this approach until things were already starting to right themselves.   I put it in my notes in case there is a next time, though.

  • Like 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.