There are some things you could do relatively easily to have more peace of mind.
With Cloudflare Tunnel you’re at least only allowing port 80/443 to hit your server already. You could consider also configuring Cloudflare to block countries outside your own to limit exposure.
You’d definitely want to have SSL configured for your site, or better yet, have it (and your other services) run behind a proxy that supports SSL.
It is also typically pretty easy to implement fail2ban so that you can limit brute force attempts to login on any of your exposed services.
I guess lastly make sure you’ve got backups elsewhere of these photos and videos.
They probably meant that through the tunnel you can get to one of these ports, because the HTTP requests are forwarded there. Should only work for HTTP(S) though
Yeah, exactly. That’s what I was trying to convey with that comment as well. The only thing necessarily exposed is whatever you’re running on the only port(s) that the tunnel uses.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
There are some things you could do relatively easily to have more peace of mind.
With Cloudflare Tunnel you’re at least only allowing port 80/443 to hit your server already. You could consider also configuring Cloudflare to block countries outside your own to limit exposure.
You’d definitely want to have SSL configured for your site, or better yet, have it (and your other services) run behind a proxy that supports SSL.
It is also typically pretty easy to implement fail2ban so that you can limit brute force attempts to login on any of your exposed services.
I guess lastly make sure you’ve got backups elsewhere of these photos and videos.
In my experienc, using cloudflare tunnel, I don’t even open 80/443. That’s the beauty of the tunnel - no open ports (except 22 for ssh).
They probably meant that through the tunnel you can get to one of these ports, because the HTTP requests are forwarded there. Should only work for HTTP(S) though
I wouldn’t even open 22 and would switch that out for a 1024+ port
Yeah, exactly. That’s what I was trying to convey with that comment as well. The only thing necessarily exposed is whatever you’re running on the only port(s) that the tunnel uses.