# Hoe "veilig" is het om Discourse zelf te draaien zonder kennis van serverbeveiliging

**URL:** <https://meta.discourse.org/t/how-safe-is-running-discourse-on-your-own-without-server-security-knowledge/170527>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [18 november 2020 om 19:17 UTC](https://meta.discourse.org/t/how-safe-is-running-discourse-on-your-own-without-server-security-knowledge/170527 "2020-11-18T19:17:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [18 november 2020 om 19:45 UTC](https://meta.discourse.org/t/how-safe-is-running-discourse-on-your-own-without-server-security-knowledge/170527/3 "2020-11-18T19:45:32Z")

</div>

On the [installs that I do](https://www.literatecomputing.com/discourse-installation-packages/) I enable auto-security upgrades and automatic reboots when they are required. I don’t recommend it, but I’ve had people leave those sites running for years without doing even a single upgrade.

I’d recommend creating the droplet with an SSH key so that password logins via SSH are disabled by default or endeavoring to do that. You can also install `fail2ban`, but disabling passwords completely is a good idea.

I’d recommend following the offical install guidelines if only so you see how things work so you can do rebuilds.

---

_[View the full topic](https://meta.discourse.org/t/how-safe-is-running-discourse-on-your-own-without-server-security-knowledge/170527)._
