this post was submitted on 09 Jul 2025
39 points (61.1% liked)

Selfhosted

49434 readers
1268 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Nice big old port scan. Brand new server too. Just a few days old so there is nothing to find. Don't worry I contacted AWS. Stay safe out there.

you are viewing a single comment's thread
view the rest of the comments
[–] non_burglar@lemmy.world 28 points 4 days ago

I don't think anyone here disagrees that port scanning is bad, nor that you even filed an aws ticket. And congrats on your live service.

But your answers to comments are weird, like this is not only your first server or vps experience with a public interface, but your first time exposing anything to the public web. And even if that's true, there's a first time for everyone.

But man, doubling down and insisting that "port scanning is unauthorized traffic" betrays a certain naivete about how tcpip works.

What you are seeing is not only normal, but AWS can't do anything about it because that's how IP source and destination sockets work.