How to migrate to new server?

Software TeddyCloud
1

Hello,

since I bought a new nas system I wanted migrate teddycloud from my old nas to the new one.

My old setup is proxmox with docker and portainer, my new nas is an Ugreen with the docker app installed and running.

Is there a best practice? I am not really familiar with docker itself. Or would it be easier to start from scratch?

1 Like
2

Im also interested! Coming from Proxmox with portainer too and would like to expand the volume of the docker image.

3

You could setup a new instance and copy alle the certificates to the new one (and ensure the ip/ hostname stays the same). That’s the minimal approach.

Or you migrate the whole volumes.

4

A post was split to a new topic: Move TC from Synology NAS to a Ugreen NaS

5

The IP of the new teddycloud is different, so I think I have to flash the boxes again. Since I have all the certificates it should be enough to flash the c2.der (like explained in this thread, I have the cc3200 version of the box). Or do I miss something?

6

If you have the cc3200 version you just need to change the alturl patch or do in case of a ip change only.

7

Is it enough to change the ip in pihole?

Edit: just changing the dns record in pihole to the new ip does not work, box just says code owl.
Edit2: I changed the ip of the new teddycloud server with macvlan to the old ip but I still get codeword owl.

8

Did you copy the boxes certs to teddycloud again? So you might have copied a teddycloud ca cert to teddycloud

9

Sorry for the late reply.

I uploaded the contents of the /teddycloud_certs/_data/client/00…1 from the old server to the location on my ugreen.

grafik
grafik899×380 28.6 KB

These folders are defined before deploying the container

Screenshot 2025-11-01 101432
Screenshot 2025-11-01 1014321776×460 69.5 KB

I still get the codeworde owl.

Would it be easier/possible to reflash the toniebox and kind of start from scratch?

10

i would say the server certs are also important.

Is boxine green now in Teddycloud?

Can you check if the ca.der contains boxine if you open the file?

can you post the latest docker logs when you are doing a freshnesscheck?

11

Boxine is green in teddycloud. This is the content of the ca.der of my box:

grafik
grafik481×323 65.3 KB

And this from the new server

grafik
grafik483×338 68.3 KB

Log during freshness check:

INFO |cloud_request.c:0200:web_request()| Connecting to HTTP server prod.de.tbs.toys:443…
INFO |cloud_request.c:0252:web_request()| trying IP: 18.156.186.144
INFO |cloud_request.c:0200:web_request()| Connecting to HTTP server prod.de.tbs.toys:443…
INFO |cloud_request.c:0252:web_request()| trying IP: 3.69.182.181
INFO |cloud_request.c:0486:web_request()| Response: ‘1761996643’
INFO |cloud_request.c:0486:web_request()| Response: ‘1761996644’
INFO |handler_api.c:2389:handleApiTonieboxJson()| Trying to read /teddycloud/config/tonieboxes.json with size 3022
INFO |server.c:0961:server_init()| 1 open HTTPS API connections
INFO |server.c:0961:server_init()| 0 open HTTPS API connections
INFO |server.c:0961:server_init()| 1 open HTTPS API connections
INFO |server.c:0961:server_init()| 0 open HTTPS API connections
INFO |server.c:0961:server_init()| 1 open HTTPS API connections
INFO |server.c:0961:server_init()| 0 open HTTPS API connections
INFO |server.c:0961:server_init()| 1 open HTTPS API connections
INFO |server.c:0961:server_init()| 0 open HTTPS API connections
INFO |server.c:0961:server_init()| 1 open HTTPS API connections
INFO |server.c:0961:server_init()| 0 open HTTPS API connections
INFO |server.c:0961:server_init()| 1 open HTTPS API connections
INFO |server.c:0961:server_init()| 0 open HTTPS API connections

EDIT: I copied the server certificates from the old one to the new server and now the box is recognized. I thought I had done this but apparently not.

12

so problem solved?

1 Like
13

Problem solved, yes. Thank you :slight_smile: