What Is My Nextcloud Server Address?

What Is My Nextcloud Server Address?

That file holds the magic URL under the overwrite.cli.url key—something like 'overwrite.cli.url' => 'https://cloud.example.com'. Want to check without digging through files? Fire up your server terminal and run sudo -u www-data php /var/www/nextcloud/occ config:list. Just remember: whatever URL you find there better match your current domain or IP, or things will break when clients try to connect.

What’s Happening

Here’s the thing: Nextcloud hardcodes that address for every single connection. Swap routers or move domains? Suddenly mobile apps and browsers can’t reach the server anymore. You’ll see errors like “server not found” or timeouts. The kicker? Nextcloud won’t update this automatically. So when connections fail, the first place to look is that stored URL.

How do I find my Nextcloud server address?

SSH into your server, then run sudo -u www-data php /var/www/nextcloud/occ config:list. Scan for lines like overwritehost => 'cloud.example.com' or overwrite.cli.url => 'https://cloud.example.com'. Those are your active connection points. Prefer raw file access? Just peek at config.php itself with sudo cat /var/www/nextcloud/config/config.php. Either way, you’ll spot the URL in seconds.

Why isn’t my Nextcloud server address updating?

Mobile apps, desktop clients, and browsers love caching URLs to speed up logins. Change the server address? Those cached values may keep sending users to the wrong place for days. DNS propagation delays don’t help either. Force an update by clearing the app cache or reinstalling the client. DNS issues? Flush the cache or drop the TTL beforehand to cut downtime.

Step-by-Step Solution

1. Connect to your Nextcloud server via SSH using an admin account:

   ssh admin@192.168.1.100

2. Jump straight to the Nextcloud config folder:

   cd /var/www/nextcloud/config

3. Double-check the current settings with the Nextcloud CLI:

   sudo -u www-data php /var/www/nextcloud/occ config:list

   Look for overwritehost and overwrite.cli.url to confirm the active server address.
4. Open config.php in nano (or your favorite editor):

   sudo nano config.php

   Update the relevant lines, for example:

   'overwritehost' => 'new.cloud.example.com',
   'overwriteprotocol' => 'https',
   'overwrite.cli.url' => 'https://new.cloud.example.com',
   

5. Save the file (Ctrl+O, Enter, Ctrl+X in nano).
6. Restart your web server to make the changes stick:
   • Apache users:

     sudo systemctl restart apache2

   • Nginx fans:

     sudo systemctl restart nginx

If This Didn’t Work

• Still stuck with DNS issues? Clear your device’s DNS cache:
  • Windows users:

    ipconfig /flushdns

  • macOS folks:

    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

  • Linux admins:

    sudo systemd-resolve --flush-caches

• Certificate warnings popping up? Toss the new certificate into your OS trust store or update it in your reverse proxy (Nginx, Traefik—whatever you’re running).
• Mobile app still throwing tantrums? Delete and reinstall it, or wipe its cache in your device’s app settings.

Prevention Tips

• Make future updates easier with environment variables in config.php:

  'overwritehost' => getenv('NEXTCLOUD_HOST'),

  That way you only change one variable instead of hunting through files.
• Backup config.php weekly—mistakes happen, and a fresh backup beats a frantic recovery.
• Turn on overwrite.cli.url so CLI tools always hit the right host without guessing.
• Drop your DNS TTL to 300 seconds 48 hours before a domain move. That cuts downtime when the switch happens.

Running a dynamic IP? Set up a dynamic DNS service like No-IP so your address stays reachable without constant manual tweaks.