Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi @puggolouie,
I’ve actually never experienced this on any linux machine so I had to do some research. This seems to be experienced when you are using nmap on Windows.
There are some bugs opened about it here - BUG
Anyway, can you confirm how exactly are you trying to scan your local environment from your droplet?
Regards, KDSys
Hello, @puggolouie
Could you please let me know what OS you’re using? There was a bug in a specific version and I would like to check this. Also what happens when you run the scan locally on your droplet?
sudo netstat -plunt
Let me know how it goes.
Regards, Alex
This is a dumb issue with how snap works. The fix is running
snap connect nmap:network-control
after installing nmap.