MacOS client 2022

client
61

I have this exact issue too with both 2.4.x and the 2.5.x beta clients on different Macs.

All the other clients connect and backup flawlessly.

The mac logs give me “No result when looking up hostname “wss://<server.url>/socket”. Err: 0”

My server doesn’t have a proxy setup, and the config is the same on all computers, so this seems to be a mac only problem. The mac firewall is disabled. Is there something that i can do to troubleshoot this more ?

62

Hello,

Sorry - I don’t know what’s causing the lack of server_idents.txt or the hostname error for you - but for the record, here’s what happened when I install the 2.4.12-2 package linked at the top of this thread on an Intel system running macOS 14.5 Sonoma which has had all local Urbackup configuration data (as located in /Library/Application Support/Urbackup Client) removed (however the client remained configured on the Urbackup Server, running on the same local network):

  • I install the package - it completes without error and prompts for Full Disk Access (which it already has - I know this is an area which needs tidying up…);
  • At this point, server_idents.txt does not yet exist;
  • I entered the local client Settings screen and start entering the Internet Server settings;
  • Before I had finished entering the settings, I saw the Urbackup Client menu bar icon go yellow, and server_idents.txt had appeared - seemingly because the Client/Server local network negotiation completed independently and configured a new client entry on the server.

The Internet server name/IP I’m entering is the base hostname for the WAN connection of the server without any scheme prefix - e.g. myserver.example.com - and I’m not seeing any hostname error.

Have you tried configuring the client on the same LAN as the server, or only over the Internet?

63

Hello,
some of the problems, that are mentioned here, went away, when I changed the file
permissions of the /Library/Application Support/Urbackup Client/var/urbackup.
I allowed the wheel group full access to this directory and all files within this directory.
I did this with the finder program.
I also did this multiple times, because some files were created later on in this directory.
After changing file permissions, I also was able to use the gui to add a backup path.

I also had problems adding a client on the same LAN.
This was due to multiple network cards and multiple network IP Adresses.
The multicast or the multicast answer was sent to the wrong network addresse.

When I disabled the second network card, the communication between client and server for the initial setup went through.

I also disabled SLAAC for IPv6 on the server and only used fixed IPv6 addresses.

64

Has anyone have successfully setup the MacOS client in Sequoia?

65

Hello @eRJe

For what it’s worth, I’m using it on macOS Sequoia 15.1 (Intel) at present to backup my home folder. My Urbackup Client was already installed on macOS Sonoma before I upgraded to Sequoia, so I’m currently unaware if there are any installation-specific issues.

66

Thanks for the confirmation. Although I’m on a M1, I have more hope now to get it setup.

I’m working remote via VPN and I am not sure if this is causing extra issues. (The Mac im working on is connected via VPN to the home network where Urbackup is installed). V2.4.x seems to behave different to V2.5.x, where 2.4 would connect but fail the backup due to authentication issues and 2.5 doesn’t connect at all.

67

I’m running Urbackup Client 2.4.12, and I’m happily connecting to the server on either the local network, or via the Internet-exposed server connection.

It would be worth you setting up whilst you’re connected to the same network as the server, to minimise complications.

68

Thanks for the confirmation again.

I think I will experiment a bit more when I am back in the local network (physically). After trying 2.5.x I witnessed only strange behaviour. Also when I went back to 2.4.12.