Restoring from previous instance

Support
1

I am trying to restore from a previous instance. I have the following files backed up from the old instance: cert.pem config config.xml csrftokens.txt https-cert.pem https-key.pem index-v0.14.0.db key.pem. I am now running syncthing in a docker container. Here’s my compose file:

services: syncthing: image: syncthing/syncthing container_name: syncthing hostname: syncthing environment:

  • PUID=1000
  • PGID=1000
  • STGUIADDRESS=:8086 volumes:
  • ./syncthing-config-backup:/var/syncthing #- ./syncthing-config-backup:/var/syncthing/data network_mode: host restart: unless-stopped healthcheck: test: curl -fkLsS -m 2 127.0.0.1:8384/rest/noauth/health | grep -o --color=never OK || exit 1 interval: 1m timeout: 10s retries: 3

My backed up folder is in ~/docker/syncthing/syncthing-config-backup.

My compose file is in ~/docker/syncthing/.

Docker ps shows my instance unhealthy. Do I need to do something with port 8384? Did I configure this right? Accessing the webui, it doesn’t look like anything carried over. I am using a different IP, so not sure if that needs to be reflected somewhere….

2

If you configure syncthing’s API/GUI to listen on port 8086, you can’t then subsequently expect it to be reachable on port 8384.

1 Like
3

ok, made that change. everything else I did is correct? it doesn’t look like the interface is password protected like it was before.

4

Can anyone please assist?

5

No idea what the problem is, are you missing your config? The paths that you’re mounting look weird (why are you mounting syncthing-config-backup twice in different locations?), but due to the broken formatting it’s not really readable.

6

Here is the docker-compose file:

image
image1057×413 18.1 KB

In my docker /var/syncthing directory, I can see the following files are mounted from the host:

cert.pem config config.xml csrftokens.txt https-cert.pem https-key.pem index-v0.14.0.db key.pem

7

Can anyone please assist me?

8

You’re binding to a specific LAN address, but your test command targets 127.0.0.1. Either change your listening address also to 127.0.0.1 or switch to 0.0.0.0.

1 Like
9

Ok, thanks, I’ve updated that. I brought it down and up again. Still seeing this message, though. I know there was a password set in my previous instance.

image
image1394×536 21.1 KB

10

From inside the container, try editing /var/syncthing/config.xml.

Based on the available info, it’s not yet clear that Syncthing inside the container is using the files from your previous instance (which doesn’t sound as though it was running in a container).

(When posting content from the console and/or text files, please use the preformatted text feature in the editor to preserve formatting so it’s much easier to read for those trying to help. Screenshots of text are okay, but then it’s often not searchable by others looking for help on the same issues.)

11

I’m not sure what you’re asking me to do. I am able to view the file. Do you want me to post it here? I see devices listed in the file that were attached to my previous instance.

12

You’d mentioned earlier that you were using files saved from another Syncthing installation and also that you expected to see the web UI being password-protected, but isn’t now. Combined with it sounding like the older setup wasn’t using Docker, it’s not clear that the saved configuration files are actually being used.

So, the first step is to verify that you can view/edit Syncthing’s files under /var/syncthing inside the container instance, because if you cannot, then it would explain all of the symptoms you’re seeing.

Your YAML file has the following bind mount declaration:

volumes:
  - ./syncthing-config-backup:/var/syncthing

The relative path ./syncthing-config-backup is fine, but then you’ll have to be in the parent directory when you start the container.

13

I am able to edit that file in the docker container. Here are the files in /var/syncthing in the container:

cert.pem config.xml https-cert.pem index-v0.14.0.db config csrftokens.txt https-key.pem key.pem

I do start the container from the parent directory.