November 17, 20205 yr Hey all, so I'll start off by saying that if there is a better place to get an answer for this, please let me know and I'll post there. This is a Duplicacy container. There's not a specific support thread, and the general template thread serves so many varying situations it's challenging to identify real trends. I've had the Duplicacy containers running on my 2 Unraid servers for several weeks. Uptime for both is 20+ days, and that goes back to some manual reboots on my part. Both servers have been running great in the bridge I created for their VLAN. Today I was on the dashboard and noticed Unraid1's Duplicacy container was stopped. Weird, as I didn't stop it. All others running fine. Unraid2 is just great. I tried starting it and it stopped immediately. Here's what the log reports: Can't start the web server: listen tcp 192.168.60.200:443: bind: cannot assign requested address There's nothing else on that custom bridge and no conflict showing. Just to test, I tried changing IP, no go. I tried changing network to host, bridge, etc. All complete fine but it fails to start. I've not touched anything on my Unraid server. EDIT: I realized it might be worth noting that I have port 3875 on this as the container port. Same as the other one, and it's been that way from the beginning, so I'm not sure why it is referencing 443 off the top of my head, either. EDIT2: I compared the settings.json file on my other Duplicacy instance and I noted that it did not have entries for https and domain as this one did. Even though the templates looked basically identical, there were differences here in the settings.json. I edited those lines out and I was able to recover my instance so both are working now. Edited November 17, 20205 yr by BurntOC
Archived
This topic is now archived and is closed to further replies.