sonofdbn Posted October 12 Share Posted October 12 Apologies in advance for this long post, but it might apply to others in a similar situation. I've been running the Linuxserver Nextcloud docker container and accessing it via DuckDNS and Swag. I recently changed ISPs and the new ISP uses CGNAT, which, in brief, as I understand it, doesn't hand out IP addresses to users in a way that works with DuckDNS. I thought this would mean that I would at least be able to access NC from my home network, but it turns out not to be the case. (I can still get to the files in the NC share, but not the NC GUI. In fact, DuckDNS seems to be very persistent, which I'm finding confusing. Let's say my DuckDNS name is NC.duckdns.org, and that's what I used to use to access the NC container. Assume my NC container has a host IP address of 192.168.1.99:100. What I find confusing is that if I now try to access the NC GUI by entering 192.168.1.99:100 in my browser, the browser goes searching for NC.duckdns.org and returns an error message saying something like NC.duckdns.org took too long to respond. (This occurs using Chrome and Firefox.) I don't know why (or how) the browser links a local IP address like 192.168.1.99:100 to NC.duckdns.org. I can understand it working the other way round because of DNS, i.e., linking the name to the IP address. The main problem now is that I sync various files and folders on my Win10 PC to NC. The NC sync client uses an account like [email protected], and now it can't connect to NC.duckdns.org. Based on some googling, it seems there's no way of editing that account. So it looks like I have to create a new account and re-create all the syncing (which looks like it will be quite tedious). But creating a new account has also not been possible. I used the NC sync client to try to add another user using the IP address as the domain; it finds the server (it tells me there's an untrusted certificate issued by LSIO) but then it requires authorisation via a browser using an NC.duckdns.org login address. So I tried briefly to kill NC.duckdns.org by stopping the DuckDNS container and removing the NC.duckdns.org entry in Duckdns and restarting Swag, but that didn't seem to change anything. Admittedly by then I was a bit impatient and perhaps didn't wait long enough for the changes to propogate. More googling showed that it might be possible to install Tailscale in the NC container, but not sure if that will fix the Win10 PC syncing problem. (I'm happily using Tailscale for other things.) I will do some more experimenting but thought I should seek some guidance on this forum. Any suggestions on how to resolve this? (I know that unRAID has great things planned with Tailscale but I need a solution now. And I did see the YouTube videos by SpaceInvader suggesting using Tailscale and a VPS, but I'd like to avoid adding another subscription expense and more complications. ) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.