{"id":1119,"date":"2026-11-19T03:00:00","date_gmt":"2026-11-19T03:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1119"},"modified":"2026-11-19T03:00:00","modified_gmt":"2026-11-19T03:00:00","slug":"install-docmost-docker-ubuntu-22-04","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/19\/install-docmost-docker-ubuntu-22-04\/","title":{"rendered":"How to Install Docmost with Docker on Ubuntu 22.04"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Docmost using Docker on Ubuntu 22.04 to get a private collaborative wiki behind automatic HTTPS. With DNS already pointed to your VPS, the setup takes about 15 minutes and ends at Docmost&#8217;s workspace creation 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 Ubuntu 22.04 LTS (Jammy Jellyfish) VPS with at least 2 GB of RAM and 10 GB of free disk space. Plan for extra storage if your team will upload files.<\/li>\n\n\n<li>SSH access as <code>root<\/code> or a normal user with working <code>sudo<\/code> privileges.<\/li>\n\n\n<li>A hostname such as <code>YOUR_DOMAIN<\/code> with an A record pointing to <code>SERVER_IP<\/code>. Caddy needs the hostname to issue a trusted TLS certificate.<\/li>\n\n\n<li>Inbound TCP 80 and 443 allowed by your VPS provider. SSH must also be reachable; Docmost&#8217;s application port will not be public.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> if you need an Ubuntu 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 regular SSH account. If you are logged in as <code>root<\/code>, remove <code>sudo<\/code> from each command.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Ubuntu 22.04 and update the host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Confirming the Jammy codename before adding Docker&#8217;s repository prevents Apt from pulling packages for the wrong Ubuntu release.<\/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 check should show Jammy and a 64-bit architecture:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Ubuntu 22.04.x LTS\nCodename: jammy\nx86_64<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Resolve any DNS, mirror, or package-signature error now. Do not substitute <code>noble<\/code> or another codename in the Docker source.<\/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 provides the container runtime, while the Compose plugin starts Docmost, PostgreSQL, Redis, and Caddy from one definition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remove packages that can conflict with Docker&#8217;s official Engine packages. On a server already running important containers, inspect those workloads before removing a runtime package.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt-get remove -y docker.io docker-compose docker-compose-v2 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\/ubuntu\/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\/ubuntu\nSuites: ${UBUNTU_CODENAME:-$VERSION_CODENAME}\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 Docker&#8217;s <a href=\"https:\/\/docs.docker.com\/engine\/install\/ubuntu\/\" target=\"_blank\" rel=\"noopener\">official Ubuntu installation instructions<\/a> and avoids the deprecated <code>apt-key<\/code> workflow. Check the daemon, Compose plugin, and a disposable container:<\/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; exact 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\">This guide keeps <code>sudo docker<\/code> in use. Membership in the <code>docker<\/code> group provides root-equivalent control of the host, so add it only if you accept that tradeoff.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create Docmost&#8217;s secrets<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: A long application secret protects sessions, and one shared database password lets both PostgreSQL and Docmost authenticate consistently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the application directory and generate hexadecimal values. Hex characters avoid special-character parsing problems inside the PostgreSQL connection URL.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openssl rand -hex 32\nopenssl rand -hex 24\nsudo install -d -m 0755 \/opt\/docmost\nsudo nano \/opt\/docmost\/.env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Put the first generated value in <code>APP_SECRET<\/code>, the second in <code>DB_PASSWORD<\/code>, and use the real hostname in <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, then limit access to the credentials:<\/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 first command produces a 64-character secret, which is longer than Docmost&#8217;s 32-character minimum. Keep <code>APP_URL<\/code> identical to the address users will open, including a subdomain if you use one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Define Caddy and the Docmost stack<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Caddy obtains and renews HTTPS certificates and forwards WebSocket traffic, while named Docker volumes keep pages, uploads, database records, and certificates across container updates.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the reverse-proxy file. The <a href=\"https:\/\/docmost.com\/docs\/self-hosting\/reverse-proxy\/caddy\" target=\"_blank\" rel=\"noopener\">official Docmost Caddy configuration<\/a> proxies to the Compose service name and supports the collaborative editor:<\/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, replacing <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\">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 definition:<\/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 prevents direct internet access to port 3000; Caddy still reaches Docmost over the private Compose network. Do not publish PostgreSQL or Redis. The quoted variables are loaded from <code>\/opt\/docmost\/.env<\/code> when Compose runs in that directory.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Configure UFW and launch Docmost<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: UFW should allow only administration and Caddy&#8217;s web traffic, leaving the application, database, and cache off the public interface.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If SSH uses a custom port, replace <code>OpenSSH<\/code> with that port rule before enabling the firewall. Adding the SSH rule first helps prevent locking yourself out.<\/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\">The status should show SSH, HTTP, and HTTPS as allowed. Docker warns that published container ports can bypass some UFW paths, which is another reason this stack publishes only Caddy&#8217;s ports and binds Docmost to loopback. Apply the same 80\/443 policy in the VPS provider firewall.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Validate the Compose interpolation, download the images, and start the services:<\/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\"><code>docker compose config --quiet<\/code> should return without an error. A healthy stack has four services running, with only Caddy showing public bindings:<\/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\">Names may vary with the Compose project name. A service that repeatedly restarts needs its logs checked before you continue.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Docmost installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: One HTTPS request checks DNS, the provider firewall, UFW, Caddy&#8217;s certificate, the reverse proxy, and Docmost&#8217;s listener 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 setup page should ask for a workspace name and administrator account. Use a unique, strong password, create a page, and edit it from a second browser tab to confirm the application and real-time connection are working.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review recent logs after the first launch:<\/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 privately\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Ubuntu VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Host Docmost privately<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Run a Docker-ready Docmost workspace on an Ubuntu VPS with root access and room for persistent data.<\/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 was not added correctly, or Apt is using a stale package index. Confirm that <code>\/etc\/apt\/sources.list.d\/docker.sources<\/code> contains <code>Suites: jammy<\/code>, then run <code>sudo apt-get update<\/code> and retry the install. Do not mix a Debian source or Ubuntu 24.04 codename into this server.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">UFW blocks SSH after it is enabled<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The SSH service rule may not match a custom SSH port. From an existing console or provider VNC session, allow the actual port, for example <code>sudo ufw allow 2222\/tcp<\/code>, then run <code>sudo ufw reload<\/code>. Keep the current SSH session open until a new connection succeeds.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>502 Bad Gateway<\/code> from Caddy<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Docmost may still be starting, or the application container may be restarting because a variable is missing. Run <code>sudo docker compose ps<\/code> and <code>sudo docker compose logs --tail=80 docmost<\/code>; check that <code>.env<\/code> is in <code>\/opt\/docmost<\/code> and that <code>sudo docker compose config<\/code> renders non-empty <code>APP_SECRET<\/code>, <code>DB_PASSWORD<\/code>, and <code>APP_URL<\/code> values.<\/p>\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 A record may point somewhere else, or port 80\/443 may be blocked before traffic reaches the VPS. Check that <code>YOUR_DOMAIN<\/code> resolves to <code>SERVER_IP<\/code>, allow both ports in the provider firewall, and inspect <code>sudo docker compose logs caddy<\/code>. Caddy needs a publicly resolvable hostname for a trusted certificate.<\/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>Keep <code>\/opt\/docmost\/.env<\/code> root-readable only and do not commit it to a repository.<\/li>\n\n\n<li>Back up the <code>docmost<\/code>, <code>db_data<\/code>, and <code>caddy_data<\/code> volumes before upgrades or host maintenance. <code>docker compose down<\/code> does not remove named volumes unless you add <code>-v<\/code>.<\/li>\n\n\n<li>Update the stack deliberately with <code>sudo docker compose pull &amp;&amp; sudo docker compose up -d<\/code> from <code>\/opt\/docmost<\/code>, then check the logs and open the workspace.<\/li>\n\n\n<li>After confirming SSH access, use the <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">VPSLake SSH hardening generator<\/a> to review key-only authentication and other SSH settings.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use a subdomain for Docmost?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Create an A record such as <code>docs.YOUR_DOMAIN<\/code>, then use that exact hostname in both <code>APP_URL<\/code> and <code>Caddyfile<\/code>. Caddy will request the certificate for the subdomain once DNS is visible and the web ports are reachable.<\/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 durable application data and Redis for caching and real-time coordination. Keeping both on the private Compose network avoids exposing their ports while allowing the application to reach them by service name.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I access Docmost at the server IP?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can test the application locally with <code>curl http:\/\/127.0.0.1:3000<\/code>, but the public configuration is designed for a domain. A hostname is needed for Caddy&#8217;s trusted HTTPS certificate and gives <code>APP_URL<\/code> a stable value.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What happens if I run <code>docker compose down<\/code>?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The containers and network stop, but the named volumes remain, so pages, uploads, PostgreSQL data, Redis data, and Caddy certificates are preserved. Start the deployment again with <code>sudo docker compose up -d<\/code> from <code>\/opt\/docmost<\/code>.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I use a subdomain for Docmost?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. Create an A record such as `docs.YOUR_DOMAIN`, then use that exact hostname in both `APP_URL` and `Caddyfile`. Caddy will request the certificate for the subdomain once DNS is visible and the web ports are reachable.\"}}, {\"@type\": \"Question\", \"name\": \"Why are PostgreSQL and Redis separate containers?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Docmost uses PostgreSQL for durable application data and Redis for caching and real-time coordination. Keeping both on the private Compose network avoids exposing their ports while allowing the application to reach them by service name.\"}}, {\"@type\": \"Question\", \"name\": \"Can I access Docmost at the server IP?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can test the application locally with `curl http:\/\/127.0.0.1:3000`, but the public configuration is designed for a domain. A hostname is needed for Caddy's trusted HTTPS certificate and gives `APP_URL` a stable value.\"}}, {\"@type\": \"Question\", \"name\": \"What happens if I run `docker compose down`?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The containers and network stop, but the named volumes remain, so pages, uploads, PostgreSQL data, Redis data, and Caddy certificates are preserved. Start the deployment again with `sudo docker compose up -d` from `\/opt\/docmost`.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on Ubuntu 22.04 with PostgreSQL, Redis, Caddy HTTPS, UFW, persistent storage, and troubleshooting in 15 minutes.","protected":false},"author":1,"featured_media":1120,"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":[118,138,139,101],"class_list":["post-1119","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-docker","tag-docmost","tag-self-hosting","tag-ubuntu-22-04","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1119","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=1119"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1119\/revisions"}],"predecessor-version":[{"id":4105,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1119\/revisions\/4105"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1120"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}