{"id":1109,"date":"2026-11-17T18:00:00","date_gmt":"2026-11-17T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1109"},"modified":"2026-11-17T18:00:00","modified_gmt":"2026-11-17T18:00:00","slug":"install-docmost-docker-debian-11","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/17\/install-docmost-docker-debian-11\/","title":{"rendered":"How to Install Docmost Using Docker on Debian 11"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Docmost using Docker on Debian 11 to run a private collaborative wiki with PostgreSQL, Redis, and HTTPS. Allow about 15 minutes for the Docker images, DNS check, and first workspace setup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A 64-bit Debian 11 (Bullseye) VPS with at least 2 GB of RAM and 10 GB of free disk space. Debian 11 reached the end of its Debian LTS period on August 31, 2026, so plan a migration to Debian 12 or newer after this deployment.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a normal Linux account with working <code>sudo<\/code> privileges.<\/li>\n\n\n<li>A domain such as <code>YOUR_DOMAIN<\/code> with an A record pointing to <code>SERVER_IP<\/code>. Caddy needs this name to request a trusted TLS certificate.<\/li>\n\n\n<li>Provider-level inbound TCP access for ports 80 and 443. Docmost itself will stay on the server&#8217;s private Docker network.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> if you need a Debian server with root access.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This guide uses the Docker Engine repository for Bullseye, Docker Compose, and Debian&#8217;s <code>ufw<\/code> firewall. Run the commands as a sudo-capable user; add <code>sudo<\/code> to commands if you are not logged in as <code>root<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Debian 11 and update the host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Confirming the codename prevents an old image from accidentally using a Bookworm or Trixie repository.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. \/etc\/os-release\nprintf '%s\\n' \"$PRETTY_NAME\"\nprintf 'Codename: %s\\n' \"$VERSION_CODENAME\"\nuname -m\nsudo apt-get update\nsudo apt-get upgrade -y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The release should identify Debian GNU\/Linux 11 and the codename should be <code>bullseye<\/code>. For a typical 64-bit VPS, the architecture line is <code>x86_64<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Debian GNU\/Linux 11 (bullseye)\nCodename: bullseye\nx86_64<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If <code>apt-get update<\/code> reports expired Debian mirrors, repair the provider&#8217;s Debian 11 archive sources before continuing. Do not point a Bullseye host at a newer release just to silence an update error.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Install Docker Engine and Compose<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Docker runs Docmost&#8217;s containers, while the Compose plugin manages the application, database, cache, and reverse proxy together. Docker&#8217;s <a href=\"https:\/\/docs.docker.com\/engine\/install\/debian\/\" target=\"_blank\" rel=\"noopener\">Debian installation guide<\/a> uses a signed keyring and a dedicated Apt source, which avoids the deprecated <code>apt-key<\/code> approach.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Install the tools needed to add the repository, then register the Bullseye source explicitly:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt-get install -y ca-certificates curl openssl\nsudo install -m 0755 -d \/etc\/apt\/keyrings\nsudo curl -fsSL https:\/\/download.docker.com\/linux\/debian\/gpg -o \/etc\/apt\/keyrings\/docker.asc\nsudo chmod a+r \/etc\/apt\/keyrings\/docker.asc\nsudo tee \/etc\/apt\/sources.list.d\/docker.sources &gt; \/dev\/null &lt;&lt;EOF\nTypes: deb\nURIs: https:\/\/download.docker.com\/linux\/debian\nSuites: bullseye\nComponents: stable\nArchitectures: $(dpkg --print-architecture)\nSigned-By: \/etc\/apt\/keyrings\/docker.asc\nEOF\nsudo apt-get update\nsudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin\nsudo systemctl enable --now docker<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Check the daemon, Compose plugin, and a disposable container before configuring Docmost:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active docker\nsudo docker version --format 'Client {{.Client.Version}} \/ Server {{.Server.Version}}'\nsudo docker compose version\nsudo docker run --rm hello-world<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output is similar to this; package patch versions will vary:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>active\nClient 29.x.y \/ Server 29.x.y\nDocker Compose version v2.x.y\nHello from Docker!<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Keep using <code>sudo docker<\/code> in this guide. Membership in the <code>docker<\/code> group grants root-equivalent control, so it should be an intentional choice rather than a convenience added during installation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create Docmost&#8217;s secrets and configuration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The application secret signs Docmost data, and PostgreSQL must receive the same database password that appears in the connection URL. Hexadecimal values avoid special-character parsing problems in that URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the deployment directory and generate two random values:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openssl rand -hex 32\nopenssl rand -hex 24\nsudo install -d -m 0750 \/opt\/docmost\nsudo nano \/opt\/docmost\/.env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Enter this in <code>\/opt\/docmost\/.env<\/code>, replacing every uppercase placeholder with the matching generated value and your real domain:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>APP_URL=https:\/\/YOUR_DOMAIN\nAPP_SECRET=REPLACE_WITH_64_HEX_CHARACTERS\nDB_PASSWORD=REPLACE_WITH_48_HEX_CHARACTERS<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Save the file, then restrict it because it contains the database credential:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chmod 600 \/opt\/docmost\/.env\nsudo chown root:root \/opt\/docmost\/.env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>APP_SECRET<\/code> must be at least 32 characters. <code>APP_URL<\/code> must exactly match the hostname people will use, including a subdomain such as <code>docs.YOUR_DOMAIN<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Define the containers and HTTPS proxy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Docmost&#8217;s official deployment uses PostgreSQL 18 and Redis 8. Caddy adds automatic HTTPS and forwards WebSocket connections, which the real-time editor needs; the <a href=\"https:\/\/docmost.com\/docs\/self-hosting\/reverse-proxy\" target=\"_blank\" rel=\"noopener\">Docmost reverse-proxy guidance<\/a> recommends this production pattern.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a Caddy configuration that sends requests to the internal <code>docmost<\/code> service:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/opt\/docmost\/Caddyfile<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use the following content, changing <code>YOUR_DOMAIN<\/code> to the same hostname in <code>.env<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>YOUR_DOMAIN {\n    reverse_proxy docmost:3000\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now create <code>\/opt\/docmost\/docker-compose.yml<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/opt\/docmost\/docker-compose.yml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Paste this Compose file:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>services:\n  caddy:\n    image: caddy:2\n    ports:\n      - \"80:80\"\n      - \"443:443\"\n    volumes:\n      - .\/Caddyfile:\/etc\/caddy\/Caddyfile:ro\n      - caddy_data:\/data\n      - caddy_config:\/config\n    depends_on:\n      - docmost\n    restart: unless-stopped\n\n  docmost:\n    image: docmost\/docmost:latest\n    depends_on:\n      - db\n      - redis\n    environment:\n      APP_URL: ${APP_URL}\n      APP_SECRET: ${APP_SECRET}\n      DATABASE_URL: postgresql:\/\/docmost:${DB_PASSWORD}@db:5432\/docmost\n      REDIS_URL: redis:\/\/redis:6379\n    ports:\n      - \"127.0.0.1:3000:3000\"\n    restart: unless-stopped\n    volumes:\n      - docmost:\/app\/data\/storage\n\n  db:\n    image: postgres:18\n    environment:\n      POSTGRES_DB: docmost\n      POSTGRES_USER: docmost\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    restart: unless-stopped\n    volumes:\n      - db_data:\/var\/lib\/postgresql\n\n  redis:\n    image: redis:8\n    command: [\"redis-server\", \"--appendonly\", \"yes\", \"--maxmemory-policy\", \"noeviction\"]\n    restart: unless-stopped\n    volumes:\n      - redis_data:\/data\n\nvolumes:\n  docmost:\n  db_data:\n  redis_data:\n  caddy_data:\n  caddy_config:<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>127.0.0.1<\/code> binding keeps port 3000 off the public interface, while the named volumes preserve pages, uploads, database records, Redis data, and TLS certificates when containers are recreated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Allow web traffic and start Docmost<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Only Caddy needs public access. UFW allows SSH and the two web ports; PostgreSQL and Redis have no published host ports.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt-get install -y ufw\nsudo ufw default deny incoming\nsudo ufw default allow outgoing\nsudo ufw allow OpenSSH\nsudo ufw allow 80\/tcp\nsudo ufw allow 443\/tcp\nsudo ufw --force enable\nsudo ufw status verbose<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Docker can place published ports ahead of some UFW filtering paths, so the safest rule is to publish only the ports you actually need. This Compose file exposes only 80 and 443 publicly and binds Docmost to loopback.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Validate the interpolated Compose file, pull the images, and start the stack:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose config --quiet\nsudo docker compose pull\nsudo docker compose up -d\nsudo docker compose ps<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The first pull can take several minutes. A healthy result has four services in an <code>Up<\/code> state, with only Caddy showing public port mappings:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>NAME                 SERVICE   STATUS    PORTS\ndocmost-caddy-1      caddy     Up        0.0.0.0:80-&gt;80\/tcp, 0.0.0.0:443-&gt;443\/tcp\ndocmost-docmost-1    docmost   Up\ndocmost-db-1         db        Up\ndocmost-redis-1      redis     Up<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Container names may differ. A service that repeatedly restarts needs its logs checked before you open the site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Docmost installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Test the health endpoint through the domain so DNS, Caddy&#8217;s certificate, the proxy route, and the Docmost listener are checked together:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsS -o \/dev\/null -w 'HTTP %{http_code}\\n' https:\/\/YOUR_DOMAIN\/api\/health<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>HTTP 200<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/YOUR_DOMAIN<\/code> in a browser. The Docmost workspace form should appear. Enter a workspace name, administrator details, and a unique strong password, then create a test page and edit it in a second browser tab to confirm the real-time path works.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review the startup messages once the workspace exists:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose logs --tail=40 caddy docmost db redis<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The logs should not contain a restart loop, database authentication failure, or ACME certificate error.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Launch a private Docmost wiki\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Debian VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Launch a private Docmost wiki<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Run your documentation workspace on a Docker-ready VPS with the resources and root access this setup needs.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-vps\" aria-label=\"View Linux VPS plans\">View Linux VPS plans<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><code>Unable to locate package docker-ce<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Docker source is missing, has the wrong suite, or Apt has stale metadata. Check that the source says <code>Suites: bullseye<\/code>, then refresh the cache and retry:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -E '^(URIs|Suites|Signed-By):' \/etc\/apt\/sources.list.d\/docker.sources\nsudo apt-get update\nsudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not replace <code>bullseye<\/code> with <code>bookworm<\/code> on a Debian 11 system; mixing release repositories can break the host.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>permission denied while trying to connect to the Docker daemon socket<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The current account is not allowed to use Docker directly. Use the <code>sudo docker<\/code> and <code>sudo docker compose<\/code> forms shown here, or deliberately configure Docker group access for a trusted administrator and reconnect the SSH session.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The browser shows <code>502 Bad Gateway<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Caddy is reachable but Docmost is still initializing or has stopped. Inspect the first application or dependency error, then restart only after correcting the cause:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose ps\nsudo docker compose logs --tail=80 docmost db redis\nsudo docker compose restart<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Caddy cannot obtain a certificate<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The domain may point to another address, or port 80\/443 may be blocked by the VPS provider firewall. Confirm that <code>YOUR_DOMAIN<\/code> resolves to <code>SERVER_IP<\/code>, allow both ports in the provider&#8217;s network controls, and keep the Caddy container running while it requests the certificate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>password authentication failed for user \"docmost\"<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">PostgreSQL keeps the password from its first initialization. Restore the original <code>DB_PASSWORD<\/code> in <code>.env<\/code> if it was changed later; do not run <code>docker compose down -v<\/code> on a live wiki because removing <code>db_data<\/code> deletes the database.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening and maintenance<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Back up the <code>docmost<\/code>, <code>db_data<\/code>, <code>redis_data<\/code>, <code>caddy_data<\/code>, and <code>caddy_config<\/code> volumes before upgrades or host maintenance.<\/li>\n\n\n<li>Update deliberately from <code>\/opt\/docmost<\/code> with <code>sudo docker compose pull<\/code> followed by <code>sudo docker compose up -d<\/code>, and review the result with <code>sudo docker compose ps<\/code>.<\/li>\n\n\n<li>Keep port 3000, PostgreSQL, and Redis unpublished. The <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">VPSLake SSH hardening generator<\/a> can help tighten SSH after the application is working.<\/li>\n\n\n<li>Treat Debian 11 as a migration target: move the deployment to a supported Debian release before relying on it for a long-lived public workspace.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is Debian 11 still a good choice for a new Docmost server?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Debian 11 is a legacy target now that its regular LTS period has ended. Use this guide when an existing Bullseye VPS cannot be upgraded immediately, and choose Debian 12 or newer for a fresh deployment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I access Docmost by IP address instead of a domain?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can test the app over an IP, but Caddy cannot provide the same straightforward trusted certificate for a normal public deployment. A domain also gives you a stable value for <code>APP_URL<\/code> and keeps browser WebSocket connections on HTTPS.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why are PostgreSQL and Redis separate containers?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Docmost uses PostgreSQL for structured application data and Redis for supporting cache and real-time work. Compose keeps both services on its private network, so neither database port is exposed to the internet.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I stop Docmost without deleting its data?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">From <code>\/opt\/docmost<\/code>, run <code>sudo docker compose stop<\/code> to stop the services while retaining their named volumes. Use <code>sudo docker compose start<\/code> to bring the same workspace back without repeating setup.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Is Debian 11 still a good choice for a new Docmost server?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Debian 11 is a legacy target now that its regular LTS period has ended. Use this guide when an existing Bullseye VPS cannot be upgraded immediately, and choose Debian 12 or newer for a fresh deployment.\"}}, {\"@type\": \"Question\", \"name\": \"Can I access Docmost by IP address instead of a domain?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can test the app over an IP, but Caddy cannot provide the same straightforward trusted certificate for a normal public deployment. A domain also gives you a stable value for `APP_URL` and keeps browser WebSocket connections on HTTPS.\"}}, {\"@type\": \"Question\", \"name\": \"Why are PostgreSQL and Redis separate containers?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Docmost uses PostgreSQL for structured application data and Redis for supporting cache and real-time work. Compose keeps both services on its private network, so neither database port is exposed to the internet.\"}}, {\"@type\": \"Question\", \"name\": \"How do I stop Docmost without deleting its data?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"From `\/opt\/docmost`, run `sudo docker compose stop` to stop the services while retaining their named volumes. Use `sudo docker compose start` to bring the same workspace back without repeating setup.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on Debian 11 with PostgreSQL, Redis, Caddy HTTPS, UFW rules, verification, and common fixes for a secure private wiki in minutes.","protected":false},"author":1,"featured_media":1110,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,9],"tags":[96,118,138,139],"class_list":["post-1109","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-debian-11","tag-docker","tag-docmost","tag-self-hosting","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1109","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=1109"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1109\/revisions"}],"predecessor-version":[{"id":4084,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1109\/revisions\/4084"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1110"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1109"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1109"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1109"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}