this post was submitted on 08 Jul 2023
145 points (100.0% liked)

Selfhosted

39435 readers
2 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 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
145
How do you deal with malicious requests to your servers? (lemmy.dbzer0.com)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
79 comments fedilink hide all child comments
 

I put up a vps with nginx and the logs show dodgy requests within minutes, how do you guys deal with these?

Edit: Thanks for the tips everyone!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

Does it integrate with NPM?

[–] [email protected] 4 points 1 year ago (1 children)

Yes it does! You find everything on the site. It is very well documented.

[–] [email protected] 2 points 1 year ago (1 children)

Ok, so I spent way too much time tonight trying to figure this out, made a mess of my npm, and fixed it.

It is very well documented.

Official documentation on using crowdsec with NPM is out of date and relies on a fork that's no longer maintained. I'm trying to find any documentation on how to integrate the bouncer into the official NPM project and am really coming up empty.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

You only need the unmaintaind version (official PR is in the works: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/2677 ) if you want to bounce at the NPM level (aka: with a captcha). At the moment I am using crowdsec to parse the NPM logs (and some other logs) and bounce at the IP tables level on my VPS ( block only) and at the opnsense firewall level (also block only) at home.

[–] [email protected] 1 points 1 year ago (1 children)

I'm not sure if it's the fact that I was up at 1am trying to figure this all out or what but it wasn't clicking last night. So the NPM (nginx) integration would strictly be the captcha and I would need to bounce at the firewall to block? That makes way more sense to me now. Thanks.

[–] [email protected] 2 points 1 year ago

No problem, crowdsec is not super simple. There is a new learning platform you need to check out! Feel free to DM me when you are stuck on something.