Add a TransIP API key pair and SiteShift lists your VPSes. Pick one, link it over SSH as root, and push a local WordPress site to it — or pull one you already run there.
Lists your VPSes · SSH as root, port 22 · webroot /var/www/html by default
Under API → Key pairs. TransIP shows the private key once, so save it immediately. If you restrict the key to whitelisted IPs, add this machine's IP to the list or TransIP rejects every request.
Hosting → Add account → TransIP → your TransIP username plus the private key (PEM). SiteShift validates it before saving.
New site → Pull from vendor → choose the VPS. SiteShift pre-fills root, port 22 and /var/www/html; adjust the webroot if your site lives elsewhere, and add your SSH key path or password.
Pull an existing site down, or create a local one and push it up. The VPS needs tar, mysqldump and mysql — standard on any LAMP/LEMP install.
TransIP's API has no VPS-creation endpoint that SiteShift uses, so new servers are made in the control panel; SiteShift only lists them.
No — it lists the ones you have. Create the VPS in the TransIP control panel, install your web stack, then pick it in SiteShift.
Yes. Root is only the default the integration pre-fills; change the SSH user and webroot on the connection to whatever your server uses.
If the package gives you SSH access, link it as a manual SSH connection. The API integration itself is about VPSes.
Connect your host once. Pull, work, push.
Get SiteShift — €9/mo