"Move" Pterodactyl node from one panel to another
I use Pterodactyl to admin a small server network. I am currently in the process of migrating VPS', primarily to split the panel and the nodes onto separate servers. This is why a 1 to 1 file transfer is not an option.
I installed the Pterodactyl panel on a new server. Now I want to add an existing node (currently on the old VPS and connected to the old panel) to the new panel (on the new VPS), which worked. The problem: the new panel doesn't see the existing servers on that node. Any ideas?
6 Replies
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by chaoticducc#0
You will need to copy the
pterodactyl database from the old panel to the new panel
And ensure you have also copied the /var/www/pterodactyl/.env file from your old setup to the new one
You could alternatively only copy the servers table, but you would have to fix all the, node, allocations, nest, fields for each server manually.What would be the best way to approach that? I don't have a lot of experience with SQL.
If you want it to be as easy as possible, probably just sqldump of the old pterodactyl database
And then running that .sql file on the new database (after clearing out what is already there)
Can also use tools like HeidiSQL which is a more visual way of doing it
But requires you to do SSH tunneling, or have SQL exposed publicly on the internet
Use tailscale and secure copy the sql dump files from one server to another, then migrate the databases with the new ones you create
Honestly if you don’t have experience with it, I wouldn’t bother. Just start from scratch and secure copy your volumes using tar and gunzip
Trying to 1:1 migrate the node is much more complex than just creating a new node and migrating the files inside of it to the new one
Copying /var/lib/pterodactyl/volumes, copying the DB and copying .env is all you need
Setting up tailscale solely for a file transfer is crazy to me
SSH (SCP) exists, SFTP exists