Answer from AI:
First of all, your intention in checking that option on the local server is correct; this allows clients on the local network to connect to the server on the internet as well. However, the scenario where the same client backs up to both the local server and a server on the internet at the same time is a bit delicate due to the nature of UrBackup. A client can officially belong to only one server at a time.
If a client is to back up to both the local server and the internet server, the internet server must recognize that client as an “Internet Client,” and the local server must also allow this.
Here are the steps you need to follow in order to make this scenario work smoothly:
Step 1: Internet UrBackup Server (Internet Server) Settings
The server on the internet must accept client connections coming from the outside world (your local network).
Port Forwarding (Port Forwarding / NAT): You must forward the following ports from the firewall/router device in front of the Internet server to the server:
55414 (TCP): The main communication port for Internet clients.
55413 (TCP): Web interface (optional, if you’ll be accessing it remotely).
Enable Internet Mode:
Go to Settings → Server → Internet tab in the web interface.
Check the “Enable internet mode” box.
Internet server name/IP: Enter the server’s public static IP address or Domain/DDNS name here (Example: yedek.sirketiniz.com or 85.x.x.x).
Configure the Client for the Server:
From the main screen, click the “Add Client” button.
Select the “Add new internet client/client behind NAT” option and enter the computer’s name.
The system will provide you with an “Authentication key.” Make a note of it.
Step 2: Local Server Settings
As you mentioned, the local server needs to be allowed to “blink” the client to the internet server.
Go to Settings → Server → Internet.
Enable the “Connect as internet/active client if connected to as local/passive client” option.
(This setting allows the Internet server to actively connect and communicate with the client while the client is in a passive state on the local network.)
Step 3: Client Computer Settings
Since only a single UrBackup service is running on the client computer, we must manually enter the Internet server’s credentials.
server_idents.txt Update:
For Windows: C:\Program Files\UrBackup\server_idents.txt
For Linux: /usr/local/var/urbackup/server_idents.txt
Add the internet server’s fingerprint and name to this file. (You can find this information at the bottom of the internet server’s Settings → Server section.)
Internet Server IP and Key Settings:
Open the client interface (UrBackup Client Backend) or right-click the icon in the bottom-right corner of Windows and go to Settings.
Go to the Internet tab.
Internet server name/IP: Enter it in the format urbackup://[Internet_Server_External_IP_or_Domain]:55414.
Internet server password/Auth key: Paste the key provided by the Internet server in Step 1 here.
Check the “Connect to the Internet server on the local network” option (because the machines are currently on the local network but you want them to connect to the Internet as well).
Next Checklist (Troubleshooting)
After completing all steps, you should test the following to verify if the connection has been established:
Log Check: Check the debug.log file on the client computer to see if it can access the internet server (check for the “Failed connecting to internet server…” error).
Network Test: Verify that the port is open by sending a telnet command from the client computer to the internet server’s IP address:
SSH
telnet [internet_IP_Address] 55414
UrBackup Operation Logic: While the client is backing up to the local server, it does not simultaneously back up to the internet server. It queues the task. Once the local backup is complete or paused, the internet server triggers the client, and the internet backup begins.
