{"id":1111,"date":"2026-11-18T03:00:00","date_gmt":"2026-11-18T03:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1111"},"modified":"2026-11-18T03:00:00","modified_gmt":"2026-11-18T03:00:00","slug":"install-docmost-docker-debian-12","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/18\/install-docmost-docker-debian-12\/","title":{"rendered":"How to Install Docmost Using Docker on Debian 12"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Docmost using Docker on Debian 12 to run a private collaborative wiki behind HTTPS. With DNS already pointed at your VPS, the deployment takes about 15 minutes and ends at the Docmost workspace setup screen.<\/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 12 (Bookworm) VPS with at least 2 GB of RAM and 10 GB of free disk space. Leave additional room for uploaded files and Docker image updates.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a regular 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 uses this hostname to obtain and renew a trusted TLS certificate.<\/li>\n\n\n<li>Inbound TCP ports 80 and 443 allowed by both the VPS provider and the server firewall. Port 3000 does not need to be public.<\/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\">The commands below use <code>sudo<\/code> for a normal SSH user. If you are logged in as <code>root<\/code>, remove <code>sudo<\/code> from the commands.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Debian 12 and update the server<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Checking the release codename first prevents Docker\u2019s Apt repository from being configured for the wrong Debian version.<\/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 output should identify Bookworm and a supported 64-bit architecture:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Debian GNU\/Linux 12 (bookworm)\nCodename: bookworm\nx86_64<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Fix any Apt mirror, DNS, or signature error before continuing. Do not point a Debian 12 machine at a Debian 13 repository to work around a package 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\">Why: Docker runs the application containers, and the Compose plugin starts Docmost, PostgreSQL, Redis, and Caddy as one deployment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a fresh VPS, remove unofficial or conflicting Docker packages first. If this server already runs containers, inspect them before removing <code>podman-docker<\/code>, <code>containerd<\/code>, or <code>runc<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt-get remove -y docker.io docker-compose docker-doc docker-buildx podman-docker containerd runc\nsudo 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: bookworm\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\">This follows the signed-key setup in Docker\u2019s <a href=\"https:\/\/docs.docker.com\/engine\/install\/debian\/\" target=\"_blank\" rel=\"noopener\">official Debian installation guide<\/a>. Verify 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; the patch versions will change:<\/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 access to the host, so add it only as a deliberate administration choice.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create protected Docmost settings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Docmost needs a persistent application secret, while PostgreSQL must use one matching password in both its container and the application connection string.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Generate hexadecimal values so the database password can safely appear in a connection URL, then create the deployment directory:<\/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\">In <code>\/opt\/docmost\/.env<\/code>, use the first command\u2019s output for <code>APP_SECRET<\/code>, the second for <code>DB_PASSWORD<\/code>, and your real hostname for <code>APP_URL<\/code>:<\/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 and restrict it because it contains a 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\">The secret generated by <code>openssl rand -hex 32<\/code> is 64 characters, which exceeds Docmost\u2019s 32-character minimum. <code>APP_URL<\/code> must exactly match the hostname visitors will use, including a subdomain if you choose one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Add Caddy and the Compose definition<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Caddy terminates HTTPS and forwards WebSocket connections for Docmost\u2019s real-time editor, while Docker volumes preserve the wiki when containers are recreated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create <code>\/opt\/docmost\/Caddyfile<\/code>:<\/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\">Enter this content and replace <code>YOUR_DOMAIN<\/code> with the same hostname used 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\">The <a href=\"https:\/\/docmost.com\/docs\/self-hosting\/reverse-proxy\/caddy\" target=\"_blank\" rel=\"noopener\">official Docmost Caddy guide<\/a> uses this service-to-service proxy pattern and confirms that Caddy handles HTTPS and WebSockets. Now create the Compose file:<\/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 the following:<\/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 direct port 3000 access off the public interface. The named volumes hold pages, uploads, PostgreSQL data, Redis persistence, and Caddy certificates outside the disposable container layers.<\/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\">Why: UFW should permit SSH and Caddy\u2019s two web ports while the application, database, and cache remain unpublished.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If SSH uses a custom port, allow that port instead of <code>OpenSSH<\/code> before enabling UFW:<\/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 warns that published container ports can bypass some UFW filtering paths. The safer layout here is to publish only Caddy\u2019s 80 and 443, keep port 3000 on loopback, and apply the same web-port policy in the VPS provider firewall.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Validate the rendered Compose configuration, 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 may take several minutes. A healthy result has four services in an <code>Up<\/code> state, with Docmost bound only to loopback:<\/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        127.0.0.1:3000-&gt;3000\/tcp\ndocmost-db-1         db        Up\ndocmost-redis-1      redis     Up<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Compose may choose different names. If a service repeatedly restarts, inspect its logs before opening 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 HTTPS so one request checks DNS, Caddy\u2019s certificate, the reverse proxy, and Docmost\u2019s listener:<\/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. Docmost should display the workspace setup form. 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 real-time collaboration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review recent logs after the first login:<\/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 output should not show a repeating restart loop, PostgreSQL authentication failure, or ACME certificate error.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Host Docmost securely\">\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\">Host Docmost securely<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Run your private documentation workspace on a Docker-ready Debian VPS with root access.<\/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. Confirm that the source uses Debian 12\u2019s <code>bookworm<\/code> suite, refresh Apt, and retry the package installation:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -E '^(URIs|Suites|Architectures|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 change <code>bookworm<\/code> to <code>trixie<\/code> on a Debian 12 host; mixing release repositories can break the operating system.<\/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 may still be starting or may have exited. Inspect the application and dependency logs, correct the first reported error, and restart the services:<\/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 an HTTPS certificate<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The domain may resolve to a different server, or port 80\/443 may be blocked by the provider firewall. Confirm that <code>YOUR_DOMAIN<\/code> resolves to <code>SERVER_IP<\/code>, allow both ports in the provider controls, and keep Caddy running while it completes the certificate request.<\/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>sudo 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 VPS maintenance.<\/li>\n\n\n<li>Review image updates before applying them. From <code>\/opt\/docmost<\/code>, run <code>sudo docker compose pull<\/code> and then <code>sudo docker compose up -d<\/code>, followed by <code>sudo docker compose ps<\/code>.<\/li>\n\n\n<li>Keep port 3000, PostgreSQL, and Redis unpublished. After Docmost works, use the <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">VPSLake SSH hardening generator<\/a> to tighten SSH access.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What DNS record does Caddy need?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Create an A record for <code>YOUR_DOMAIN<\/code> that points to <code>SERVER_IP<\/code>. Wait until public DNS resolves to that address before starting the stack, because Caddy must reach the server on ports 80 and 443 to issue the certificate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use an existing Nginx or Apache server instead of Caddy?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes, but the proxy must send requests to Docmost on port 3000 and support WebSocket upgrades. Keep <code>APP_URL<\/code> set to the public HTTPS address and do not expose PostgreSQL or Redis.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does <code>docker compose down<\/code> delete my pages?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. <code>down<\/code> removes the containers and network but leaves the named volumes. Avoid <code>down -v<\/code> unless you intentionally want to erase the Docmost, PostgreSQL, Redis, and Caddy data volumes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I change the domain after installation?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Update <code>APP_URL<\/code> in <code>.env<\/code> and the hostname in <code>Caddyfile<\/code>, then run <code>sudo docker compose up -d<\/code> from <code>\/opt\/docmost<\/code>. Caddy will request a certificate for the new hostname after its DNS record points to the VPS.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"What DNS record does Caddy need?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Create an A record for `YOUR_DOMAIN` that points to `SERVER_IP`. Wait until public DNS resolves to that address before starting the stack, because Caddy must reach the server on ports 80 and 443 to issue the certificate.\"}}, {\"@type\": \"Question\", \"name\": \"Can I use an existing Nginx or Apache server instead of Caddy?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes, but the proxy must send requests to Docmost on port 3000 and support WebSocket upgrades. Keep `APP_URL` set to the public HTTPS address and do not expose PostgreSQL or Redis.\"}}, {\"@type\": \"Question\", \"name\": \"Does `docker compose down` delete my pages?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. `down` removes the containers and network but leaves the named volumes. Avoid `down -v` unless you intentionally want to erase the Docmost, PostgreSQL, Redis, and Caddy data volumes.\"}}, {\"@type\": \"Question\", \"name\": \"How do I change the domain after installation?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Update `APP_URL` in `.env` and the hostname in `Caddyfile`, then run `sudo docker compose up -d` from `\/opt\/docmost`. Caddy will request a certificate for the new hostname after its DNS record points to the VPS.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on Debian 12 with PostgreSQL, Redis, Caddy HTTPS, UFW rules, health checks, and fixes for a private wiki in minutes.","protected":false},"author":1,"featured_media":1112,"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":[97,118,138,139],"class_list":["post-1111","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-debian-12","tag-docker","tag-docmost","tag-self-hosting","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1111","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=1111"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1111\/revisions"}],"predecessor-version":[{"id":4089,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1111\/revisions\/4089"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1112"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1111"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}