Relinking Windows PC after changing Internet Provider

I recently moved to Starlink for my internet access provider and in doing so when the Starlik system came up it used different addressing assignments than the router assignments on the HughesNet system I used previously. For instance my static DHCP addressing changed from: 192.168.1.107 to 192.168.0.107.

My TP-Link LAN router changed from: 192.168.1.1 to 192.168.0.1.

When I reinitated Syncthing on my Linux PC it came right up. Its address for the Syncthing webpage is: 127.0.0.1:8384. Which I believe is what it was originally.

But on the Windows 11 PC I am unsure what it is supposed to be assigned. In the XML config file under AppData/Local/Syncthing:

 </device>
    <gui enabled="true" tls="false" debugging="false" sendBasicAuthPrompt="false">
        <address>192.168.0.130:8384</address>
        <user>ed</user>
        <password>$2a$10$O4x3wfm6yZVXsrfaEjDIFuBF.tnlfVeZhhRK18UoR.2F8Guvohxr.</password>
        <apikey>NTMhmamGi9sZn5CWGCc3ZqYCsGZChizK</apikey>
        <theme>dark</theme>
    </gui>

I changed the address assignment from 192.168.1.130:8384 to 192.168.0.130:8384. I then reinitated Syncthing but it still is not linking with the address change according to the log file:

[start] 2024/10/11 20:39:53 INFO: syncthing v1.27.12 "Gold Grasshopper" (go1.22.6 windows-amd64) builder@github.syncthing.net 2024-09-06 07:15:45 UTC
[PP65Z] 2024/10/11 20:39:53 INFO: My ID: PP65ZBX-FCPBASL-MQ3G3Q3-HVTQRQI-ZV6AQTP-ZJQHWWR-MIMYJXG-CJ75YQ7
[PP65Z] 2024/10/11 20:39:53 INFO: Hashing performance is 379.96 MB/s
[PP65Z] 2024/10/11 20:39:53 INFO: Overall send rate is unlimited, receive rate is unlimited
[PP65Z] 2024/10/11 20:39:53 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[PP65Z] 2024/10/11 20:39:53 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:53 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:53 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:53 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[PP65Z] 2024/10/11 20:39:53 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[PP65Z] 2024/10/11 20:39:53 INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
[PP65Z] 2024/10/11 20:39:53 WARNING: Failed starting API: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/11 20:39:53 INFO: Ready to synchronize "DELL Laptop Backup Files" (fd4mr-sbs6i) (receiveonly)
[PP65Z] 2024/10/11 20:39:53 INFO: Failed initial scan of sendreceive folder "Default Folder" (default)
[PP65Z] 2024/10/11 20:39:53 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[PP65Z] 2024/10/11 20:39:53 WARNING: Starting API/GUI: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/11 20:39:53 INFO: Ready to synchronize "Windows Files For Linux PC" (fr27f-nqh56) (sendonly)
[PP65Z] 2024/10/11 20:39:53 INFO: Ready to synchronize "Desktop-Laptop Sketch Transfers" (omvyj-g3ysm) (sendonly)
[PP65Z] 2024/10/11 20:39:53 INFO: Ready to synchronize "Linux Backups" (ova3z-kqvk5) (receiveonly)
[PP65Z] 2024/10/11 20:39:53 INFO: Ready to synchronize "Linux-Windows Two Way Portal" (reymq-t92ia) (sendreceive)
[PP65Z] 2024/10/11 20:39:53 INFO: TCP listener ([::]:22000) starting
[PP65Z] 2024/10/11 20:39:53 INFO: QUIC listener ([::]:22000) starting
[PP65Z] 2024/10/11 20:39:53 INFO: QUIC listener ([::]:22000) shutting down
[PP65Z] 2024/10/11 20:39:54 INFO: TCP listener ([::]:22000) shutting down
[PP65Z] 2024/10/11 20:39:54 INFO: Exiting
[start] 2024/10/11 20:39:56 INFO: syncthing v1.27.12 "Gold Grasshopper" (go1.22.6 windows-amd64) builder@github.syncthing.net 2024-09-06 07:15:45 UTC
[PP65Z] 2024/10/11 20:39:56 INFO: My ID: PP65ZBX-FCPBASL-MQ3G3Q3-HVTQRQI-ZV6AQTP-ZJQHWWR-MIMYJXG-CJ75YQ7
[PP65Z] 2024/10/11 20:39:56 INFO: Hashing performance is 380.62 MB/s
[PP65Z] 2024/10/11 20:39:56 INFO: Overall send rate is unlimited, receive rate is unlimited
[PP65Z] 2024/10/11 20:39:56 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[PP65Z] 2024/10/11 20:39:56 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:56 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:56 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:56 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[PP65Z] 2024/10/11 20:39:56 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[PP65Z] 2024/10/11 20:39:56 INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
[PP65Z] 2024/10/11 20:39:56 INFO: Ready to synchronize "DELL Laptop Backup Files" (fd4mr-sbs6i) (receiveonly)
[PP65Z] 2024/10/11 20:39:56 WARNING: Failed starting API: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/11 20:39:56 INFO: Failed initial scan of sendreceive folder "Default Folder" (default)
[PP65Z] 2024/10/11 20:39:56 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[PP65Z] 2024/10/11 20:39:56 WARNING: Starting API/GUI: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/11 20:39:56 INFO: Ready to synchronize "Windows Files For Linux PC" (fr27f-nqh56) (sendonly)
[PP65Z] 2024/10/11 20:39:56 INFO: Ready to synchronize "Desktop-Laptop Sketch Transfers" (omvyj-g3ysm) (sendonly)
[PP65Z] 2024/10/11 20:39:56 INFO: Ready to synchronize "Linux Backups" (ova3z-kqvk5) (receiveonly)
[PP65Z] 2024/10/11 20:39:56 INFO: Ready to synchronize "Linux-Windows Two Way Portal" (reymq-t92ia) (sendreceive)
[PP65Z] 2024/10/11 20:39:56 INFO: TCP listener ([::]:22000) starting
[PP65Z] 2024/10/11 20:39:56 INFO: QUIC listener ([::]:22000) starting
[PP65Z] 2024/10/11 20:39:56 INFO: QUIC listener ([::]:22000) shutting down
[PP65Z] 2024/10/11 20:39:57 INFO: TCP listener ([::]:22000) shutting down
[PP65Z] 2024/10/11 20:39:57 INFO: Exiting
[start] 2024/10/11 20:39:58 INFO: syncthing v1.27.12 "Gold Grasshopper" (go1.22.6 windows-amd64) builder@github.syncthing.net 2024-09-06 07:15:45 UTC
[PP65Z] 2024/10/11 20:39:58 INFO: My ID: PP65ZBX-FCPBASL-MQ3G3Q3-HVTQRQI-ZV6AQTP-ZJQHWWR-MIMYJXG-CJ75YQ7
[PP65Z] 2024/10/11 20:39:59 INFO: Hashing performance is 378.25 MB/s
[PP65Z] 2024/10/11 20:39:59 INFO: Overall send rate is unlimited, receive rate is unlimited
[PP65Z] 2024/10/11 20:39:59 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
[PP65Z] 2024/10/11 20:39:59 INFO: Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:59 INFO: Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:59 INFO: Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[PP65Z] 2024/10/11 20:39:59 INFO: Using discovery mechanism: IPv4 local broadcast discovery on port 21027
[PP65Z] 2024/10/11 20:39:59 INFO: Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
[PP65Z] 2024/10/11 20:39:59 INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
[PP65Z] 2024/10/11 20:39:59 WARNING: Failed starting API: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/11 20:39:59 INFO: Ready to synchronize "DELL Laptop Backup Files" (fd4mr-sbs6i) (receiveonly)
[PP65Z] 2024/10/11 20:39:59 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down
[PP65Z] 2024/10/11 20:39:59 INFO: Failed initial scan of sendreceive folder "Default Folder" (default)
[PP65Z] 2024/10/11 20:39:59 WARNING: Starting API/GUI: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/11 20:39:59 INFO: Ready to synchronize "Windows Files For Linux PC" (fr27f-nqh56) (sendonly)
[PP65Z] 2024/10/11 20:39:59 INFO: Ready to synchronize "Desktop-Laptop Sketch Transfers" (omvyj-g3ysm) (sendonly)
[PP65Z] 2024/10/11 20:39:59 INFO: Ready to synchronize "Linux Backups" (ova3z-kqvk5) (receiveonly)
[PP65Z] 2024/10/11 20:39:59 INFO: Ready to synchronize "Linux-Windows Two Way Portal" (reymq-t92ia) (sendreceive)
[PP65Z] 2024/10/11 20:39:59 INFO: TCP listener ([::]:22000) starting
[PP65Z] 2024/10/11 20:39:59 INFO: QUIC listener ([::]:22000) starting
[PP65Z] 2024/10/11 20:39:59 INFO: QUIC listener ([::]:22000) shutting down
[PP65Z] 2024/10/11 20:40:00 INFO: TCP listener ([::]:22000) shutting down
[PP65Z] 2024/10/11 20:40:00 INFO: Exiting

I am missing a link somewhere so hopefully you guys/gals can set me straight on this challenge. thnaks a lot,

Mister Ed

Option 1: Reconfigure Starlink to use your old IP range.

Option 2: Wipe your Syncthing config on the Windows machine and reconfigure.

Option 3: Change the listen IP to 0.0.0.0 or to the Device’s new IP address (see Syncthing Configuration — Syncthing documentation)

It sounds like you previously configured Syncthing to use a static IP.

What you’ve changed in the config.xml is the Web GUI address, not the address that Syncthing works with.

But now that you can reach the the WebGUI, open the Settings from the Action menu, go to the Connections tab and change “Sync Protocol Listen Addresses” to default.

You shouldn’t need to restart Syncthing.

1 Like

You can do this? How?

Delete the config file and then reinitiate syncthing and it will recreate the config file? Would just deleting syncthing an reinstalling it be just as easy?

no idea how to accomplish that…

Ok…but where do I change the other assignment?

I cannot reach anything on the Windows PC involving Syncthing at the browser level. I can see on the Linux PC browser webpage the Listen Addresses parameter and it is set to ‘default.’ If there is a particular file somewhere I need to reconfigure then I need to know where that is. Otherwise deleting syncthing and reinstalling it might get me over this hump with less difficulty.

[PP65Z] 2024/10/12 18:40:20 WARNING: Failed starting API: listen tcp 192.168.0.130:8384: bind: The requested address is not valid in its context.
[PP65Z] 2024/10/12 18:40:20 INFO: Failed initial scan of sendreceive folder "Default Folder" (default)
[PP65Z] 2024/10/12 18:40:20 INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down

I am not understanding why if Syncthing previously used: 192.168.1.130:8384 as the browesr webpage address why is changing it to: 192.168.0.130:8384 in the config file not giving it the needed updated address? Am I supposed to be acccessing the Syncthing GUI from 1 address on my LAN regardless of which device I am currently using? If so 127.0.0.1:8384 that I use on the Linux PC is not accessible from the Windows PC. I have been unable to find this address inside my router. The Starlink router is in bypass mode so this should not be related to that. ???

  1. I don’t have Starlink. I did some digging and it doesn’t seem that that it supports changing the LAN IP address, which is pretty ridiculous. That offends the network engineer in me, and I’m completely sure that if I ever get Starlink I’ll put it into Bypass Mode and use my own router.

  2. It’s slightly easier just to delete the configuration file, but rock on if you want to delete it and reinstall.

  3. From the Syncthing UI, go to Actions / Settings / Connections and change “Sync Protocol Listen Address” to “default” (as was described by @mopani). Or directly edit Syncthing’s config.xml file; look for “<listenAddress” under “” and change it to “default”.

I am currently in bypass mode as it seems to work with less issues…

So I am going to assume deleting the config file justs forces Syncthing to recreate it on the next initiation…

From the current config file on the Windows PC it seems to already be that way:

<options>
        <listenAddress>default</listenAddress>
        <globalAnnounceServer>default</globalAnnounceServer>
        <globalAnnounceEnabled>true</globalAnnounceEnabled>
        <localAnnounceEnabled>true</localAnnounceEnabled>
        <localAnnouncePort>21027</localAnnouncePort>
        <localAnnounceMCAddr>[ff12::8384]:21027</localAnnounceMCAddr>
        <maxSendKbps>0</maxSendKbps>
        <maxRecvKbps>0</maxRecvKbps>

Syncthing will create a fresh config file if it starts and there isn’t one.

If it isn’t working now, I would recommend a “do over” with a new config file or deleting Syncthing and starting over on that Device. This assuming that there aren’t other network issues.

127.0.0.1 is a special address called “loop-back”, it is for services that should only be reachable on that computer. You could call it the “self” address; the 192.168.1.130 is a routable address that is reachable from other computers.

According to the docs, the default “listen” address is the loop-back address, so you won’t be able to reach the WebGUI except on the computer Syncthing is running on. To reach it from other computers, the WebGUI address should be 0.0.0.0:8384 in the config.xml – specifying a 0 address means “whatever this computer’s address is”:

   <gui enabled="true" tls="false" debugging="false">
        <address>0.0.0.0:8384</address>
        <apikey>[random numbers</apikey>
        <theme>default</theme>
    </gui>
    <ldap></ldap>
    <options>
        <listenAddress>default</listenAddress>
  • Note that tls="true" is a safer setting, but you can leave it false while you’re getting things fixed.

If you have many folder shares configured on this computer, then its worth trying to fix the config.xml. If not, then its probably easier to shut down Syncthing, RENAME config.xml and restart Syncthing. It will create a default config – I’m not sure if it will re-use the existing cert.pem that becomes the “Device ID” (copy cert.pem and key.pem to something like certcopy.pem and keycopy.pem in case they do get re-created, so you can “undo” if you want to keep trying).

If it does re-use the existing cert.pem Device ID then the other devices will try to connect, and you can accept each device and then accept each folder share – making sure to point them to the previous directories that were shared via Syncthing.

1 Like

Solved:

Turns out it was just a matter of entering into the config file the the loopback address: 127.0.0.1:8384 at:

<gui enabled="true" tls="false" debugging="false">
        <address>127.0.0.1:8384</address>

Thanks for the help…

Mister Ed

1 Like