{"id":1768,"date":"2026-11-15T22:36:53","date_gmt":"2026-11-15T22:36:53","guid":{"rendered":"https:\/\/affordablevpsserver.com\/blog\/?p=1768"},"modified":"2026-11-15T22:36:53","modified_gmt":"2026-11-15T22:36:53","slug":"vps-migration-preflight-snapshot-checks","status":"publish","type":"post","link":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/","title":{"rendered":"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Most failed migrations do not fail during the move. They fail three weeks later when a cron job that never ran on the old host turns out to have been the only thing pruning a log directory, or when the mail server stops relaying because the new provider blocks port 25 and nobody checked. This checklist is the pre-flight pass: what to inventory on the source, what to prove on the target before the switch, and the post-cutover checks that catch what the pre-flight missed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Capture the Source Machine&#8217;s Real State<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before copying anything, record the numbers the new plan has to beat. A cheap destination plan is often smaller in one dimension than the source, and you want to discover that now rather than after DNS has moved.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># disk and inode headroom \u2014 both matter, inodes often bite first\ndf -h; echo; df -i\n# top directories by size, skipping mounts\ndu -xhd1 \/ 2&gt;\/dev\/null | sort -h | tail -15\n# memory and swap in use at peak\nfree -m; swapon --show\n# kernel, distro and PHP\/MySQL versions\nuname -r; cat \/etc\/os-release | head -3\nphp -v | head -1; mysql --version; nginx -v 2&gt;&amp;1\n# listening services and firewall\nss -tulpn\niptables-save &gt; \/root\/iptables.bak 2&gt;\/dev\/null; nft list ruleset &gt; \/root\/nft.bak 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Note the <code>df -i<\/code> figure against the destination&#8217;s. A source with 4 million inodes in use will not fit on a plan capped at 500,000, even if the byte count looks fine. Also record the PHP minor version: an app that works on 8.1 may throw deprecation warnings on 8.3, and a cheap new plan will often ship 8.3 as default.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Inventory Every Scheduled Job<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cron is the most common silent breakage. Collect every scheduler in one place and read each line.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>for u in $(cut -d: -f1 \/etc\/passwd); do echo \"== $u\"; crontab -l -u \"$u\" 2&gt;\/dev\/null; done\nls -1 \/etc\/cron.d\/ \/etc\/cron.daily\/ 2&gt;\/dev\/null\nsystemctl list-timers --all --no-pager\n# anything referencing a path that will change\ngrep -rE \"rsync|backup|\/srv\/|\/home\/\" \/etc\/cron* 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Job<\/th><th>Breakage risk on new host<\/th><th>Check<\/th><\/tr><\/thead><tbody><tr><td>Certbot renew<\/td><td>Timer missing or wrong challenge type<\/td><td><code>certbot renew --dry-run<\/code><\/td><\/tr><tr><td>Backup to object storage<\/td><td>Credentials\/env file not copied<\/td><td>Run once manually, check exit code<\/td><\/tr><tr><td>Database optimise<\/td><td>Version-specific SQL syntax<\/td><td>Run on target, read stderr<\/td><\/tr><tr><td>Log rotation<\/td><td>Custom logrotate config under \/etc\/logrotate.d<\/td><td><code>logrotate -d<\/code> on target<\/td><\/tr><tr><td>App queue worker (systemd)<\/td><td>Unit file not enabled<\/td><td><code>systemctl is-enabled<\/code><\/td><\/tr><\/tbody><\/table>\n<\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Lower DNS TTLs on a Schedule<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">TTL reduction must happen at least two times the current TTL before cutover, because resolvers cache the old value until it expires. Record the current TTLs, then set A, AAAA, MX and relevant CNAMEs to 300 seconds.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># current TTLs and resolved values\ndig +noall +answer example.com A\ndig +noall +answer example.com MX\ndig +noall +answer www.example.com CNAME\n\n# typical schedule for a 3600s TTL:\n# T-2h  or earlier: set TTL to 300, wait for old TTL to expire\n# T-26h: verify propagation with a public resolver\ndig @1.1.1.1 example.com A +noall +answer<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If your DNS is hosted at the provider you are leaving, move the zone to a third-party nameserver days before cutover and change the registrar&#8217;s NS records first. Migrating DNS and the web server in the same hour doubles your rollback time.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Prove TLS Issuance on the Target<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Do not assume the new host can obtain certificates. Some cheap plans sit behind NAT without port 80 reachable, which breaks HTTP-01 challenges. Before cutover, confirm inbound 80\/443 reach the destination.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># from the target, confirm a webserver answers on 80 from outside\ncurl -I http:\/\/target-ip\/ -H \"Host: example.com\"\n# then a test issuance for the real name \u2014 this must succeed pre-cutover\ncertbot certonly --webroot -w \/var\/www\/html -d example.com --dry-run\n# if DNS-01 with a provider API is available, staging test:\ncertbot certonly --dns-cloudflare -d example.com --staging<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Rate limits are the real cost of getting this wrong: five duplicate certificate limits per week per domain set means a botched cutover can leave you unable to issue for days. Always run <code>--dry-run<\/code> or <code>--staging<\/code> first. If you are copying the existing certificate instead of reissuing, copy <code>\/etc\/letsencrypt<\/code> whole, account key included, or renewals on the new host will fail.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Mail Records Are Not Optional<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Even if the site does not send mail, the domain probably does \u2014 password resets, contact forms, transactional receipts. Port 25 is blocked on a majority of budget providers, and many also block 465\/587 until you request unblocking.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Record<\/th><th>What to capture<\/th><th>Failure symptom<\/th><\/tr><\/thead><tbody><tr><td>MX<\/td><td>Priorities and target hostnames<\/td><td>Inbound mail bounces after cutover<\/td><\/tr><tr><td>SPF (TXT)<\/td><td>Full string, including includes<\/td><td>Outbound mail marked spam<\/td><\/tr><tr><td>DKIM<\/td><td>Selector name + public key; private key on the host<\/td><td>DMARC fails, delivery drops<\/td><\/tr><tr><td>DMARC<\/td><td>Policy and rua address<\/td><td>Reports lost, policy silently stricter<\/td><\/tr><tr><td>PTR \/ rDNS<\/td><td>Requested from the new provider<\/td><td>Major mailbox providers reject or greylist<\/td><\/tr><\/tbody><\/table>\n<\/figure>\n\n\n\n<pre class=\"wp-block-code\"><code>dig +short example.com MX\ndig +short example.com TXT\ndig +short SELECTOR._domainkey.example.com TXT\n# outbound test from the target before cutover\necho test | mail -s test you@example.net &amp;&amp; tail -5 \/var\/log\/mail.log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the new provider blocks port 25 permanently, the correct answer is to relay outbound mail through a transactional provider and add its include to SPF \u2014 not to keep the old host alive purely for mail.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Restore Test on the Target, Not Just a Copy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The migration is only as good as a restore you have actually performed. On the target, before DNS changes, do a full restore and then compare it against the source numerically.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># row counts on the three biggest tables, both hosts\nmysql -N -e \"SELECT table_name, table_rows FROM information_schema.tables\n  WHERE table_schema='appdb' ORDER BY table_rows DESC LIMIT 3;\"\n# file counts and total size\nfind \/var\/www\/html -type f | wc -l; du -sh \/var\/www\/html\n# checksums of a sample of static assets\nfind \/var\/www\/html\/uploads -type f -name '*.jpg' | head -50 | xargs md5sum | sort -k2 | md5sum<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then serve the restored site locally against the real domain name using a hosts-file override, and click through the five pages that matter most: home, a deep article, a search result, a form submission and a login. This catches hardcoded absolute URLs, missing rewrite rules and plugin licence issues that a checksum comparison will not.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pre-Flight Checklist Summary<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>Disk <em>and<\/em> inode usage measured on source; destination limits confirmed.<\/li><li>PHP and MySQL versions on target matched or tested against the app.<\/li><li>Every cron job, systemd timer and logrotate config inventoried.<\/li><li>TTL lowered 2\u00d7 current value ahead of cutover; DNS zone on an independent provider.<\/li><li>Firewall rules exported and recreated on the target.<\/li><li>TLS dry-run successful; account key copied if using the existing cert.<\/li><li>MX, SPF, DKIM, DMARC captured; outbound mail tested from the target.<\/li><li>Full restore performed and verified numerically and by clicking through.<\/li><li>Rollback plan written: old IP, old instance still paid, and a time to revert by.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Post-Cutover Verification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After the switch, verify from outside rather than from the server itself \u2014 the server always thinks it works. Run these within the first hour.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># confirm the world sees the new IP\ndig @8.8.8.8 example.com +short\n# TLS chain validity and expiry\ncurl -sSI https:\/\/example.com | head -5\nopenssl s_client -connect example.com:443 -servername example.com \/dev\/null | openssl x509 -noout -dates -issuer\n# status codes for key paths\nfor p in \/ \/robots.txt \/sitemap.xml \/wp-login.php; do echo -n \"$p \"; curl -so \/dev\/null -w '%{http_code}\\n' https:\/\/example.com$p; done\n# mail path\ndig +short example.com MX<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then check the things that only fail under use: submit the contact form, trigger a password reset, and confirm a search returns results from the new database rather than a cached page. Watch <code>journalctl -f<\/code> and the nginx error log for the first 24 hours; most cutover faults appear as a slow trickle of 404s on paths that existed with a different permalink structure on the old host.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The First Week After Cutover<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Keep the old instance paid and powered for seven days \u2014 the cost of a week&#8217;s overlap on a cheap plan is less than an hour of downtime, and it is your only fast rollback. During that week, check three things daily: that backups run on the new host and land off-host, that certificate renewal succeeded (or is scheduled correctly), and that the destination&#8217;s disk usage is not climbing faster than the plan can absorb. If any of those look wrong, reverting the A record is a five-minute operation while you still have the source intact.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For sizing the destination plan before you start, the price-banded tables at <a href=\"https:\/\/affordablevpsserver.com\/#providers\">the VPS provider comparison<\/a> are ordered to match this checklist&#8217;s disk and memory figures.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Most failed migrations do not fail during the move. They fail three weeks later when a cron job that never ran on the old host turns out to have been the only thing pruning a log directory, or when the mail server stops relaying because the new provider blocks port 25 and nobody checked. This [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":1,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-1768","post","type-post","status-publish","format-standard","hentry","category-vps-hosting-tutorials"],"blocksy_meta":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans - Affordable VPS Server Blog<\/title>\n<meta name=\"description\" content=\"Most failed migrations do not fail during the move. They fail three weeks later when a cron job that never ran on the old host turns out to have been the\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans\" \/>\n<meta property=\"og:description\" content=\"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans\" \/>\n<meta property=\"og:url\" content=\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/\" \/>\n<meta property=\"og:site_name\" content=\"Affordable VPS Server Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-15T22:36:53+00:00\" \/>\n<meta name=\"author\" content=\"Affordable-Vps-Server-Author\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Affordable-Vps-Server-Author\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/\",\"url\":\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/\",\"name\":\"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans - Affordable VPS Server Blog\",\"isPartOf\":{\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/#website\"},\"datePublished\":\"2026-11-15T22:36:53+00:00\",\"author\":{\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/#\/schema\/person\/685a02c93a3c45030f7427ec928b0df7\"},\"description\":\"Most failed migrations do not fail during the move. They fail three weeks later when a cron job that never ran on the old host turns out to have been the\",\"breadcrumb\":{\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/affordablevpsserver.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/#website\",\"url\":\"https:\/\/affordablevpsserver.com\/blog\/\",\"name\":\"Affordable VPS Server Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/affordablevpsserver.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/#\/schema\/person\/685a02c93a3c45030f7427ec928b0df7\",\"name\":\"Affordable-Vps-Server-Author\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/affordablevpsserver.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/8fa20973a7dd04621d396c26ba26b5c5e6c19595583335121958527393f6f95e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/8fa20973a7dd04621d396c26ba26b5c5e6c19595583335121958527393f6f95e?s=96&d=mm&r=g\",\"caption\":\"Affordable-Vps-Server-Author\"},\"sameAs\":[\"https:\/\/affordablevpsserver.com\/blog\"],\"url\":\"https:\/\/affordablevpsserver.com\/blog\/author\/affordablevpsserver\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans - Affordable VPS Server Blog","description":"Most failed migrations do not fail during the move. They fail three weeks later when a cron job that never ran on the old host turns out to have been the","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/","og_locale":"en_US","og_type":"article","og_title":"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans","og_description":"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans","og_url":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/","og_site_name":"Affordable VPS Server Blog","article_published_time":"2026-11-15T22:36:53+00:00","author":"Affordable-Vps-Server-Author","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Affordable-Vps-Server-Author","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/","url":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/","name":"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans - Affordable VPS Server Blog","isPartOf":{"@id":"https:\/\/affordablevpsserver.com\/blog\/#website"},"datePublished":"2026-11-15T22:36:53+00:00","author":{"@id":"https:\/\/affordablevpsserver.com\/blog\/#\/schema\/person\/685a02c93a3c45030f7427ec928b0df7"},"description":"Most failed migrations do not fail during the move. They fail three weeks later when a cron job that never ran on the old host turns out to have been the","breadcrumb":{"@id":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/affordablevpsserver.com\/blog\/vps-migration-preflight-snapshot-checks\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/affordablevpsserver.com\/blog\/"},{"@type":"ListItem","position":2,"name":"A Pre-Migration Snapshot Checklist Before Moving a Website Between Cheap VPS Plans"}]},{"@type":"WebSite","@id":"https:\/\/affordablevpsserver.com\/blog\/#website","url":"https:\/\/affordablevpsserver.com\/blog\/","name":"Affordable VPS Server Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/affordablevpsserver.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/affordablevpsserver.com\/blog\/#\/schema\/person\/685a02c93a3c45030f7427ec928b0df7","name":"Affordable-Vps-Server-Author","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/affordablevpsserver.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/8fa20973a7dd04621d396c26ba26b5c5e6c19595583335121958527393f6f95e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/8fa20973a7dd04621d396c26ba26b5c5e6c19595583335121958527393f6f95e?s=96&d=mm&r=g","caption":"Affordable-Vps-Server-Author"},"sameAs":["https:\/\/affordablevpsserver.com\/blog"],"url":"https:\/\/affordablevpsserver.com\/blog\/author\/affordablevpsserver\/"}]}},"_links":{"self":[{"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/posts\/1768","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/comments?post=1768"}],"version-history":[{"count":1,"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/posts\/1768\/revisions"}],"predecessor-version":[{"id":1770,"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/posts\/1768\/revisions\/1770"}],"wp:attachment":[{"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/media?parent=1768"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/categories?post=1768"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/affordablevpsserver.com\/blog\/wp-json\/wp\/v2\/tags?post=1768"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}