[v1.4.2, linux] Failing to connect to remote device

Support
1

I’m unable to connect to the remote device from the web GUI. When I set the GUI Listen Address to the IP address of the remote device, the syncthing process in my local device outputs:

[WABWF] 19:12:42 WARNING: Starting API/GUI: listen tcp 192.168.32.83:8384: bind: cannot assign requested address
[WABWF] 19:12:42 WARNING: Starting API/GUI: listen tcp 192.168.32.83:8384: bind: cannot assign requested address
[WABWF] 19:12:42 WARNING: Starting API/GUI: listen tcp 192.168.32.83:8384: bind: cannot assign requested address
[WABWF] 19:12:42 WARNING: Starting API/GUI: listen tcp 192.168.32.83:8384: bind: cannot assign requested address
[WABWF] 19:12:42 WARNING: Starting API/GUI: listen tcp 192.168.32.83:8384: bind: cannot assign requested address
[WABWF] 19:12:42 WARNING: Starting API/GUI: listen tcp 192.168.32.83:8384: bind: cannot assign requested address

I don’t see missing any steps from all the tutorials I’ve seen.

2

Ahem, you do not connect to your remote device by the web gui address. Just add it by clicking add device and its syncthing device id to your setup.

3

The OP meant he cannot connect to a remote UI.

Seems like firewall/permissions are getting in the way, as syncthing is not allowed to listen on that address

4

I can nmap to the remote device’s IP address, the host is up. However, the 8384 port is closed because of the “marathontp” service. It’s even present when syncthing is not loaded. Also, when using namap on local device’s IP address, 8384 port is also closed by the same service.

5

Ok , https://www.speedguide.net/port.php?port=8384 only mentions udp #8384 but you could try setting another port with “0.0.0.0:18384”

6

It seems some other service is already using that port, so you’ll have to change it.

7

There’s lots of confusion here. You mention the errors coming from the local device, after setting the listen address to the remote device address. Doing that makes no sense, so I think take a step back, explain what you’re trying to accomplish, and someone can give more general advice.

1 Like
8

I’m trying to access the web GUI of my remote device (a headless server) from my local device, so I set the GUI Listen Address, on my local device’s web GUI, to the remote device’s IP address which is 192.168.32.83. I fail to access 192.168.32.83:8384 through my web browser and meanwhile my local device outputs that warning I posted.

I can already access my remote device via SSH without any issue though.

9

The web ui that you are accessing is always local.

That address in that box explains what address to listen on, not what address to connect to build the UI from.

If you want from device A to access device Bs UI, on device B your ui listen address should be <0.0.0.0 or ip of B>:8483, and on device A you should use http://<ip of B>:8384 in the browser

10

I set device B’s listen address to device’s 192.162.32.83:8384 and accessed https://192.162.32.83:8384 on my browser, my folder is syncing now. Although, when I set it to 0.0.0.0:8384, my browser output “Host check error”.

Thank you.

11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.