Very general steps: - open the required ports specified in the README on repo on new vps - copy your docker-compose.yml from that machine and adjust any traefik or caddy (I forget which proxy we were using at that time) files to point to right domains and ips - ensure you have docker, docker-compose, wireguard and wireguard-tools installed on the machine - migrate your DB, if on DO one click, you'd need to copy the netmaker.db file from the data dir in netmaker (or where it's mounted on the VPS) (while netmaker container is stopped) - copy that file into the dir your netmaker server will mount as it's data dir (see your compose) - then, ensure your domain is pointed to your new VPS in AWS - ensure your compose images for netmaker + netmaker-ui are still on v0.14.6 or look like how it looked on your DO droplet - ensure mosquitto broker is installed with correct mosquitto.conf configuration (copy mosquitto.conf into appropriate dir to be mounted from old machine) - docker-compose up -d (in dir that docker-compose.yml is) - check your dashboard to see if you can login and/or see your nodes - next step may not be necessary, but may speed up re-connecting with server* - restart your netclients (or run netclient pull), if the domains have been updated to new VPS, you should be good to go

I have not tied yet, but thank you so much for such detailed guide!

sorry to hear, it's hard to pinpoint where exactly that went wrong. did you use your own DNS records or rely on nip.io during initial install?

I gave wildcard certificate to server

if they are connecting they should be functioning.. can the nodes communicate with anyone?

Basically, nodes are raspberry pi's. They located in different places, in different networks and no one can connect.