Make your NextCloud server accessible via the internet.
Make your NextCloud server accessible via the internet.
Hello everyone, I'm evaluating different ways to connect my NextCloud instance to the WAN. Right now it's limited to a LAN network. The goal is to share large files across the wider network. So far I've looked into several options:
- Using NGROK as a proxy server to forward packets – this would require the free tier which caps outbound data at 1GB, making it unsuitable.
- Switching to paid plans; however, paying might push me toward using OneDrive instead.
- Opening ports on the router and assigning a domain – my ISP doesn’t provide static IP addresses, and buying a dedicated IP could be costly.
- Setting up my own VPN network – this would likely deter clients who prefer direct downloads.
- Trying an alternative like https://theboroer.github.io/localtunnel-www/ – I’m unsure about its performance limits and potential throttling with many connections.
Any better alternatives? Maybe replacing NGROK with a different tunneling solution?
I manage domains and reverse proxies. My IP stays consistent most of the time, though I have an auto-updater for rare changes. You can obtain free domains, but a recognizable name is better for clients—prices around $10 to $20 per year.
You noted most ISPs don’t offer static IPs, right? Is there really no way to afford it? This usually means bypassing CGNAT. That leads me to CGNAT—are you using it? If not, as @Kilrah mentioned, you could set up a domain or reverse proxy for free, or pay a modest fee for a domain around ten dollars a year. The only alternative is risking downtime when your IP changes, which can happen frequently.
You can verify your connection status by testing at the network site. Upgrading to a static IP is an option, but cloud storage may offer better value than changing your internet plan. If you need to adjust the IP through the domain console, follow the instructions there. If you're unable to update it yourself, expect manual intervention from support.
You highlighted an important point about clients and residential use. Review your ISP’s terms carefully to see if hosting big files for paying customers is permitted. If this aligns with your expectations, you might need to switch to a paid service tier or a different plan. This could be the reason self-hosting isn’t viable.
Automated of course. If you will be buying a domain then it would be best to buy it from someone who allows you to edit DNS records via API. For example Porkbun: https://porkbun.com/api/json/v3/documentation https://kb.porkbun.com/article/190-getti...orkbun-api Some give you simple URL and query paramter for updates, like freends (afraid.org): curl https://sync.afraid.org/u/your-token/ Which you then pluck into a bash script and run it every x minutes using cron or systemd, or on windows using powershell and task scheduler. Their server detects the public IP from where the request came from. Some providers have a bit more elaborate scripts, but it boils down: check your current public IP, does it match the existing recored, no -> send update via http request. The 5 minutes or so of downtime I mentioned earlier doesn't come from how often you check what is your current public IP, but that is typically how long it takes for the new DNS record to propagate (it can be even quicker, rarely it takes longer). @Echothedolpin has a valid point. If you will be serving paying clients you could very well be in breach of ToS with your ISP. If you are, then I'd consider some cheap VPS high storage solution, check out: https://lowendbox.com/tag/highstorage/ (not affiliated, I've been renting cheap VPS boxes for a long time and that is the 1st site I check when I need a new one). All that being said, if you have a handfull of clients and they aren't constantly downloading huge files from you... I doubt your ISP would notice or care about it, but you should read that ToS before proceeding.