Set up fail2ban for nginx, move IPFS gateway to proxy role #449
No reviewers
greg
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#449
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/fail2ban_nginx"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In order to deal with a DDoS on our IPFS gateway, we have set up fail2ban for nginx and moved the IPFS nginx site to the proxy role, i.e. fornax (later all LBs/hosts).
This also cleans up and refactors the recipes and roles a little bit.
There's a conflict in
Berksfile.lock, is it something you forgot to commit?It's not something I forgot, no. Must have been something merged to master since this branch was created.
abdc496999tod06f5d7723Rebased on master now, with the conflict resolved.
👍