Jump to content

Unexpected Blockage of Web Server Ports by Malwarebytes Nebula


Recommended Posts


I recently encountered an issue with Malwarebytes Nebula on my AWS Windows EC2 instance which I use for hosting a web server. After installing Malwarebytes Nebula, my server stopped serving content to the web even though I was still able to reach the server locally via localhost.

Upon investigating, I discovered that port 80/443 traffic wasn't making it inbound to the instance.

To resolve the issue, I had to manually open the necessary ports in the firewall.  This was working before, so the ports were open prior to the installation.  I was wondering if this is an expected behavior from Malwarebytes Nebula? Is there a way to prevent this automatic closure of ports during or after installation, particularly for those essential to a web server?

Thanks for your time and assistance.

Best regards,


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
  • 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.