Not sure if this is your issue but in Windows after moving to a service based install you need to add --no-hosted-server to the “shortcuts” that launch Duplicati otherwise the TrayIcon will launch it’s own server, which will by default be at 8200.
Off the top I’m not certain why that would have removed the trayicon, I don’t have a Linux box kicking around at the moment to play with.
In Windows the command that starts the service should not have the --no-hosted-server switch but all other shortcuts/launchers should have it. Once one of the shortcut/launchers runs (normally via startup group) the trayicon then shows up.
Personally I use an URL shortcut to http://localhost:8300/ngax/ or a bookmark in my browser to get me to the GUI.
Maybe someone else who is more familiar with Duplicati in Linux can chime in with some insight.
/etc/default/duplicati is another way to add --no-hosted-server option so TrayIcon only does that.
A question to me is whether Server will complain, but it might not matter. It probably ignores extras. Duplicati.GUI.TrayIcon.exe is the place where the option fits. Note it has trouble with GUI password.
If you want more help, the “Installing” link above should help reach some people who know Manjaro.
These conflict. First says to put the server at port 8300. Second says to not run server. Which wins?
One way to find out is to browse to port 8300. You want (I assume) only the started-at-boot Duplicati however the started-at-login TrayIcon connects to that other to provide a bit more control and status.
If you don’t need Duplicati running as root, or when you’re not logged in, then take that path instead.
It’s only predicted if you protect your GUI (e.g. using the Settings screen, or –webservice-password).
If this is nothing you made, it’s possible it’s leftover from defaults the AUR packagers have provided.
If password was picked by you, you could try giving TrayIcon --webserver-password=<password>
Have you used systemctl as specified? You can also use ps -ef | grep -i duplicati to watch.
You should have two processes as root (the start-at-boot), and two as you, which will eventually go
away if it can’t get logged in to the server due to the password problem. It will retry connects briefly.
That will not work, you need to remove the --no-hosted-server from the Duplicati.Server.exe. You should add the --no-hosted-server to any and all other shortcuts/launchers but not to the server itself.
Then the question would be why systemd isn’t doing as well. Did you test any setup directions?
You can practice on system systemd, i.e. systemctl status duplicati and journalctl -f.
If those look reasonable, then the setup directions suggest you can add --user to see that one.
The status command will also show where your unit file lives, so you can check if you edited it.
I doubt it. There’s nothing magic about 8200 that lets you in without a password if you’ve set one.
I’m not sure what the unit file looked like before you started edits. The one I know pulls options in.
/usr/bin/duplicati-server (look at the script) runs Server. /usr/bin/duplicati runs TrayIcon.
If you prefer, you can put the password there or obtain it from any more secured source that you like.
The GUI password is there to protect the GUI, not protect against local users with direct shell access.
I think you should solve systemd, but it’s your choice. Systemd experts out there, feel free to help.
Its been too long so I really don’t remember. You can also clean out Duplicati fully though and get it back to original. You just have to remove the package, then make sure the systemd config is ended and removed, and remove all left over Duplicati folders in user’s .cache, .local or whatever.
Duplicati also didn’t like to be opened from UI. I think this might be the issue here or at least related as it would act weird with duplicates with different ports that way (I’ve definitely noted that it has for me). If you want to get to the UI, try opening the browser then using a bookmark to it (initially just using the URL) eg http://localhost:8200/ngax/index.html
If the second is the cause then you can try to just reboot and see if that fixes the duplicate Duplicati’s. Adjust the port on the URL to match the one you want if not default and if set. Any previously duplicated Duplicati’s should not bring anything up when doing it that way so you need to have that port in the URL to be correct.
That’s all I’m saying on the Linux topic though. Life is a lot easier without Duplicati on Linux