{"id":1129,"date":"2026-11-20T09:00:00","date_gmt":"2026-11-20T09:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1129"},"modified":"2026-11-20T09:00:00","modified_gmt":"2026-11-20T09:00:00","slug":"install-drupal-lemp-centos-stream-10","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/20\/install-drupal-lemp-centos-stream-10\/","title":{"rendered":"How to Install Drupal with LEMP on CentOS Stream 10"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Drupal with LEMP on CentOS Stream 10 and finish with a Drupal 11 site served by Nginx, PHP-FPM, and MariaDB in about 25 minutes. You will build the stack over SSH, secure the writable directories, add HTTPS, and finish the setup in Drupal&#8217;s browser installer.<\/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 fresh CentOS Stream 10 VPS with at least 2 GB of RAM and 10 GB of free disk space. Media, modules, logs, and backups will need additional room.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a normal account with working <code>sudo<\/code> privileges.<\/li>\n\n\n<li>A public IPv4 address and a domain such as <code>YOUR_DOMAIN<\/code> whose A record points to <code>SERVER_IP<\/code>. The domain is needed for a trusted Let&#8217;s Encrypt certificate.<\/li>\n\n\n<li>A long, unique database password and a separate Drupal administrator password. Replace every uppercase placeholder before executing a command or submitting a form.<\/li>\n\n\n<li>If you need the server first, choose a <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> with root access and CentOS Stream 10 support.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This guide installs Drupal 11.4.8 from the official release archive. Drupal 11 needs PHP 8.3 or newer, MariaDB 10.6 or newer, PDO, and extensions such as XML, GD, cURL, Mbstring, and zlib; see Drupal&#8217;s <a href=\"https:\/\/www.drupal.org\/docs\/getting-started\/system-requirements\" target=\"_blank\" rel=\"noopener\">system requirements<\/a> and the <a href=\"https:\/\/www.drupal.org\/project\/drupal\/releases\/11.4.8\" target=\"_blank\" rel=\"noopener\">11.4.8 release page<\/a> for the supported platform details.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Install Nginx, MariaDB, PHP-FPM, and firewalld<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Install the complete stack from the CentOS Stream repositories so the services, package names, and PHP extensions agree with the operating system.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf update -y\nsudo dnf install -y nginx firewalld mariadb-server php php-cli php-fpm php-mysqlnd php-gd php-mbstring php-xml php-opcache php-curl php-zip php-intl curl tar gzip policycoreutils-python-utils\nsudo systemctl enable --now firewalld nginx mariadb php-fpm\nphp -v\nnginx -v<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The PHP version must start with <code>8.3<\/code>, and both version commands should complete without an error. Nginx serves static files and passes PHP requests to PHP-FPM instead of embedding PHP in the web server.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP 8.3.x (cli) (built: ...)\nnginx version: nginx\/...<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Open SSH and web traffic<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Allow administration and the two web protocols, but do not open MariaDB&#8217;s port because Drupal will use a local database connection.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo 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\">The last command should list <code>ssh<\/code>, <code>http<\/code>, and <code>https<\/code>. If your SSH daemon uses a custom port, add that port before reloading firewalld so the new rules do not cut off your session.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create a private MariaDB database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal should have its own database and local-only account; using the MariaDB administrator in the web application would make a Drupal compromise much more serious.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the hardening assistant and remove anonymous users, the test database, and remote administrative access when prompted:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb-secure-installation<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now create the database with UTF-8 support. Replace <code>YOUR_DB_PASSWORD<\/code> with a strong password that contains no single quote, then save it for the browser installer.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb -e \"CREATE DATABASE drupal CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; CREATE USER 'drupaluser'@'localhost' IDENTIFIED BY 'YOUR_DB_PASSWORD'; GRANT ALL PRIVILEGES ON drupal.* TO 'drupaluser'@'localhost'; FLUSH PRIVILEGES;\"\nsudo mariadb -e \"SELECT VERSION() AS mariadb_version; SHOW DATABASES LIKE 'drupal';\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The result should show a MariaDB version and one database named <code>drupal<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb_version\n10.11.x-MariaDB\nDatabase (drupal)\ndrupal<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Download Drupal and set safe file labels<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The release archive contains Drupal&#8217;s runtime dependencies, so Composer is not needed for this first deployment. Pinning the current 11.4.8 security release also prevents an unattended major-version change during installation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/var\/www\nsudo curl -fL https:\/\/ftp.drupal.org\/files\/projects\/drupal-11.4.8.tar.gz -o \/tmp\/drupal-11.4.8.tar.gz\nsudo tar -tzf \/tmp\/drupal-11.4.8.tar.gz | head -n 1\nsudo tar -xzf \/tmp\/drupal-11.4.8.tar.gz -C \/var\/www\nsudo mv \/var\/www\/drupal-11.4.8 \/var\/www\/drupal\nsudo rm -f \/tmp\/drupal-11.4.8.tar.gz<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The archive check should begin with <code>drupal-11.4.8\/<\/code>. Keep the application code owned by <code>root<\/code>, let the Nginx group read it, and grant Nginx write access only where Drupal needs it during installation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R root:nginx \/var\/www\/drupal\nsudo find \/var\/www\/drupal -type d -exec chmod 750 {} +\nsudo find \/var\/www\/drupal -type f -exec chmod 640 {} +\nsudo install -d -o nginx -g nginx -m 0770 \/var\/www\/drupal\/sites\/default\/files\nsudo cp \/var\/www\/drupal\/sites\/default\/default.settings.php \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chown root:nginx \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chmod 660 \/var\/www\/drupal\/sites\/default\/settings.php\nsudo semanage fcontext -a -t httpd_sys_content_t '\/var\/www\/drupal(\/.*)?'\nsudo semanage fcontext -a -t httpd_sys_rw_content_t '\/var\/www\/drupal\/sites\/default\/files(\/.*)?'\nsudo semanage fcontext -a -t httpd_sys_rw_content_t '\/var\/www\/drupal\/sites\/default\/settings.php'\nsudo restorecon -RFv \/var\/www\/drupal\nsudo setsebool -P httpd_can_network_connect_db 1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The persistent SELinux rules allow content to be read while limiting web-process writes to Drupal&#8217;s files directory and installer settings file. The database boolean permits PHP-FPM to reach MariaDB without disabling SELinux.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Create a dedicated PHP-FPM pool<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A separate pool gives this site its own Unix socket and worker limits, making the Nginx-to-PHP handoff explicit instead of relying on the default Apache-oriented pool.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/php-fpm.d\/drupal.conf &gt;\/dev\/null &lt;&lt;'FPM'\n[drupal]\nuser = nginx\ngroup = nginx\nlisten = \/run\/php-fpm\/drupal.sock\nlisten.owner = nginx\nlisten.group = nginx\nlisten.mode = 0660\npm = dynamic\npm.max_children = 20\npm.start_servers = 2\npm.min_spare_servers = 1\npm.max_spare_servers = 3\npm.max_requests = 500\nFPM\n\nsudo tee \/etc\/php.d\/90-drupal.ini &gt;\/dev\/null &lt;&lt;'INI'\nmemory_limit = 256M\nupload_max_filesize = 64M\npost_max_size = 64M\nmax_execution_time = 120\nINI\n\nsudo php-fpm -t\nsudo systemctl restart php-fpm\nsudo systemctl is-active php-fpm<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The configuration test should report success and the final command should print <code>active<\/code>. The 256 MB memory limit gives Drupal room for its installer and common modules without changing the system&#8217;s global resource policy.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Configure the Nginx server block<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Nginx needs a front-controller rule for Drupal&#8217;s clean URLs, a FastCGI socket, and explicit blocks for executable files that should never be served from the public files directory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remove the package&#8217;s placeholder site if it exists, then create the server block. Replace <code>YOUR_DOMAIN<\/code> and <code>ADMIN_EMAIL<\/code> with real values.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo rm -f \/etc\/nginx\/conf.d\/default.conf\nsudo tee \/etc\/nginx\/conf.d\/drupal.conf &gt;\/dev\/null &lt;&lt;'NGINX'\nserver {\n    listen 80;\n    server_name YOUR_DOMAIN;\n    root \/var\/www\/drupal;\n    index index.php index.html;\n    client_max_body_size 64m;\n\n    location \/ {\n        try_files $uri \/index.php?$query_string;\n    }\n\n    location ~* ^\/sites\/default\/files\/.*\\.php$ {\n        deny all;\n    }\n\n    location ~ \\.php$ {\n        try_files $uri =404;\n        include fastcgi_params;\n        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n        fastcgi_param QUERY_STRING $query_string;\n        fastcgi_pass unix:\/run\/php-fpm\/drupal.sock;\n    }\n\n    location ~* \\.(?:engine|inc|install|make|module|profile|po|sh|sql|theme|twig|tpl|yml)(?:~|\\.sw[op]|\\.bak|\\.orig|\\.save)?$ {\n        deny all;\n    }\n}\nNGINX\n\nsudo nginx -t\nsudo systemctl reload nginx<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Nginx should return <code>syntax is ok<\/code> and <code>test is successful<\/code>. The <code>try_files<\/code> rule sends missing paths to Drupal&#8217;s front controller while still serving images, CSS, and JavaScript directly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Add HTTPS and run the Drupal installer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s Encrypt needs the domain to resolve to this VPS and port 80 to be reachable from the internet. Install Certbot from EPEL, let it update the Nginx block, and force HTTP requests onto HTTPS.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf install -y epel-release\nsudo dnf install -y certbot python3-certbot-nginx\nsudo certbot --nginx --redirect --domain YOUR_DOMAIN --email ADMIN_EMAIL --agree-tos --no-eff-email\nsudo certbot renew --dry-run<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The renewal test should end with a success message. Open <code>https:\/\/YOUR_DOMAIN\/core\/install.php<\/code>, select <code>English<\/code>, choose the <code>Standard<\/code> profile, and select <code>MySQL, MariaDB, or equivalent<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use these database values:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Database name: <code>drupal<\/code><\/li>\n\n\n<li>Database username: <code>drupaluser<\/code><\/li>\n\n\n<li>Database password: <code>YOUR_DB_PASSWORD<\/code><\/li>\n\n\n<li>Database host: <code>localhost<\/code><\/li>\n\n\n<li>Database port: <code>3306<\/code><\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Create a unique administrator username, a long password, and a monitored email address. Drupal will create its tables and redirect you to the site&#8217;s front page when the wizard completes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Drupal LEMP installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Check the service state, Nginx syntax, HTTPS response, and database from SSH, then open the site in a private browser window. These checks catch a broken daemon or virtual host before you start adding content.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active nginx php-fpm mariadb firewalld\nsudo nginx -t\ncurl -fsSI https:\/\/YOUR_DOMAIN\/\nsudo mariadb -e \"SHOW DATABASES LIKE 'drupal';\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected results are four <code>active<\/code> lines, a successful Nginx test, an HTTP <code>200<\/code> or Drupal redirect, and a row named <code>drupal<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>active\nactive\nactive\nactive\nnginx: configuration file \/etc\/nginx\/nginx.conf test is successful\nHTTP\/2 200\ndrupal<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In Drupal, open <strong>Manage \u2192 Reports \u2192 Status report<\/strong> and fix any warning about trusted hosts, PHP extensions, or file permissions.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Launch your Drupal server\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">CentOS Stream VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Launch your Drupal server<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Get root access for a secure Drupal LEMP deployment on CentOS Stream 10.<\/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>502 Bad Gateway<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Nginx cannot reach the PHP-FPM socket, usually because the pool failed to start or the socket path in the two configuration files differs. Confirm the socket and inspect the service log.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ls -l \/run\/php-fpm\/drupal.sock\nsudo grep -E '^(listen|user|group)' \/etc\/php-fpm.d\/drupal.conf\nsudo journalctl -u php-fpm -n 40 --no-pager\nsudo systemctl restart php-fpm nginx<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><code>403 Forbidden<\/code> or the installer says files are not writable<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Unix owner, group mode, or SELinux context is wrong. Restore the labels and recreate only Drupal&#8217;s intended writable directory; do not solve this by making the whole site world-writable.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R root:nginx \/var\/www\/drupal\nsudo install -d -o nginx -g nginx -m 0770 \/var\/www\/drupal\/sites\/default\/files\nsudo restorecon -RFv \/var\/www\/drupal\nsudo systemctl restart php-fpm nginx<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><code>Access denied for user 'drupaluser'@'localhost'<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The password in the installer does not match the local MariaDB account, or the account was created with a different host value. Reset it through the local administrative socket and enter the same value again.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb -e \"ALTER USER 'drupaluser'@'localhost' IDENTIFIED BY 'YOUR_DB_PASSWORD'; FLUSH PRIVILEGES;\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Certbot reports a failed challenge<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The DNS record may still point to another address, or port 80 may be blocked by firewalld or an upstream VPS firewall. Check both the public DNS result and the local service before retrying.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-cmd --zone=public --list-services\ncurl -I http:\/\/YOUR_DOMAIN\/\nsudo certbot --nginx --redirect --domain YOUR_DOMAIN<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>After the web installer finishes, make <code>settings.php<\/code> read-only and restore its normal SELinux label:<\/li>\n\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>  sudo chmod 640 \/var\/www\/drupal\/sites\/default\/settings.php\n  sudo chown root:nginx \/var\/www\/drupal\/sites\/default\/settings.php\n  sudo restorecon -v \/var\/www\/drupal\/sites\/default\/settings.php<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Add <code>YOUR_DOMAIN<\/code> and any deliberate <code>www<\/code> alias to Drupal&#8217;s trusted-host settings in <code>sites\/default\/settings.php<\/code> so unexpected Host headers are rejected.<\/li>\n\n\n<li>Keep MariaDB local-only, back up the database and <code>\/var\/www\/drupal<\/code>, and apply CentOS and Drupal security updates before installing new modules.<\/li>\n\n\n<li>For a repeatable SSH baseline, use VPSLake&#8217;s <a href=\"https:\/\/vpslake.com\/sshd-hardening-generator\">SSH hardening generator<\/a>.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does CentOS Stream 10 support Drupal 11?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Drupal 11 requires PHP 8.3 or newer and MariaDB 10.6 or newer, and the packages installed here provide those requirements. The PHP extension list can grow when you add contributed modules, so review a module&#8217;s requirements before enabling it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why use a separate PHP-FPM pool for Nginx?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The pool gives Drupal a predictable socket, worker limits, and <code>nginx<\/code> ownership. It also avoids accidentally pointing the server block at a pool intended for a different web server or application.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I install Drupal using only the VPS IP address?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can use the IP for a temporary HTTP test, but a domain is the practical production choice. Certbot needs a domain that resolves publicly, and Drupal&#8217;s trusted-host protection is easier to configure with a stable hostname.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need Composer for this tutorial?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The official release archive is enough for a single-site installation. Composer is the better long-term workflow when you manage Drupal core, modules, and themes in a project repository, so use it for repeatable deployments and controlled updates.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does CentOS Stream 10 support Drupal 11?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. Drupal 11 requires PHP 8.3 or newer and MariaDB 10.6 or newer, and the packages installed here provide those requirements. The PHP extension list can grow when you add contributed modules, so review a module's requirements before enabling it.\"}}, {\"@type\": \"Question\", \"name\": \"Why use a separate PHP-FPM pool for Nginx?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The pool gives Drupal a predictable socket, worker limits, and `nginx` ownership. It also avoids accidentally pointing the server block at a pool intended for a different web server or application.\"}}, {\"@type\": \"Question\", \"name\": \"Can I install Drupal using only the VPS IP address?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can use the IP for a temporary HTTP test, but a domain is the practical production choice. Certbot needs a domain that resolves publicly, and Drupal's trusted-host protection is easier to configure with a stable hostname.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need Composer for this tutorial?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The official release archive is enough for a single-site installation. Composer is the better long-term workflow when you manage Drupal core, modules, and themes in a project repository, so use it for repeatable deployments and controlled updates.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Drupal with LEMP on CentOS Stream 10 using Nginx, MariaDB, PHP-FPM, firewalld, SELinux, HTTPS, and secure clean URLs, checks, and fixes.","protected":false},"author":1,"featured_media":1130,"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":[110,140,73,125,72],"class_list":["post-1129","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-centos-stream-10","tag-drupal","tag-mariadb","tag-nginx","tag-php","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1129","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=1129"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1129\/revisions"}],"predecessor-version":[{"id":4126,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1129\/revisions\/4126"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1130"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}