Firewalll via API at Hetzner #365
Labels
No Label
Blocked
Bug
Contributions welcome
Did not do
Errata
Feature request
Fixed
How To
Invalid
Needs design
No resolution
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Providers
Digital Ocean
Providers
Hetzner
Refactor
Severity
High
Severity
Low
Severity
Medium
Source
Community
Source
Core Team
Source
Stakeholders
Translations
Under investigation
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: SelfPrivacy/selfprivacy.org.app#365
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Description
MAybe there is a way to add a Firewall to the Server via Hetzner API? All the Ports used bei the Project could be opend, but all others coud be closed.
Context and notes
The Firewall of Hetzner is very simple in forground.
In Background it save the Server for DDoS an many other Problems. So it seams to be sensfull to activate it by default.
Belong to the sense of this Project, it should be done by create and start the server on the same way, using the API.
This would complete it a bit more.
Hetzner firewall docs: https://docs.hetzner.com/cloud/firewalls/faq
DO firewall docs: https://docs.digitalocean.com/products/networking/firewalls/
In both cases these are just firewalls, and they do not provide DDoS protection. There is also a firewall on the server itself.
Ok, it is just my expierience, that the VPS ist no too busy with the firewal outside. And it really seamed to defense a bigg attack on another VPS of mine like a DDoS. Maybe it is not mentioned in the documentation, but in fact, Hetzner defense the System ouside quite good if any firewall is active. ?
Fedback will be welcome...