{"id":1107,"date":"2026-11-17T13:00:00","date_gmt":"2026-11-17T13:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1107"},"modified":"2026-11-17T13:00:00","modified_gmt":"2026-11-17T13:00:00","slug":"install-docmost-docker-almalinux-9","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/17\/install-docmost-docker-almalinux-9\/","title":{"rendered":"How to Install Docmost with Docker on AlmaLinux 9"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Docmost using Docker on AlmaLinux 9 to run a collaborative wiki with PostgreSQL, Redis, and automatic HTTPS. This guide takes about 15 minutes on a fresh VPS and leaves Docmost\u2019s application port private behind Caddy.<\/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 AlmaLinux 9 server with at least 2 GB of RAM and 10 GB of free disk space. Increase those resources if you expect a large team or many file uploads.<\/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 the hostname to request a trusted TLS certificate.<\/li>\n\n\n<li>Inbound TCP 80 and 443 allowed in both the VPS provider firewall and the host firewall. Port 3000 will remain bound to loopback.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> if you need an AlmaLinux server with root access.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The commands below assume a non-root SSH account, so they use <code>sudo<\/code>. If you are logged in as <code>root<\/code>, omit <code>sudo<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm AlmaLinux 9 and update the host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Confirming the release and CPU architecture prevents an Enterprise Linux repository mismatch before Docker is installed.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. \/etc\/os-release\nprintf '%s\\n' \"$PRETTY_NAME\"\nuname -m\nsudo dnf upgrade -y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The release should identify AlmaLinux 9, and the architecture should be <code>x86_64<\/code> or <code>aarch64<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>AlmaLinux 9.x (...)\nx86_64<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The minor release and kernel details change as AlmaLinux publishes updates. If DNF reports a mirror, DNS, or signature problem, correct that first instead of continuing with a partial upgrade.<\/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 containers, while the Compose plugin manages Docmost and its PostgreSQL, Redis, and Caddy services as one stack.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a fresh VPS, remove packages that can conflict with Docker\u2019s runtime. Skip this removal if the machine already hosts important Podman containers; inspect those workloads before changing the runtime.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf remove -y docker \\\n  docker-client docker-client-latest docker-common docker-latest \\\n  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 uses Docker\u2019s RHEL repository method documented in the official <a href=\"https:\/\/docs.docker.com\/engine\/install\/rhel\/\" target=\"_blank\" rel=\"noopener\">Docker Engine installation guide<\/a>, which is the appropriate package path for AlmaLinux 9. Check the daemon, Compose plugin, and a disposable test 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 resembles this; exact 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\">Do not add your account to the <code>docker<\/code> group unless you deliberately accept its root-equivalent access. Using <code>sudo docker<\/code> keeps that privilege explicit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create the Docmost secrets<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Docmost needs a persistent application secret, and PostgreSQL must use the same database password in both the database service and the application connection string.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Generate values that contain only hexadecimal characters, so they can safely appear in the database URL. Then create a directory for the deployment:<\/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\ncd \/opt\/docmost\nsudo vi .env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Create <code>\/opt\/docmost\/.env<\/code> in <code>vi<\/code>. Replace the uppercase placeholders with the two generated values and the domain that will serve Docmost:<\/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 lock it down 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\"><code>APP_SECRET<\/code> must be at least 32 characters; the command above creates 64. <code>APP_URL<\/code> must match the HTTPS address users will enter, including the subdomain if you use one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Define Docmost and Caddy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Caddy provides HTTPS and forwards WebSocket connections for real-time editing, while Docker\u2019s named volumes keep pages, uploads, and database data after container recreation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First create the reverse-proxy configuration. The <a href=\"https:\/\/docmost.com\/docs\/self-hosting\/reverse-proxy\" target=\"_blank\" rel=\"noopener\">Docmost reverse-proxy documentation<\/a> explains why WebSocket forwarding is required for collaborative editing.<\/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\">Paste this content, changing <code>YOUR_DOMAIN<\/code> to 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 vi \/opt\/docmost\/docker-compose.yml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use this configuration. It follows Docmost\u2019s current Docker service layout and keeps the app\u2019s published port on <code>127.0.0.1<\/code> rather than exposing port 3000 to the internet.<\/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 disabling SELinux. The named volumes are the persistent data boundary: do not remove them when troubleshooting a live installation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Open the web ports and start the stack<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: firewalld should expose only Caddy\u2019s HTTP and HTTPS endpoints; PostgreSQL, Redis, and Docmost stay on Docker\u2019s internal network or loopback.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Install and enable firewalld, then allow the two ports Caddy needs 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 --add-service=http\nsudo firewall-cmd --permanent --add-service=https\nsudo firewall-cmd --reload\nsudo firewall-cmd --list-services<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The last command should include <code>http<\/code> and <code>https<\/code>. Confirm the Compose file and its environment substitutions before pulling images:<\/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>config --quiet<\/code> is silent when the YAML is valid. After the first image download, all four services should report <code>Up<\/code> in output similar to this:<\/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\">Compose may choose different container names. A service that repeatedly restarts needs its logs checked before you proceed.<\/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: Testing the health endpoint through the domain checks DNS, Caddy\u2019s certificate, the reverse proxy, and Docmost\u2019s HTTP listener together.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the check from the server or another machine with DNS access:<\/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 setup page should appear. Enter a workspace name, administrator name, email address, and a strong unique password, then create the workspace and a test page. Creating a page with an attachment is a useful check that both the editor and the storage volume work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a final service check, review recent logs without following them indefinitely:<\/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, a PostgreSQL authentication failure, or an 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\">AlmaLinux VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Host Docmost securely<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy a Docker-ready AlmaLinux VPS for a private 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>No match for argument: docker-ce<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">DNF cannot see Docker\u2019s repository, often because the repository command was skipped or metadata is stale. Confirm that the host is AlmaLinux 9, then refresh the repository and try the package install again:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf config-manager --add-repo https:\/\/download.docker.com\/linux\/rhel\/docker-ce.repo\nsudo dnf clean all\nsudo dnf makecache\nsudo dnf install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Caddy logs <code>permission denied<\/code> for <code>Caddyfile<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On an SELinux-enabled AlmaLinux host, the bind-mounted file needs a container-readable label. Check that the Compose mount ends in <code>:ro,Z<\/code>, then recreate only Caddy so Docker reapplies the label:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose up -d --force-recreate caddy\nsudo docker compose logs --tail=40 caddy<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not disable SELinux to work around this error.<\/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 initializing or the application container may have exited. Inspect the service state and the first error in the dependency logs, fix that error, and restart the stack:<\/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 still resolve to another address, or port 80\/443 may be blocked by the provider firewall or an upstream security group. Confirm that <code>YOUR_DOMAIN<\/code> resolves to <code>SERVER_IP<\/code>, run <code>sudo firewall-cmd --list-services<\/code>, and allow HTTP and HTTPS in every network firewall in front of the VPS.<\/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 it received when its volume was initialized. Restore the original <code>DB_PASSWORD<\/code> in <code>.env<\/code> if it was changed after first startup; do not run <code>docker compose down -v<\/code> on a live workspace because deleting the database volume destroys stored data.<\/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>127.0.0.1:3000<\/code> in the Compose mapping and never publish PostgreSQL or Redis ports.<\/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>Review image changes before applying them. From <code>\/opt\/docmost<\/code>, use <code>sudo docker compose pull<\/code> followed by <code>sudo docker compose up -d<\/code> for a planned update.<\/li>\n\n\n<li>After confirming Docmost works, tighten SSH access with the <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">VPSLake SSH hardening generator<\/a> and keep <code>.env<\/code> readable only by <code>root<\/code>.<\/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. Point the subdomain\u2019s A record to the VPS, 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 and inbound web ports are ready.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does the setup use PostgreSQL and Redis instead of SQLite?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Docmost\u2019s standard Docker deployment expects PostgreSQL for application data and Redis for supporting real-time and cache operations. Keeping those services in the Compose network avoids exposing database ports while preserving their data in named volumes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is port 3000 supposed to be reachable from the internet?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The <code>127.0.0.1:3000:3000<\/code> mapping makes Docmost available to Caddy on the server while preventing direct remote access to the application port. Public requests should arrive at HTTPS on port 443.<\/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\">Run <code>sudo docker compose stop<\/code> from <code>\/opt\/docmost<\/code>. This stops the containers but keeps the named volumes; <code>sudo docker compose start<\/code> brings the same deployment back without repeating workspace setup.<\/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. Point the subdomain\u2019s A record to the VPS, then use that exact hostname in both `APP_URL` and `Caddyfile`. Caddy will request the certificate for the subdomain once DNS and inbound web ports are ready.\"}}, {\"@type\": \"Question\", \"name\": \"Why does the setup use PostgreSQL and Redis instead of SQLite?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Docmost\u2019s standard Docker deployment expects PostgreSQL for application data and Redis for supporting real-time and cache operations. Keeping those services in the Compose network avoids exposing database ports while preserving their data in named volumes.\"}}, {\"@type\": \"Question\", \"name\": \"Is port 3000 supposed to be reachable from the internet?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The `127.0.0.1:3000:3000` mapping makes Docmost available to Caddy on the server while preventing direct remote access to the application port. Public requests should arrive at HTTPS on port 443.\"}}, {\"@type\": \"Question\", \"name\": \"How do I stop Docmost without deleting its data?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Run `sudo docker compose stop` from `\/opt\/docmost`. This stops the containers but keeps the named volumes; `sudo docker compose start` brings the same deployment back without repeating workspace setup.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on AlmaLinux 9 with PostgreSQL, Redis, Caddy HTTPS, firewalld, and checks for a working private wiki in minutes.","protected":false},"author":1,"featured_media":1108,"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":[95,118,138,139],"class_list":["post-1107","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-almalinux-9","tag-docker","tag-docmost","tag-self-hosting","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1107","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=1107"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1107\/revisions"}],"predecessor-version":[{"id":4079,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1107\/revisions\/4079"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1108"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1107"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1107"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}