Duplicacy ignoring settings.json listening address?

Support
#1

Hi, I’ve been looking for an answer to this around the forums but found nothing on my own. This is my current settings.json

{
    "listening_address": "0.0.0.0:3875"
}

And yet duplicacy is still listening on 127.0.0.1:

txgr@txgr-compute:~$ sudo netstat -tulpn | grep duplicacy
tcp        0      0 127.0.0.1:3875          0.0.0.0:*               LISTEN      801/duplicacy-web

No matter how I try and start the program it just doesn’t seem to be working.

#2

Maybe there’s just something I’m not understanding about this/this command/Linux networking to begin with. Regardless I’m still pretty stuck.

#3

So you killall duplicacy_web processes, then change settings.json under $HOME/.duplicacy_web/, which depending on how you launch it can be in different places, then start duplicacy process, and verify in the duplicacy_web.log that is successfully parsed the json file?

#4

Well I checked that file and this is about the only thing that looks off:

2025/05/03 04:26:49 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: exec: "dbus-launch": executable file not found in $PATH

But is this even related?

#5

It’s not related.

Can you confirm the rest?

  • that you kill duplciacy process
  • that you are making change in the file at the location duplicacy expects it?

Actually, lets do a simpler check – go to WebUI Settings, and check what’s written in “HTTP address” in “Start up options”:

If you don’t see this:
image

then you are not making changes in the correct file or not restarting duplicacy process.

Also, any reason why can’t you change that in the WebUI?

#6

I can’t access the WebUI- that’s mainly been my issue. I figured maybe it’s some sorta reverse proxy issue but I guess starting from being able to even access it with the IP/port directly would be a start. I can access some of my docker stuff through the port but just not Duplicacy

Here’s the service status:

May 03 04:26:49 txgr-compute systemd[1]: Started duplicacy.service - Duplicacy backup software`.
May 03 04:26:49 txgr-compute duplicacy-web[801]: Duplicacy Web Edition 1.8.0 (B47138)
May 03 04:26:49 txgr-compute duplicacy-web[801]: Starting the web server at http://127.0.0.1:3875

But going to our server’s IP:3875 won’t connect. No clue why-- but maybe that’s the more important issue isn’t it :thinking:

#7

I’m very confused. Are you running duplicaly in the docker?

Then what is duplicacy.service? Can you post content of the service file? Do you have HOME variable defined there? Because that’s where the .duplicacy_web will live.

Pleased answer these questions. I’m asking the third time. There is no reason to withhold this information.

It’s obviously listening on 127.0.0.1. Your changes in the settings file don’t have effect. Answering the questions above will help to understand why.

Because it’s listening on loopback. Not on any of the external interfaces.

You can use SSH port tunneling to access web ui to change settings. Run this in terminal on your local machine (you might need to set AllowTcpForwarding to yes in /etc/ssh/sshd_config on the server and restart sshd first)

 ssh -L 3875:127.0.0.1:3875 txgr-compute

then click here to access duplicacy: http://localhost:3875

#8

Wasn’t withholding, and really really really dislike the implication that I was. I had a train of thought and ran with it. Genuinely don’t like this at all. Phrasing this humanely just to let you know.

Restarted the entire server. Didnt’ killall but did kill all processes with duplicacy in it’s name. Checked the service afterwords too. Wasn’t running.

Don’t know where “Duplicacy expects it”.

1 Like
#9

Working on doing this now.

#10

Here:

I can rephrase.

It will be looking at $HOME/.duplicacy_web, wherever $HOME is pointing at the time of launch. If this is systemd service then HOME is likely undefined. You would need to define it explicitly. Hence, request to see your .service file.

#11

Well, I’m just a user like yourself, and I’m volunteering my time on Sunday evening making an attempt at helping you solve your issue. I feel you came here to get the problem resolved, not to exchange pleasantries: If I come out curt or/and direct – I apologize, that was not my intention. On topic – I don’t see any other reason why would you ignore my question two times – if it wasn’t important, I would not be asking. Why would I want to waste your or my time? But I digress, back on topic.