"Failed to resolve remote server" persists even though it shouldn't in Seadrive

Seafile Client
1

Hello,

a few days ago, I’ve updated the SeaDrive client to version 3.0.15 on macOS 15.5 (Sequoia).
Everything was working fine (green checkmark in the menu bar icon) until the notebook entered standby and lost its network connection.

When the computer came back online, the message “Failed to resolve remote server” appeared in the icon’s dropdown menu, and the icon now shows an exclamation mark.

However, the notebook is definitely online and the client seems to be working correctly — but the warning/error remains. I’ve tried restarting the client and even rebooting the computer, but I can’t get rid of the exclamation mark.

Am I missing something or doing something wrong? Could this be a bug? (I’ve never seen such behavior in previous versions.)

By the way, would it be possible to display a green checkmark and/or a red exclamation mark on the SeaDrive icon in macOS, similar to how it works on other platforms?

Thanks in advance for any advice or suggestions!

Best regards,
Roberto.

2

Hello @RobertoPassuello ,

The “Failed to resolve remote server” error will be automatically resolved by SeaDrive once the network is restored. If the exclamation mark remains, it may be due to a sync error. After you check the sync error, the exclamation mark should disappear.

3

Hello @feiniks ,
thank you for your quick answer.

I’ve performed a quick “regression” test as the logs and the “Show file sync errors” menu item show no error at all.
I’ve uninstalled version 3.0.15 and installed 3.0.14.

The error doesn’t show and the OK checkmark (not green as there are no colors in macOS icon) is displayed on the icon.
I’ve disconnected the computer from the network and the exclamation mark appears correctly. After activating the network again, the OK checkmark is shown again on the icon in a few seconds.

However, after reinstalling version 3.0.15, the exclamation mark persists. As mentioned, the logs report no sync errors or anything unusual.

Is there anywhere else I could look for more detailed information that might help with debugging this issue?

Thanks in advance for any suggestions.
Best,
Roberto.

4

Hello @RobertoPassuello ，

This issue was likely caused by version 3.0.15 persisting sync errors. We will improve the handling of network errors in the next release.

1 Like
5

Hello @feiniks ,
does this mean the issue is an unintended consequence of the first ChangeLog entry for version 3.0.15?
Best,
Roberto

6

Hello @RobertoPassuello ,

Yes , I think so.

1 Like