{"id":44,"date":"2023-09-28T21:51:36","date_gmt":"2023-09-28T14:51:36","guid":{"rendered":"http:\/\/nitirat.ddns.net\/wordpress\/?p=44"},"modified":"2024-08-29T22:22:12","modified_gmt":"2024-08-29T15:22:12","slug":"install-the-apache-web-server-on-ubuntu-20-04","status":"publish","type":"post","link":"http:\/\/nitirat.ddns.net\/wordpress\/?p=44","title":{"rendered":"Install the Apache Web Server on Ubuntu 20.04"},"content":{"rendered":"\n<p>The Apache HTTP server is the most widely-used web server in the world. It provides many powerful features including dynamically loadable modules, robust media support, and extensive integration with other popular software.<\/p>\n\n\n\n<p>In this guide, we\u2019ll explain how to install an Apache web server on your Ubuntu 20.04 server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"prerequisites\">Prerequisites<\/h2>\n\n\n\n<p>Before you begin this guide, you should have a regular, non-root user with sudo privileges configured on your server. Additionally, you will need to enable a basic firewall to block non-essential ports. You can learn how to configure a regular user account and set up a firewall for your server by following our&nbsp;<a href=\"https:\/\/www.digitalocean.com\/community\/tutorials\/initial-server-setup-with-ubuntu-20-04\">Initial server setup guide for Ubuntu 20.04<\/a>.<\/p>\n\n\n\n<p>When you have an account available, log in as your non-root user to begin.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-1-\u2014-installing-apache\">Step 1 \u2014 Installing Apache<\/h2>\n\n\n\n<p>Apache is available within Ubuntu\u2019s default software repositories, making it possible to install it using conventional package management tools.<\/p>\n\n\n\n<p>Let\u2019s begin by updating the local package index to reflect the latest upstream changes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Then, install the&nbsp;<code>apache2<\/code>&nbsp;package:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>After confirming the installation,&nbsp;<code>apt<\/code>&nbsp;will install Apache and all required dependencies.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-2-\u2014-adjusting-the-firewall\">Step 2 \u2014 Adjusting the Firewall<\/h2>\n\n\n\n<p>Before testing Apache, it\u2019s necessary to modify the firewall settings to allow outside access to the default web ports. Assuming that you followed the instructions in the prerequisites, you should have a UFW firewall configured to restrict access to your server.<\/p>\n\n\n\n<p>During installation, Apache registers itself with UFW to provide a few application profiles that can be used to enable or disable access to Apache through the firewall.<\/p>\n\n\n\n<p>List the&nbsp;<code>ufw<\/code>&nbsp;application profiles by typing:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw app list\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>You will receive a list of the application profiles:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>OutputAvailable applications:\n  Apache\n  Apache Full\n  Apache Secure\n  OpenSSH\n<\/code><\/pre>\n\n\n\n<p>As indicated by the output, there are three profiles available for Apache:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Apache<\/strong>: This profile opens only port 80 (normal, unencrypted web traffic)<\/li>\n\n\n\n<li><strong>Apache Full<\/strong>: This profile opens both port 80 (normal, unencrypted web traffic) and port 443 (TLS\/SSL encrypted traffic)<\/li>\n\n\n\n<li><strong>Apache Secure<\/strong>: This profile opens only port 443 (TLS\/SSL encrypted traffic)<\/li>\n<\/ul>\n\n\n\n<p>It is recommended that you enable the most restrictive profile that will still allow the traffic you\u2019ve configured. Since we haven\u2019t configured SSL for our server yet in this guide, we will only need to allow traffic on port 80:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw allow 'Apache'\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>You can verify the change by typing:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ufw status\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>The output will provide a list of allowed HTTP traffic:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>OutputStatus: active\n\nTo                         Action      From\n--                         ------      ----\nOpenSSH                    ALLOW       Anywhere                  \nApache                     ALLOW       Anywhere                \nOpenSSH (v6)               ALLOW       Anywhere (v6)             \nApache (v6)                ALLOW       Anywhere (v6)\n<\/code><\/pre>\n\n\n\n<p>As indicated by the output, the profile has been activated to allow access to the Apache web server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-3-\u2014-checking-your-web-server\">Step 3 \u2014 Checking your Web Server<\/h2>\n\n\n\n<p>At the end of the installation process, Ubuntu 20.04 starts Apache. The web server should already be up and running.<\/p>\n\n\n\n<p>Check with the&nbsp;<code>systemd<\/code>&nbsp;init system to make sure the service is running by typing:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl status apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Output\u25cf apache2.service - The Apache HTTP Server\n     Loaded: loaded (\/lib\/systemd\/system\/apache2.service; enabled; vendor preset: enabled)\n     Active: active (running) since Thu 2020-04-23 22:36:30 UTC; 20h ago\n       Docs: https:\/\/httpd.apache.org\/docs\/2.4\/\n   Main PID: 29435 (apache2)\n      Tasks: 55 (limit: 1137)\n     Memory: 8.0M\n     CGroup: \/system.slice\/apache2.service\n             \u251c\u250029435 \/usr\/sbin\/apache2 -k start\n             \u251c\u250029437 \/usr\/sbin\/apache2 -k start\n             \u2514\u250029438 \/usr\/sbin\/apache2 -k start\n\n<\/code><\/pre>\n\n\n\n<p>As confirmed by this output, the service has started successfully. However, the best way to test this is to request a page from Apache.<\/p>\n\n\n\n<p>You can access the default Apache landing page to confirm that the software is running properly through your IP address. If you do not know your server\u2019s IP address, you can get it a few different ways from the command line.<\/p>\n\n\n\n<p>Try typing this at your server\u2019s command prompt:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hostname -I\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>You will get back a few addresses separated by spaces. You can try each in your web browser to determine if they work.<\/p>\n\n\n\n<p>Another option is to use the Icanhazip tool, which should give you your public IP address as read from another location on the internet:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -4 icanhazip.com\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>When you have your server\u2019s IP address, enter it into your browser\u2019s address bar:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>http:&#47;&#47;your_server_ip\n<\/code><\/pre>\n\n\n\n<p>You should see the default Ubuntu 20.04 Apache web page:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/assets.digitalocean.com\/articles\/how-to-install-lamp-ubuntu-16\/small_apache_default.png\" alt=\"Apache default page\"\/><\/figure>\n\n\n\n<p>This page indicates that Apache is working correctly. It also includes some basic information about important Apache files and directory locations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-4-\u2014-managing-the-apache-process\">Step 4 \u2014 Managing the Apache Process<\/h2>\n\n\n\n<p>Now that you have your web server up and running, let\u2019s go over some basic management commands using&nbsp;<code>systemctl<\/code>.<\/p>\n\n\n\n<p>To stop your web server, type:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl stop apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>To start the web server when it is stopped, type:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl start apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>To stop and then start the service again, type:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl restart apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>If you are simply making configuration changes, Apache can often reload without dropping connections. To do this, use this command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl reload apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>By default, Apache is configured to start automatically when the server boots. If this is not what you want, disable this behavior by typing:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl disable apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>To re-enable the service to start up at boot, type:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl enable apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Apache should now start automatically when the server boots again.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-5-\u2014-setting-up-virtual-hosts-recommended\">Step 5 \u2014 Setting Up Virtual Hosts (Recommended)<\/h2>\n\n\n\n<p>When using the Apache web server, you can use&nbsp;<em>virtual hosts<\/em>&nbsp;(similar to server blocks in Nginx) to encapsulate configuration details and host more than one domain from a single server. We will set up a domain called&nbsp;<strong>your_domain<\/strong>, but you should&nbsp;<strong>replace this with your own domain name<\/strong>. If you are setting up a domain name with DigitalOcean, please refer to our&nbsp;<a href=\"https:\/\/www.digitalocean.com\/docs\/networking\/dns\/\">Networking Documentation<\/a>.<\/p>\n\n\n\n<p>Apache on Ubuntu 20.04 has one server block enabled by default that is configured to serve documents from the&nbsp;<code>\/var\/www\/html<\/code>&nbsp;directory. While this works well for a single site, it can become unwieldy if you are hosting multiple sites. Instead of modifying&nbsp;<code>\/var\/www\/html<\/code>, let\u2019s create a directory structure within&nbsp;<code>\/var\/www<\/code>&nbsp;for a&nbsp;<strong>your_domain<\/strong>&nbsp;site, leaving&nbsp;<code>\/var\/www\/html<\/code>&nbsp;in place as the default directory to be served if a client request doesn\u2019t match any other sites.<\/p>\n\n\n\n<p>Create the directory for&nbsp;<strong>your_domain<\/strong>&nbsp;as follows:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mkdir \/var\/www\/your_domain\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Next, assign ownership of the directory with the&nbsp;<code>$USER<\/code>&nbsp;environment variable:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chown -R $USER:$USER \/var\/www\/your_domain\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>The permissions of your web roots should be correct if you haven\u2019t modified your umask value, which sets default file permissions. To ensure that your permissions are correct and allow the owner to read, write, and execute the files while granting only read and execute permissions to groups and others, you can input the following command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chmod -R 755 \/var\/www\/your_domain\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Next, create a sample&nbsp;<code>index.html<\/code>&nbsp;page using&nbsp;<code>nano<\/code>&nbsp;or your favorite editor:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/var\/www\/your_domain\/index.html\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Inside, add the following sample HTML:\/var\/www\/your_domain\/index.html<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;html&gt;\n    &lt;head&gt;\n        &lt;title&gt;Welcome to Your_domain!&lt;\/title&gt;\n    &lt;\/head&gt;\n    &lt;body&gt;\n        &lt;h1&gt;Success!  The your_domain virtual host is working!&lt;\/h1&gt;\n    &lt;\/body&gt;\n&lt;\/html&gt;<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Save and close the file when you are finished.<\/p>\n\n\n\n<p>In order for Apache to serve this content, it\u2019s necessary to create a virtual host file with the correct directives. Instead of modifying the default configuration file located at&nbsp;<code>\/etc\/apache2\/sites-available\/000-default.conf<\/code>&nbsp;directly, let\u2019s make a new one at&nbsp;<code>\/etc\/apache2\/sites-available\/your_domain.conf<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/etc\/apache2\/sites-available\/your_domain.conf\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Paste in the following configuration block, which is similar to the default, but updated for our new directory and domain name:\/etc\/apache2\/sites-available\/your_domain.conf<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;VirtualHost *:80&gt;\n    ServerAdmin webmaster@localhost\n    ServerName your_domain\n    ServerAlias www.your_domain\n    DocumentRoot \/var\/www\/your_domain\n    ErrorLog ${APACHE_LOG_DIR}\/error.log\n    CustomLog ${APACHE_LOG_DIR}\/access.log combined\n&lt;\/VirtualHost&gt;<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Notice that we\u2019ve updated the&nbsp;<code>DocumentRoot<\/code>&nbsp;to our new directory and&nbsp;<code>ServerAdmin<\/code>&nbsp;to an email that the&nbsp;<strong>your_domain<\/strong>&nbsp;site administrator can access. We\u2019ve also added two directives:&nbsp;<code>ServerName<\/code>, which establishes the base domain that should match for this virtual host definition, and&nbsp;<code>ServerAlias<\/code>, which defines further names that should match as if they were the base name.<\/p>\n\n\n\n<p>Save and close the file when you are finished.<\/p>\n\n\n\n<p>Let\u2019s enable the file with the&nbsp;<code>a2ensite<\/code>&nbsp;tool:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo a2ensite your_domain.conf\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Disable the default site defined in&nbsp;<code>000-default.conf<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo a2dissite 000-default.conf\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Next, let\u2019s test for configuration errors:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apache2ctl configtest\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>You should receive the following output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>OutputSyntax OK\n<\/code><\/pre>\n\n\n\n<p>Restart Apache to implement your changes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl restart apache2\n<\/code><\/pre>\n\n\n\n<p>&nbsp;Copy<\/p>\n\n\n\n<p>Apache should now be serving your domain name. You can test this by navigating to&nbsp;<code>http:\/\/your_domain<\/code>, where you should see something like this:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/assets.digitalocean.com\/articles\/apache_virtual_hosts_ubuntu\/vhost_your_domain.png\" alt=\"Apache virtual host example\"\/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-6-\u2013-getting-familiar-with-important-apache-files-and-directories\">Step 6 \u2013 Getting Familiar with Important Apache Files and Directories<\/h2>\n\n\n\n<p>Now that you know how to manage the Apache service itself, you should take a few minutes to familiarize yourself with a few important directories and files.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"content\">Content<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>\/var\/www\/html<\/code>: The actual web content, which by default only consists of the default Apache page you saw earlier, is served out of the&nbsp;<code>\/var\/www\/html<\/code>&nbsp;directory. This can be changed by altering Apache configuration files.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"server-configuration\">Server Configuration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>\/etc\/apache2<\/code>: The Apache configuration directory. All of the Apache configuration files reside here.<\/li>\n\n\n\n<li><code>\/etc\/apache2\/apache2.conf<\/code>: The main Apache configuration file. This can be modified to make changes to the Apache global configuration. This file is responsible for loading many of the other files in the configuration directory.<\/li>\n\n\n\n<li><code>\/etc\/apache2\/ports.conf<\/code>: This file specifies the ports that Apache will listen on. By default, Apache listens on port 80 and additionally listens on port 443 when a module providing SSL capabilities is enabled.<\/li>\n\n\n\n<li><code>\/etc\/apache2\/sites-available\/<\/code>: The directory where per-site virtual hosts can be stored. Apache will not use the configuration files found in this directory unless they are linked to the&nbsp;<code>sites-enabled<\/code>&nbsp;directory. Typically, all server block configuration is done in this directory, and then enabled by linking to the other directory with the&nbsp;<code>a2ensite<\/code>&nbsp;command.<\/li>\n\n\n\n<li><code>\/etc\/apache2\/sites-enabled\/<\/code>: The directory where enabled per-site virtual hosts are stored. Typically, these are created by linking to configuration files found in the&nbsp;<code>sites-available<\/code>&nbsp;directory with the&nbsp;<code>a2ensite<\/code>. Apache reads the configuration files and links found in this directory when it starts or reloads to compile a complete configuration.<\/li>\n\n\n\n<li><code>\/etc\/apache2\/conf-available\/<\/code>,&nbsp;<code>\/etc\/apache2\/conf-enabled\/<\/code>: These directories have the same relationship as the&nbsp;<code>sites-available<\/code>&nbsp;and&nbsp;<code>sites-enabled<\/code>&nbsp;directories, but are used to store configuration fragments that do not belong in a virtual host. Files in the&nbsp;<code>conf-available<\/code>&nbsp;directory can be enabled with the&nbsp;<code>a2enconf<\/code>&nbsp;command and disabled with the&nbsp;<code>a2disconf<\/code>&nbsp;command.<\/li>\n\n\n\n<li><code>\/etc\/apache2\/mods-available\/<\/code>,&nbsp;<code>\/etc\/apache2\/mods-enabled\/<\/code>: These directories contain the available and enabled modules, respectively. Files ending in&nbsp;<code>.load<\/code>&nbsp;contain fragments to load specific modules, while files ending in&nbsp;<code>.conf<\/code>&nbsp;contain the configuration for those modules. Modules can be enabled and disabled using the&nbsp;<code>a2enmod<\/code>&nbsp;and&nbsp;<code>a2dismod<\/code>&nbsp;command.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"server-logs\">Server Logs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>\/var\/log\/apache2\/access.log<\/code>: By default, every request to your web server is recorded in this log file unless Apache is configured to do otherwise.<\/li>\n\n\n\n<li><code>\/var\/log\/apache2\/error.log<\/code>: By default, all errors are recorded in this file. The&nbsp;<code>LogLevel<\/code>&nbsp;directive in the Apache configuration specifies how much detail the error logs will contain.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>The Apache HTTP server is the most widely-used web server in the world. It provides many powerful features including dynamically loadable modules, robust media support, and extensive integration with other popular software. In this guide, we\u2019ll explain how to install an Apache web server on your Ubuntu 20.04 server. Prerequisites Before you begin this guide, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":119,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[6],"tags":[],"class_list":["post-44","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ubuntu"],"_links":{"self":[{"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=44"}],"version-history":[{"count":1,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/44\/revisions"}],"predecessor-version":[{"id":45,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/44\/revisions\/45"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=\/wp\/v2\/media\/119"}],"wp:attachment":[{"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nitirat.ddns.net\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}