this post was submitted on 22 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

504 readers
1 users here now

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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
1
Security Concerns: Exposing My Local RESTful API to the Internet via Cloudflare Tunnel – Is My Home Network at Risk? (alien.top)
submitted 1 year ago by Sheeesssshhhhhh@alien.top to c/main@selfhosted.forum
17 comments fedilink hide all child comments
 

Hello guys, I'm have little to no experience when i have to deal with networking or cybersecurity.

I recently created a backend RESTful API on my Ubuntu VM on my personal desktop and dockerized the app, connecting it to a bridge network named 'tunnel.' I also have the Cloudflare Docker hosted in the same 'tunnel' network, which allows my local RESTful API Docker to be accessible via my domain and exposed to the internet.

Can anyone help me understand if this setup poses any security risks to my home network?

If so, what should I do to help reduce the risk? I have read that firewall helps, but does a restful api container developed with golang requires it?

you are viewing a single comment's thread
view the rest of the comments
[–] kon_dev@alien.top 1 points 1 year ago

As always, it depends. If you don't require public access, just remote access, I typically recommend VPN like tailscale. If you expose it publicly, you might want to authenticate users somehow and might enforce TLS. If you feel not confident about exposing out from your network, you could consider running it on a VPS or even a PaaS like fly.io, which help a lot with security concerns, they expose tls via their load balancers, you just own the HTTP server which you package into docker.