In my clients servers I was using all these years UrBackup but I wanted to test Duplicati.
Since Latest “stable” releases does not work on 24.04, I’ve installed 2.1.0.100 Canary.
I’ve enabled it as service (sudo systemctl enable duplicati.service) but when I open in browser localhost:8200 it ask for a password that I’ve never set. Which one is the password?
Also I don’t want to use the tray Icon, since I plan to access remotely later (if possible) by adding VHOST settings in apache2 for Proxy.
Thanks in advance.
EDIT: what I did in the meantime was:
Stop Duplicati service (sudo service duplicati stop)
Start as normal/default user Duplicati via Trayicon
Set the initial password and close the Trayicon
Copy Duplicati folder from /home/myuser/.config/Duplicati to /root/.config/Duplicati
Start Duplicati service (sudo service duplicati start)
Now I can access Duplicati via web with the assigned password.
The first option makes Duplicati listen to any network request, as opposed to just listening on the loopback adapter.
The second option lets you give the hostname the browser would send. You can use * to disable the hostname check.
Edit: there is also a paid option for managing the Duplicati instances through the Duplicati console. It is not yet fully public, but you can create an account on https://app.duplicati.com and then request remote control functionality via the support button.
This way you don’t have to deal with the settings and you get full SSL/TLS protection for the requests, and your machines do not have any open ports.
Thanks for replying. When I tried to use --webservice-password= It gave me an error (and for sure is because my password contains a @ at the beginning, but like I said in my post EDIT, I’ve solved it otherway).
Now for the rest of the tips I already saw it in the Docs. Thanks!
As for the remote access I am planing to use Proxy reverse in Apache, but is not working so far. When I setup the Proxy and enter the URL, it says that is not connected and keeps trying and trying.
Since in this server I only have one domain available, what I do is to use apache settings like domain.com/myapp. As for this case, I am using domain.com/backups (so depending of the app, I use Alias or Proxy settings). My conf. for Duplicati:
AllowEncodedSlashes On
ProxyPreserveHost On
ProxyRequests off
ProxyPass /backups http://127.0.0.1:8200/
ProxyPassReverse /backups http://127.0.0.1:8200/
Note that this makes the app spread out beyond the /backups prefix, so it may clash with other applications.
I have registered an issue for fixing this:
If you prefer, you can also edit the code in webroot/ngax/scripts/services/ServerStatus.js in you local Duplicati install (around line 344) and update it to use the /backups prefix:
const w = new WebSocket(`${websocketProtocol}//${window.location.host}/backups/notifications?token=${AppService.access_token}`);
It looks correct from the browser perspective. It is calling the correct url, and this is the step before the websocket. Since you are getting a 404, the question is who is sending this?
Can you see any log messages in Apache for this? For Duplicati you can set the environment variable:
DUPLICATI_WEBSERVER_LOGGING=1
Which will then emit verbose HTTP access logs.
The specific call is for /backups/api/v1/auth/refresh and this should be mapped to http://localhost:8200/api/v1/auth/refresh, but the 404 error indicates that it is not.
EDIT: I’ve added the settings as a new VirtualHost so to use root path / and to not conflict with another apps in the same VHOST (and of course, this Vhost in another port, 8443) but I have the same error in the browser.
Also, in Browser I get this now:
index.html:31
GET https://alogys.ddns.gdnet.ar:8443/ngax/styles/%7B%7Bactive_theme%7D%7D.css net::ERR_ABORTED 404 (Not Found)
angular.js:10514
POST https://alogys.ddns.gdnet.ar:8443/api/v1/auth/refresh 403 (Forbidden)
angular.js:10514
POST https://alogys.ddns.gdnet.ar:8443/api/v1/auth/refresh 403 (Forbidden)
GET
wss://alogys.ddns.gdnet.ar:8443/notifications?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ0eXAiOiJBY2Nlc3NUb2tlbiIsInNpZCI6IndlYnNlcnZlciIsImZhbSI6IkQ2OTlEOEFFRjM5RTE3MUUiLCJuYmYiOjE3MzI3MTc5MjEsImV4cCI6MTczMjcxODgyMSwiaXNzIjoiaHR0cHM6Ly9kdXBsaWNhdGkiLCJhdWQiOiJodHRwczovL2R1cGxpY2F0aSJ9.EIbS4BKPxL01IT7OLz1TIAgRIsae8J6kf4nQ6TRNqw0
[HTTP/1.1 400 Bad Request 101ms]
Firefox no puede establecer una conexión con el servidor en wss://alogys.ddns.gdnet.ar:8443/notifications?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ0eXAiOiJBY2Nlc3NUb2tlbiIsInNpZCI6IndlYnNlcnZlciIsImZhbSI6IkQ2OTlEOEFFRjM5RTE3MUUiLCJuYmYiOjE3MzI3MTc5MjEsImV4cCI6MTczMjcxODgyMSwiaXNzIjoiaHR0cHM6Ly9kdXBsaWNhdGkiLCJhdWQiOiJodHRwczovL2R1cGxpY2F0aSJ9.EIbS4BKPxL01IT7OLz1TIAgRIsae8J6kf4nQ6TRNqw0.
)