DevOps

Update TortoiseSVN Server IP Address (Relocate Guide)

Learn how to update your TortoiseSVN client's server IP address using Relocate or `svn switch --relocate`. Fix SVN IP connection issues and troubleshoot server changes.

1 answer• 1 view

How do I update the server IP address for a TortoiseSVN client (v1.7.6 on Windows 7) when the local SVN server’s IP (on Windows 10) has changed, preventing connection?

Use TortoiseSVN’s Relocate (or the Subversion CLI svn switch --relocate) to update the saved repository URL in your working copy so the TortoiseSVN client (v1.7.6 on Windows 7) points to the new Windows 10 server IP and port. Right‑click the working‑copy root → TortoiseSVN → Relocate, paste the new URL (include :port if changed), then run an Update; if the repo on the new host has a different UUID or path, Relocate will fail and you must check the server or do a fresh checkout. Also verify the Windows 10 server service/port and firewall (or use a DNS name / static IP) to avoid repeating this.

Contents

TortoiseSVN Relocate: GUI steps to update server IP

When the repository host (IP or port) changes but it’s the same repository (same repository root/path and same UUID), use TortoiseSVN’s Relocate to rewrite the stored URL in the working copy. Why? Because the working copy remembers the repository URL — change the server and it can’t connect until the URL is updated.

Step‑by‑step (GUI, TortoiseSVN v1.7.6 on Windows 7)

  • Identify the working‑copy root folder (the top folder you originally checked out).
  • Right‑click that folder → TortoiseSVN → Relocate.
  • In the Relocate dialog, change the old URL to the new one. Example:
  • Old: http://192.168.1.10/svn/myrepo
  • New: http://192.168.1.20/svn/myrepo (or http://203.0.113.25:7001/svn/myrepo if port changed)
  • Click OK. TortoiseSVN will update the URLs stored in the working copy metadata.
  • Run Right‑click → TortoiseSVN → Update to confirm the client talks to the new server.

Notes and cautions

  • Only use Relocate when the server host/port changed but the repository is the same (same Repository UUID). If the repository on the new machine is a different repository, Relocate will not work and may corrupt expectations — do a fresh checkout instead. See the official docs for Relocate for more details: Relocating a working copy.
  • If you have absolute svn:externals pointing to the old IP, check and update them separately (Properties → svn:externals).
  • If the Relocate menu item is greyed out or the dialog reports mismatched UUIDs, stop and run the verification steps below.

Command-line: svn switch --relocate

If you prefer the command line (or you need to script many working copies), use the Subversion client:

Example (run inside the working copy or specify the path):

bash
cd C:\projects\myrepo
svn switch --relocate http://192.168.1.10/svn/myrepo http://192.168.1.20/svn/myrepo

Or a minimal form:

bash
svn switch --relocate <OLD_URL> <NEW_URL> <PATH_TO_WC>

Verify & troubleshoot connection problems

If Relocate or svn switch --relocate fails, follow these checks in order.

  1. Confirm the repository identity
  • Run svn info in the working copy (or use TortoiseSVN → Repo‑browser) to see:
  • URL
  • Repository Root
  • Repository UUID
  • If the new host serves a repository with a different UUID, you can’t just relocate — you must check out a fresh working copy from the new repository and reapply uncommitted changes.
  1. Check network reachability
  • Can you ping the new IP? (not a proof of service, but a start)
  • Try a browser to http://<new-ip>:<port>/svn/ (or the repo path). If a browser shows the repo, the service is running.
  • Test the port: telnet <new-ip> <port> (or use an equivalent port checker). If the port is blocked, the client can’t connect.
  1. Firewall / service
  • On Windows 10 server, ensure the SVN service (VisualSVN or Apache + SVN) is running and listening on the expected port.
  • Add an inbound firewall rule for the port (80/443 or custom port).
  1. Credentials and SSL
  • If you get authorization errors, clear saved credentials in TortoiseSVN (Settings → Saved Data → Clear Authentication Data) and try again so you can re-enter credentials.
  • If SSL certificate errors appear after moving to a new host, accept or permanently trust the certificate in the Repo‑browser (or update the certificate to match the server name if using DNS).
  1. Errors that mean “fresh checkout required”
  • Mismatched Repository UUID or completely different repository structure → do a fresh checkout.
  • If you had local uncommitted changes, copy them out to a safe folder (or create patches), perform a new checkout, then reapply.
  1. Externals and absolute URLs
  • Absolute external definitions (svn:externals) might still reference the old IP. Inspect parent folder properties and update externals if needed.

If you’re trying to automate or the GUI is inconvenient, the Superuser thread above shows the same CLI approach and reason why a static IP or DNS is helpful.

Server-side checklist (VisualSVN / Windows 10)

If the server IP changed, confirm server configuration so clients can reach it reliably:

  • Assign a static IP or configure DHCP reservation on the router so the Windows 10 box keeps the same address.
  • If you expose the server externally, set up NAT/port forwarding on the router and use a public static IP or dynamic DNS name.
  • If you use VisualSVN Server, check its network/port settings and authentication options; see VisualSVN Server for configuration and ports: VisualSVN Server. A walkthrough about changing port/public IP is helpful: Resolved: Tortoise SVN change port and public IP address to relocate.
  • Ensure Windows Firewall has an inbound rule for the SVN port (HTTP/HTTPS or custom).
  • Confirm the SVN service is listening: netstat -an | findstr <port> on the server.

Use a DNS name (internal or public) instead of raw IPs whenever possible — it saves you from running Relocate every time the host’s address changes.

Quick checklist and fallback

  • On the client: Right‑click working copy → TortoiseSVN → Relocate → enter new URL → Update.
  • If you prefer CLI: svn switch --relocate <OLD_URL> <NEW_URL>.
  • If Relocate fails with UUID mismatch: backup uncommitted changes, fresh checkout from new server, reapply changes.
  • On server: set static IP / DHCP reservation, open firewall port, verify service (VisualSVN/Apache) is running, and use DNS for future stability.
  • If you can’t connect at all: verify port forwarding (if remote), firewall rules, and that the server is listening on the expected port.

Sources

Conclusion

To update the TortoiseSVN server IP address for a Windows 7 client, use TortoiseSVN’s Relocate (or svn switch --relocate) to rewrite the working‑copy URL, then run an Update to confirm. If the new host serves a different repository (different UUID or path) you’ll need to check out a fresh working copy and reapply changes. Finally, reduce future pain by giving the server a static IP or DNS name and checking firewall/port settings on the Windows 10 host.

Authors
NeuroAnswers
Author
Verified by moderation
NeuroAnswers
Moderation
Update TortoiseSVN Server IP Address (Relocate Guide)