Selfhosted
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).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
10.x.x.x is a private range. It won't be your externally visible internet address but it might be your router's WAN address if your upstream ISP is performing a NAT for IPv4 or if you have multiple chained routers in your network. If that is your router's WAN address you likely won't be able to use port forwarding for external access.
You can find your external address by visiting ifconfig.me or from a linux shell running
curl https://ifconfig.me
My recommendation would be to start from the other direction instead. Try and get the reverse proxy working with a SSL and a test page then work on making your nextcloud instance visible. You can use a tunneled service from cloudflare or tailscale to avoid the port-forwarding and add a layer of security.