Duplicacy ignoring settings.json listening address?

Great!

I never suggested you did! On the contrary, it seems that this is such as common configuration approach, we must be missing something obvious; generally it shall “just work” and not require weeks long endeavor.

For it to work in the container, it shall be listening on 0.0.0.0. My container explicitly sets that. If you are using any other container it may not be configuring that at all, and the default is 127.0.0.1

I’m not a guru. I learn a ton of new things every day for the past quarter century, and there no end on the horizon. Amount of new stuff, the stuff I don’t know, just keeps increasing at the alarming rate. I’m far from guru, on the contrary, I feel very humbled by the vastness of the problem area and I’m conscious of limits of my knowledge.

Expecting everyone to know everything would indeed be baseless and counterproductive: and the whole point to ask for help on the forums is to address some gap in knowledge, or get a nudge to overcome the hurdle. However, it’s on you to ask for clarification as needed. I don’t know you, how am I supposed to know how much to elaborate unless you tell me? 99% of things discussed in this thread is outside of scope of duplicacy, and is all about networking, firewalls, routing, and security. I don’t mind venturing there, but again, I have no idea how much to elaborate and what you don’t understand.

There are also some expectations and forum etiquette, to not question the obvious and also not assume anything.

But I did have to ask the same question three times, did not I? Once one may overlook, but second time? I’m not enjoying that either. And I have nothing to gain.

I don’t work for duplicacy. My only relationship with the company is as customer. I’m hanging out here because I believe in the product, and there are no alternatives pretty much in terms of stability, portability, and performance. I strongly believe in volunteering for a good cause. I’m volunteering my time here to answer questions (and to clean up occasional spam and vandalism when I see it – simply because I visit here often: the shield next to my username only means I have permission to do so. In my profile however I clearly state that I’m not related to duplicacy/acrosync, so there shall be no confusion).

If you dont’ like talking to me you can always ignore my responses. I’m just another user just like yourself.

This is a user forum. Your topic received 250 views as of today. Maybe other users don’t care to chime in? Maybe questions are not interesting enough? I don’t know. But now it’s’ somehow my fault for trying to help.

I don’t know proper channels for refund. I have never went through refund process myself, so can’t draw on personal experience. Maybe email the address you received the license from? or search the forum for the words “refund”?

By the way if you want dedicated support and handholding along the way — you can buy commercial license and get email support directly from the developer.

This is because you’re trying to do something most of the rest of us don’t need, and thus aren’t experienced in.

Even @gchen (pinging the developer for multiple reasons :wink: ) may not have all the pieces to get your particular setup working, but you could take a look at here and trawl the rest of the forum. We’re not even touching on the subject of certificates, either.

However, your issue isn’t specific to Duplicacy - as saspus points out, this is about general network familiarity (complicated slightly more with a Docker environment). Even I know a fair about networking, but I also lack the precise details needed to interface things properly with nginx, although I’m certain it’s quite doable with a little persistence.

Personally speaking, expose Duplicacy’s web interface to the internet will always sound like a very bad idea to me…

This is because web server software (embedded within Duplicacy) could have myriad security vulnerabilities in the various libraries. The web interface is really just a convenient way to change settings, it’s a bonus you can access it over a network, but exposing it so widely is not advisable. This is why I’d only ever do it over a Tailscale network (and further lock down access with iptables/ifw).

It’s fine no follow up/refund needed I just want to move on really. Thanks all