{"id":1127,"date":"2026-11-20T03:00:00","date_gmt":"2026-11-20T03:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1127"},"modified":"2026-11-20T03:00:00","modified_gmt":"2026-11-20T03:00:00","slug":"install-drupal-lamp-centos-stream-9","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/20\/install-drupal-lamp-centos-stream-9\/","title":{"rendered":"How to Install Drupal with LAMP on CentOS Stream 9"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Install Drupal with LAMP on CentOS Stream 9 and finish with a working Drupal 11 site behind Apache, MariaDB, PHP-FPM, and HTTPS in about 20\u201330 minutes. You will prepare the stack over SSH, then complete Drupal&#8217;s setup in a browser.<\/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 9 VPS with at least 2 GB RAM and 10 GB of free disk space. Composer is not required for this archive-based install, but Drupal and its modules still need room to grow.<\/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> pointing to <code>SERVER_IP<\/code>. The domain is needed for a trusted HTTPS certificate.<\/li>\n\n\n<li>A unique database password and a separate strong Drupal administrator password. Replace every uppercase placeholder before running a command or filling in the installer.<\/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 9 support.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This guide installs Drupal 11.4.7, a production release in the Drupal 11 branch. Drupal 11 needs PHP 8.3 or newer, MariaDB 10.6 or newer, PDO, XML, GD, cURL, OpenSSL, Mbstring, and ZIP; see Drupal&#8217;s <a href=\"https:\/\/www.drupal.org\/docs\/getting-started\/system-requirements\" target=\"_blank\" rel=\"noopener\">system requirements<\/a> for the requirements behind these choices.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Install Apache, MariaDB, PHP-FPM, and required extensions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Enable PHP 8.3 before installing the packages so CentOS Stream 9 does not select its older default PHP stream.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf update -y\nsudo dnf module reset php -y\nsudo dnf module enable php:8.3 -y\nsudo dnf install -y httpd firewalld mariadb-server curl tar policycoreutils-python-utils php php-cli php-fpm php-mysqlnd php-gd php-mbstring php-xml php-opcache php-curl php-zip php-intl\nsudo systemctl enable --now firewalld httpd mariadb php-fpm\nphp -v<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The version line should start with PHP 8.3. The <code>php-fpm<\/code> service handles PHP requests through FastCGI, while Apache serves Drupal&#8217;s static files.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP 8.3.x (cli) (built: ...)<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Allow SSH and web traffic through firewalld<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open only the ports needed for administration and the website; MariaDB stays private on the server.<\/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 final output should include <code>ssh<\/code>, <code>http<\/code>, and <code>https<\/code>. If your SSH daemon listens on a custom port, add that port before reloading the firewall so you do not lose access.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create a private MariaDB database for Drupal<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal should use its own database account rather than MariaDB&#8217;s administrative account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First run the hardening assistant and accept the secure options: remove anonymous users, block remote root login, remove the test database, and reload privilege tables.<\/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\">Create the database with UTF-8 support and restrict the application account to local connections. Replace <code>YOUR_DB_PASSWORD<\/code> with a long password that is not used anywhere else.<\/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\">You should see a MariaDB version and one database row named <code>drupal<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb_version\n11.x.x-MariaDB\nDatabase (drupal)\ndrupal<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Download Drupal and set SELinux-aware permissions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use the official Drupal 11.4.7 archive so the commands install a known production release instead of silently changing the major version later.<\/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.7.tar.gz -o \/tmp\/drupal-11.4.7.tar.gz\nsudo tar -tzf \/tmp\/drupal-11.4.7.tar.gz | head\nsudo tar -xzf \/tmp\/drupal-11.4.7.tar.gz -C \/var\/www\nsudo mv \/var\/www\/drupal-11.4.7 \/var\/www\/drupal\nsudo rm -f \/tmp\/drupal-11.4.7.tar.gz<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The archive listing should begin with <code>drupal-11.4.7\/<\/code>. Keep the application readable by Apache, but make only Drupal&#8217;s public files directory writable by the web process.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R root:apache \/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 apache -g apache -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:apache \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chmod 660 \/var\/www\/drupal\/sites\/default\/settings.php\nsudo chcon -t httpd_sys_rw_content_t \/var\/www\/drupal\/sites\/default\/settings.php\nsudo semanage fcontext -a -t httpd_sys_rw_content_t '\/var\/www\/drupal\/sites\/default\/files(\/.*)?'\nsudo restorecon -Rv \/var\/www\/drupal\/sites\/default\/files<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>chcon<\/code> temporarily lets the installer update <code>settings.php<\/code>; the final hardening step removes that write access. The persistent <code>semanage<\/code> rule lets Drupal create uploads and generated assets without disabling SELinux.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Configure PHP and the Apache virtual host<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Drupal&#8217;s <code>.htaccess<\/code> file provides clean URLs, so Apache must allow overrides for this virtual host.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo 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<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>YOUR_DOMAIN<\/code> and <code>ADMIN_EMAIL<\/code> in the virtual host before saving it.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tee \/etc\/httpd\/conf.d\/drupal.conf &gt;\/dev\/null &lt;&lt;'APACHE'\n&lt;VirtualHost *:80&gt;\n    ServerName YOUR_DOMAIN\n    ServerAdmin ADMIN_EMAIL\n    DocumentRoot \/var\/www\/drupal\n\n    &lt;Directory \/var\/www\/drupal&gt;\n        AllowOverride All\n        Options -Indexes +FollowSymLinks -MultiViews\n        Require all granted\n    &lt;\/Directory&gt;\n\n    DirectoryIndex index.php index.html\n    ErrorLog \/var\/log\/httpd\/drupal_error.log\n    CustomLog \/var\/log\/httpd\/drupal_access.log combined\n&lt;\/VirtualHost&gt;\nAPACHE\n\nsudo apachectl configtest\nsudo systemctl restart php-fpm httpd\nsudo systemctl is-active php-fpm httpd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>apachectl configtest<\/code> must return <code>Syntax OK<\/code>, followed by <code>active<\/code> for both services.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Syntax OK\nactive\nactive<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Add HTTPS before entering administrator credentials<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Point the domain&#8217;s A record to <code>SERVER_IP<\/code> first. Certbot can then validate the site over HTTP and add an Apache HTTPS configuration.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf install -y epel-release\nsudo dnf install -y certbot python3-certbot-apache\nsudo certbot --apache --domain YOUR_DOMAIN<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Choose the redirect-to-HTTPS option when prompted. If you are testing with an IP address only, postpone this step, but use a real domain and TLS before collecting passwords or publishing the site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Run the Drupal web installer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The browser installer creates Drupal&#8217;s tables and the first administrator account after the server-side prerequisites are ready.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/YOUR_DOMAIN\/core\/install.php<\/code> and choose <code>English<\/code>, the <code>Standard<\/code> profile, and <code>MySQL, MariaDB, or equivalent<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Enter 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\">On the site configuration page, use a unique administrator username, a long password, and an email address you monitor. Drupal should redirect you to the new site&#8217;s front page when the installation finishes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Drupal LAMP installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run these checks from SSH, then load the site over HTTPS in a separate browser. Together they verify the services, Apache syntax, the public response, the database, and Drupal&#8217;s required PHP modules.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active httpd php-fpm mariadb firewalld\nsudo apachectl configtest\ncurl -fsSI https:\/\/YOUR_DOMAIN\/\nphp -m | grep -E 'curl|dom|gd|mbstring|PDO|pdo_mysql|xml|zip'\nsudo mariadb -e \"SHOW DATABASES LIKE 'drupal';\"<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>active\nactive\nactive\nactive\nSyntax OK\nHTTP\/2 200\ncurl\ngd\nmbstring\nPDO\npdo_mysql\nxml\nzip\ndrupal<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected results are four <code>active<\/code> lines, <code>Syntax OK<\/code>, an HTTP <code>200<\/code> or Drupal redirect, module names in the PHP check, and one <code>drupal<\/code> database row. In Drupal, open <strong>Manage \u2192 Reports \u2192 Status report<\/strong> and resolve warnings about trusted hosts, permissions, or PHP extensions.<\/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 LAMP deployment on CentOS Stream 9.<\/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>dnf<\/code> cannot enable <code>php:8.3<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The PHP module metadata may be stale, or an older PHP stream may already be installed. Refresh packages and check the available streams; do not mix unrelated PHP package families on the same server.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dnf clean metadata\nsudo dnf makecache\nsudo dnf module list php<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If 8.3 is listed, reset the stream and enable it again, then reinstall the PHP packages from Step 1. Drupal 11.4 cannot run on PHP 8.0 or 8.1.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>403 Forbidden<\/code> or <code>500 Internal Server Error<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The common causes are a missing <code>AllowOverride All<\/code>, incorrect file labels, or a PHP-FPM failure. Read the Apache log, restore the SELinux labels, and validate the virtual host.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo tail -n 40 \/var\/log\/httpd\/drupal_error.log\nsudo restorecon -Rv \/var\/www\/drupal\nsudo apachectl configtest\nsudo systemctl restart php-fpm httpd<\/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 installer password does not match the MariaDB account, or the account was created with a different host value. Reset the local account and enter the same password in Drupal&#8217;s database form.<\/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 server, or port 80 may be blocked by firewalld or the VPS provider&#8217;s network firewall. Confirm the public A record and test the HTTP virtual host before running Certbot again.<\/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 --apache --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 completes, remove write access from the settings file 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:apache \/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>Configure Drupal trusted hosts for <code>YOUR_DOMAIN<\/code> and any deliberate <code>www<\/code> alias in <code>sites\/default\/settings.php<\/code>.<\/li>\n\n\n<li>Keep MariaDB local-only, back up <code>\/var\/www\/drupal<\/code> and the <code>drupal<\/code> database, and take a backup before core or module updates.<\/li>\n\n\n<li>Apply CentOS security updates regularly and use a separate administrator account for routine Drupal work.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Why install Drupal 11 instead of the latest download?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This guide pins Drupal 11.4.7 because it is a supported production branch that matches PHP 8.3 and MariaDB 10.6 or newer. Pinning prevents a later major release with different platform requirements from breaking a repeat installation; review Drupal&#8217;s <a href=\"https:\/\/www.drupal.org\/project\/drupal\/releases\" target=\"_blank\" rel=\"noopener\">official release page<\/a> before upgrading.<\/p>\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 use the IP for a temporary HTTP test, but a domain is the practical choice for production. It makes HTTPS, trusted-host protection, email delivery, and future site migrations much easier to manage.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need Composer for this installation?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The official release archive is enough for this single-site setup. Composer is the better choice when you manage Drupal core and contributed modules as a dependency-controlled project, so plan a Composer-based deployment for a development team.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which directory should Drupal make writable?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Only <code>sites\/default\/files<\/code> should remain writable by Apache after installation because it stores uploads and generated assets. The application code and <code>settings.php<\/code> should be readable but not writable by the web process.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Why install Drupal 11 instead of the latest download?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"This guide pins Drupal 11.4.7 because it is a supported production branch that matches PHP 8.3 and MariaDB 10.6 or newer. Pinning prevents a later major release with different platform requirements from breaking a repeat installation; review Drupal's [official release page](https:\/\/www.drupal.org\/project\/drupal\/releases) before upgrading.\"}}, {\"@type\": \"Question\", \"name\": \"Can I use an IP address instead of a domain?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can use the IP for a temporary HTTP test, but a domain is the practical choice for production. It makes HTTPS, trusted-host protection, email delivery, and future site migrations much easier to manage.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need Composer for this installation?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The official release archive is enough for this single-site setup. Composer is the better choice when you manage Drupal core and contributed modules as a dependency-controlled project, so plan a Composer-based deployment for a development team.\"}}, {\"@type\": \"Question\", \"name\": \"Which directory should Drupal make writable?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Only `sites\/default\/files` should remain writable by Apache after installation because it stores uploads and generated assets. The application code and `settings.php` should be readable but not writable by the web process.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Drupal with LAMP on CentOS Stream 9 using PHP 8.3, MariaDB, Apache, HTTPS, firewalld, and SELinux-safe permissions in about 20 minutes.","protected":false},"author":1,"featured_media":1128,"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":[71,111,140,73,72],"class_list":["post-1127","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-apache","tag-centos-stream-9","tag-drupal","tag-mariadb","tag-php","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1127","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=1127"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1127\/revisions"}],"predecessor-version":[{"id":4121,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1127\/revisions\/4121"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1128"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}