Hello. I’m pretty new here. I just managed to get my Raspberry Pi setup at home to selfhost a simple website that will act as my portfolio for some art I do.

I’m using WordPress to make the content of the website, meaning it runs on Apache, MariaDB and MySQL in the background. It’s connected via port 80 since I don’t want to pay for SSL certificates to setup https. There will be no accounts or transactions happening on my website. I don’t have anything to manage my dynamic IP but I’ll figure that out later. I’ve deleted the default Pi user on the RPi.

Are there security issues I should address preemptively? I’m worried for instance that I am exposing my home network, making it easier for someone to breach into whatever is connected there.

Any tips on making sure my setup is secure?

You are viewing a single thread.
View all comments
6 points

The WordFence plugin is a must-have for security.

If you use Caddy instead of Apache then you get SSL automatically. You’ll need php-fpm as well, tho.

permalink
report
reply
1 point

What does WordFence provide that makes it a must have?

permalink
report
parent
reply
2 points

After X attempts to log in, it bans the IP address.

It will scan your wordpress files and alert you if any of them have changed in suspicious ways (hacked).

It can disable the xml-rpc endpoint which is rarely used and is a big vector for hacking.

… and a lot more but those are the main ones for me.

permalink
report
parent
reply
1 point

Sweet thanks! Will add that ASAP

permalink
report
parent
reply
0 points

Agreed on word fence.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

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!

Community stats

  • 5.2K

    Monthly active users

  • 1.8K

    Posts

  • 19K

    Comments