{"id":1113,"date":"2026-11-18T09:00:00","date_gmt":"2026-11-18T09:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1113"},"modified":"2026-11-18T09:00:00","modified_gmt":"2026-11-18T09:00:00","slug":"install-docmost-docker-rocky-linux-10","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/18\/install-docmost-docker-rocky-linux-10\/","title":{"rendered":"How to Install Docmost Using Docker on Rocky Linux 10"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Docmost using Docker on Rocky Linux 10 to run a private, collaborative documentation workspace with PostgreSQL, Redis, and automatic HTTPS. With DNS already prepared, you can reach the workspace setup page in about 15 minutes.<\/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 Rocky Linux 10 VPS with at least 2 GB of RAM and 10 GB of free disk space. Allocate more storage if users will upload many files.<\/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 needs this hostname to request and renew a trusted TLS certificate.<\/li>\n\n\n<li>Provider-level inbound TCP access for ports 80 and 443. Docmost&#8217;s application port will stay private on the server.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> if you need a Rocky Linux server with root access.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The commands use <code>sudo<\/code> for a normal SSH account. If you are logged in as <code>root<\/code>, remove <code>sudo<\/code>. Rocky Linux 10 uses DNF and firewalld, and SELinux remains enabled throughout this setup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Rocky Linux 10 and update the host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Checking the release and architecture first keeps the Docker repository and packages aligned with the Rocky Linux 10 host.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. \/etc\/os-release\nprintf '%s\\n' \"$PRETTY_NAME\"\nprintf 'Release: %s\\n' \"$VERSION_ID\"\nuname -m\nsudo dnf upgrade -y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The output should identify Rocky Linux 10 and a 64-bit architecture:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Rocky Linux 10.x (Red Quartz)\nRelease: 10.x\nx86_64<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The exact minor release changes as Rocky publishes updates. Resolve any DNF mirror, DNS, or GPG-signature error before continuing.<\/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 Engine runs the application containers, while the Compose plugin starts Docmost and its PostgreSQL, Redis, and Caddy services together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a fresh VPS, remove packages that can conflict with Docker&#8217;s runtime. Skip this removal on a host that already runs important Podman containers until you have reviewed those workloads.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf remove -y docker docker-client docker-client-latest docker-common docker-latest docker-latest-logrotate docker-logrotate docker-engine podman runc\nsudo dnf install -y dnf-plugins-core ca-certificates curl openssl\nsudo dnf config-manager --add-repo https:\/\/download.docker.com\/linux\/rhel\/docker-ce.repo\nsudo dnf makecache\nsudo dnf 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\/rhel\/\" target=\"_blank\" rel=\"noopener\">official RHEL installation method<\/a>, which supports the RHEL-compatible package path used by Rocky Linux 10. Keep using <code>sudo docker<\/code> instead of adding your login to the <code>docker<\/code> group; that group grants root-equivalent control.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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; 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<h2 class=\"wp-block-heading\">Step 3: Create Docmost&#8217;s protected settings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Docmost needs a durable application secret, and PostgreSQL must receive one identical password from both the database service and the application connection string.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Generate hexadecimal values so the database password is safe to place in a connection URL. Then create a deployment directory that your <code>sudo<\/code> account can enter while the secret file itself stays root-readable only.<\/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\ncd \/opt\/docmost\nsudo vi .env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In <code>vi<\/code>, create <code>\/opt\/docmost\/.env<\/code>. Use the first random value for <code>APP_SECRET<\/code>, the second for <code>DB_PASSWORD<\/code>, and replace <code>YOUR_DOMAIN<\/code> with the real hostname:<\/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 access to 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\">The <code>openssl rand -hex 32<\/code> command creates a 64-character secret, which is longer than Docmost&#8217;s minimum. <code>APP_URL<\/code> must match the HTTPS hostname exactly, including any subdomain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Add Caddy and the Compose stack<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Caddy handles certificate issuance and WebSocket proxying, while the Compose volumes keep the wiki&#8217;s data when containers are recreated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the Caddy configuration first. The <a href=\"https:\/\/docmost.com\/docs\/self-hosting\/reverse-proxy\/caddy\" target=\"_blank\" rel=\"noopener\">official Docmost Caddy guide<\/a> uses this service-name proxy pattern for HTTPS deployments.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo vi \/opt\/docmost\/Caddyfile<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Enter the following 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\">Now create <code>\/opt\/docmost\/docker-compose.yml<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo vi \/opt\/docmost\/docker-compose.yml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Paste this 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,Z\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>:Z<\/code> suffix lets Docker apply an SELinux label to the Caddy bind mount without turning SELinux off. Binding Docmost to <code>127.0.0.1<\/code> prevents direct public access to port 3000; Caddy reaches the service through the private Compose network. The named volumes preserve pages, uploads, database records, Redis data, and certificates.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Open firewalld and launch Docmost<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: The host firewall should expose only the web endpoints required by Caddy, while PostgreSQL, Redis, and the application remain unreachable from the internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Install and enable firewalld, preserve SSH access, and open HTTP and HTTPS for web traffic and certificate issuance:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf install -y firewalld\nsudo systemctl enable --now firewalld\nsudo firewall-cmd --permanent --zone=public --add-service=ssh\nsudo firewall-cmd --permanent --zone=public --add-service=http\nsudo firewall-cmd --permanent --zone=public --add-service=https\nsudo firewall-cmd --reload\nsudo firewall-cmd --zone=public --list-services<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You should see <code>ssh<\/code>, <code>http<\/code>, and <code>https<\/code>. If SSH listens on a custom port, add that port instead of the <code>ssh<\/code> service before enabling the firewall. Confirm the rendered Compose configuration, download 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; only Caddy should show 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        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 container names. If a service keeps restarting, 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\">Why: An HTTPS request through the domain checks DNS, firewalld, Caddy&#8217;s certificate, the reverse proxy, and Docmost&#8217;s listener in one pass.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsS -o \/dev\/null -w 'HTTP %{http_code}\\n' https:\/\/YOUR_DOMAIN<\/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 setup page should appear. Enter a workspace name, administrator details, and a unique strong password, then create a page and edit it in a second browser tab to check the collaborative editor.<\/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 contain a repeating restart loop, a PostgreSQL authentication error, or an ACME certificate failure.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Run Docmost privately\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Rocky Linux VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Run Docmost privately<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy a Docker-ready Rocky Linux VPS for a collaborative documentation workspace behind HTTPS.<\/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>docker: command not found<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Docker repository package installation did not complete, or the shell has not refreshed its command path. Check the installation transaction and retry the package command; do not install the unrelated <code>podman-docker<\/code> compatibility package alongside Docker Engine.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf list installed 'docker*' containerd.io docker-compose-plugin\nsudo systemctl status docker --no-pager<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the list is empty, rerun Step 2 and check the DNF error rather than starting the Compose stack.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>WARNING: The \"DB_PASSWORD\" variable is not set<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Compose cannot read the <code>.env<\/code> file, or the variable name in that file does not match the name in <code>docker-compose.yml<\/code>. Confirm the file location and permissions, then validate the project from its directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo grep -E '^(APP_URL|APP_SECRET|DB_PASSWORD)=' .env\nsudo docker compose config --quiet<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The grep output should show all three keys without exposing the values in this guide. If a key is missing, edit <code>.env<\/code> and recreate the affected services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Caddy returns <code>502 Bad Gateway<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Caddy is reachable, but Docmost is still starting or has exited because a dependency or environment value is invalid. Check the service states and recent application logs:<\/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<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Correct the reported error, then run <code>sudo docker compose up -d<\/code> again. Do not delete the named volumes while diagnosing a live installation.<\/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 domain may still point to another address, or port 80\/443 may be blocked by the VPS provider firewall. Verify that <code>YOUR_DOMAIN<\/code> resolves to <code>SERVER_IP<\/code>, allow both ports in the provider firewall, and confirm the host rules with <code>sudo firewall-cmd --zone=public --list-services<\/code>.<\/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 port 3000 bound to <code>127.0.0.1<\/code>; never publish PostgreSQL or Redis ports for routine web access.<\/li>\n\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 logs afterward.<\/li>\n\n\n<li>Keep <code>.env<\/code> at mode <code>600<\/code> and use a different long password for the Docmost administrator account.<\/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 an IP address instead of a domain?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can test the application over an IP address, but Caddy cannot obtain a normal public certificate for that address. A domain is the practical choice for a secure public workspace and reliable browser WebSocket connections.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why is port 3000 bound to loopback?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Docmost does not need to be directly exposed because Caddy is the public entry point. The loopback binding removes a second unauthenticated route and leaves TLS, certificate handling, and web access policy in one place.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Where is the workspace data stored?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Uploaded files are in the <code>docmost<\/code> volume, PostgreSQL records are in <code>db_data<\/code>, and Redis persistence is in <code>redis_data<\/code>. Caddy&#8217;s certificate state uses <code>caddy_data<\/code> and <code>caddy_config<\/code>; include all five volumes in your backup plan.<\/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 named volumes remain unless you add <code>-v<\/code>. Start the deployment again from <code>\/opt\/docmost<\/code> with <code>sudo docker compose up -d<\/code>; never use <code>down -v<\/code> on a workspace whose data you need.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I use an IP address instead of a domain?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can test the application over an IP address, but Caddy cannot obtain a normal public certificate for that address. A domain is the practical choice for a secure public workspace and reliable browser WebSocket connections.\"}}, {\"@type\": \"Question\", \"name\": \"Why is port 3000 bound to loopback?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Docmost does not need to be directly exposed because Caddy is the public entry point. The loopback binding removes a second unauthenticated route and leaves TLS, certificate handling, and web access policy in one place.\"}}, {\"@type\": \"Question\", \"name\": \"Where is the workspace data stored?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Uploaded files are in the `docmost` volume, PostgreSQL records are in `db_data`, and Redis persistence is in `redis_data`. Caddy's certificate state uses `caddy_data` and `caddy_config`; include all five volumes in your backup plan.\"}}, {\"@type\": \"Question\", \"name\": \"What happens if I run `docker compose down`?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The containers and network stop, but named volumes remain unless you add `-v`. Start the deployment again from `\/opt\/docmost` with `sudo docker compose up -d`; never use `down -v` on a workspace whose data you need.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on Rocky Linux 10 with PostgreSQL, Redis, Caddy HTTPS, firewalld, and checks for a secure private wiki in 15 minutes.","protected":false},"author":1,"featured_media":1114,"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,99,139],"class_list":["post-1113","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-docker","tag-docmost","tag-rocky-linux-10","tag-self-hosting","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1113","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=1113"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1113\/revisions"}],"predecessor-version":[{"id":4094,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1113\/revisions\/4094"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1114"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}