I am working on to map the ip adresss to a domain where i can manage the urback…
i have 10 clients running online and taking backups
Accidentally i have changed the
“Server URL clients connect to:” to some other ip
then all of the clients becomes offline…i revised the step to
Server URL clients connect to:urbackup://ip:55414
i restarted all the clients but could not bring up to online…
I would assume that the new incorrect IP was propagated to all the clients. Now they are looking for a urbackup server at the incorrect IP. I don’t think (happy to be proven wrong) urbackup has a “test these settings” option inbuilt, so I would presume you need to manually adjust all the clients to the right IP address.
Check that your client file (Windows) called settings.cfg stored in C:\Program Files\UrBackup\urbackup\data\settings.cfg has the right IP (this is why I use a FQDN like bk01.company.au).
But try look here /usr/local/var/urbackup/data/settings.cfg or if you have mlocate installed do a:
$ sudo updatedb
$ sudo locate settings.cfg
Which should tell you where it is.
Definitely restart the service. I did have a random issue once with Windows client where only a full system restart of the client brought it back online. Haven’t had the issue again however.
@telx thanks for your help and info…it is very helpful
I have tried with multiple combinations its was online for sometime and it goes to offile…
i Tried and tried for 3hrs and i got the issue i am have configured the client server at 55414 instead of 55415 in the settings…
i changed the port in the internet settings everything wents normal
Can you access the UrBackup website from the internet already? If you are on a different network to the server can you enter http://123.123.123.123:55414? The best thing you can do is read through the server manual. Lots of good info here.
The FQDN is first set up using your DNS management on your domain.
You need to have a domain = example.com
Add an A record to the domain dns management for something like bkup.example.com = 123.123.123.123 (whatever your public IP is)
My helpful hints:
you do not need to use FQDN. It just makes things easier for clients and for changing server IP’s. But it does take more config.
do not open things up to the world without knowing how to secure them. At the very least using certificates to enable https. The server administration manual has advice on how to do that.
there are many ways to implement things. Figure out what you want. Then go looking. If you don’t know what you want, then research and read. It takes time to do this but it is worth it.