{"id":9991,"date":"2025-04-08T09:04:02","date_gmt":"2025-04-08T09:04:02","guid":{"rendered":"https:\/\/www.ssdnodes.com\/?p=9991"},"modified":"2025-10-14T09:47:04","modified_gmt":"2025-10-14T09:47:04","slug":"install-lets-encrypt-on-ubuntu-certbot-apache-and-nginx","status":"publish","type":"post","link":"https:\/\/www.ssdnodes.com\/blog\/install-lets-encrypt-on-ubuntu-certbot-apache-and-nginx\/","title":{"rendered":"How To Install Certbot on Ubuntu 24.04: Set Up Let&#8217;s Encrypt for Apache and Nginx"},"content":{"rendered":"<p>Installing Let's Encrypt on Ubuntu may sound a bit daunting at first, but it's actually pretty easy! Thanks to <a href=\"https:\/\/certbot.eff.org\/\" target=\"_blank\" rel=\"noopener\">Certbot<\/a>, you can quickly install a <a href=\"https:\/\/letsencrypt.org\/docs\/\" target=\"_blank\" rel=\"noopener\">Let's Encrypt<\/a> certificate and use it on your Apache and Nginx web servers to secure traffic with SSL\/TLS encryption.<\/p>\n<p>In this article, you'll learn how to install Certbot on Ubuntu 24.04, and use it to install Let's Encrypt certificates and configure them for both Apache and Nginx to use HTTPS instead of <a href=\"https:\/\/www.ssdnodes.com\/blog\/an-introduction-to-the-http-protocol-and-its-role-in-the-web\/\">HTTP<\/a>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10203 size-full\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/1-1.jpg\" alt=\"Install let's encrypt on ubuntu with certbot\" width=\"579\" height=\"386\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/1-1.jpg 579w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/1-1-300x200.jpg 300w\" sizes=\"auto, (max-width: 579px) 100vw, 579px\" \/><\/p>\n<h2>Quick-Start Guide: Install Certbot on Ubuntu 24.04<\/h2>\n<p>If you're looking for the fastest way to install Certbot and set up Let's Encrypt on Ubuntu 24.04, here are the essential commands:<\/p>\n<pre># Update packages and install Certbot\r\nsudo apt update\r\nsudo apt install -y certbot\r\n\r\n# For Apache users\r\nsudo apt install -y python3-certbot-apache\r\nsudo certbot --apache -d example.com\r\n\r\n# For Nginx users\r\nsudo apt install -y python3-certbot-nginx\r\nsudo certbot --nginx -d example.com<\/pre>\n<p>For detailed instructions, including manual installation and configuration options, continue reading below.<\/p>\n<h2>Prerequisites<\/h2>\n<ul>\n<li>To follow this tutorial, you'll need an Ubuntu 24.04 server with <strong>sudo<\/strong> privileges. If you haven't noticed, we offer the most affordable and reliable <a href=\"https:\/\/ssdnodes.com\/\" target=\"_blank\" rel=\"noopener\">Ubuntu servers<\/a> in the world. Our <a href=\"https:\/\/www.ssdnodes.com\/nvme-vps-hosting\/\">NVMe VPS<\/a> options provide lightning-fast performance for your SSL-secured websites.<\/li>\n<\/ul>\n<h2>Step 1: Install Certbot on Ubuntu 24.04<\/h2>\n<p>To install Certbot on Ubuntu 24.04, you'll first need to update your package repositories to ensure you're installing the latest version. Updating your package list refreshes your system's knowledge of available software and their versions, which is an essential first step before installing any new application:<\/p>\n<pre><code>sudo apt update<\/code><\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-12525\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/install-latest-certbot-on-ubuntu-2.webp\" alt=\"install latest certbot on ubuntu\" width=\"700\" height=\"520\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/install-latest-certbot-on-ubuntu-2.webp 700w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/install-latest-certbot-on-ubuntu-2-300x223.webp 300w\" sizes=\"auto, (max-width: 700px) 100vw, 700px\" \/><\/p>\n<p>Next, use the <code>apt<\/code> command to install <code>certbot<\/code>:<\/p>\n<pre><code>sudo apt install -y certbot<\/code><\/pre>\n<p>The Certbot command line tool will automate the process of getting and installing a Let's Encrypt certificate that you can use with Apache and Nginx servers, valid for 90 days, with the possibility of an automated renewal.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-12527\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/sudo-apt-install-y-certbot_.webp\" alt=\"sudo apt install -y certbot\" width=\"700\" height=\"514\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/sudo-apt-install-y-certbot_.webp 700w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/sudo-apt-install-y-certbot_-300x220.webp 300w\" sizes=\"auto, (max-width: 700px) 100vw, 700px\" \/><\/p>\n<h3>Note<\/h3>\n<p>Before proceeding with certificate installation, ensure that TCP ports 80 (HTTP) and 443 (HTTPS) are open on your server's <a href=\"https:\/\/www.ssdnodes.com\/blog\/vps-security-critical-steps-to-secure-vps-servers\/\">firewall<\/a>. These ports are essential for the Let's Encrypt validation process - port 80 allows the initial domain verification challenge to complete successfully, while port 443 is needed for serving encrypted HTTPS traffic once your certificate is installed.<\/p>\n<h2>Step 2: Install a Let\u2019s Encrypt Certificate Using Certbot<\/h2>\n<p>To create a Let\u2019s Encrypt certificate with <code>certbot<\/code> on Ubuntu, you\u2019ll use the following command structure:<\/p>\n<pre><code>sudo certbot certonly --webroot --webroot-path WEB_SERVER_ROOT_PATH -m EMAIL -d DOMAIN --agree-tos -n<\/code><\/pre>\n<p>Here is what each part of the preceding command means:<\/p>\n<ul>\n<li><code>certonly<\/code>: (certificate only) used to just obtain the certificate without installing it anywhere.<\/li>\n<li><code>--webroot<\/code>: An option that is used here to keep the web server running while Certbot runs, since we\u2019re already running a local web server, and don't want to stop it during the certificate issuance process.<\/li>\n<li><code>--webroot-path<\/code> or <code>-w<\/code>: Defines the top-level directory (\u201cweb root\u201d) containing the files served by your webserver. Note that the web root path must be the path on which files from the domain are served. In our example, it's the web root path from which our <code>http:\/\/www.example.com<\/code> URL serves files.<\/li>\n<li><code>--mail<\/code> or <code>-m<\/code> : The email which will be used by the certificate authority to alert you when a domain will expire.<\/li>\n<li><code>--domain<\/code> or <code>-d<\/code>: The domain name you\u2019ll use to access the server by.<code>--agree-tos<\/code>: Confirms our agreement to the ACME server's subscriber agreement.<\/li>\n<li><code>--non-interactive<\/code> or <code>-n<\/code> is used to execute the command without ever asking for user input or prompts.<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-12528\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/setup-lets-encrypt-certificate-with-certbot-on-ubuntu-24.04_.webp\" alt=\"setup let's encrypt certificate with certbot on ubuntu 24.04\" width=\"700\" height=\"343\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/setup-lets-encrypt-certificate-with-certbot-on-ubuntu-24.04_.webp 700w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2025\/04\/setup-lets-encrypt-certificate-with-certbot-on-ubuntu-24.04_-300x147.webp 300w\" sizes=\"auto, (max-width: 700px) 100vw, 700px\" \/><\/p>\n<p>Now that you are familiar with the certbot options and actions, you can form and execute a certbot command to create a certificate. For example, you can use the following command, making sure to set the appropriate values for your case:<\/p>\n<pre><code>sudo certbot certonly --webroot --webroot-path \/var\/www\/html\/ -m devops@example.com -d www.example.com --agree-tos -n<\/code><\/pre>\n<p>Once the command is executed, the following two files will be automatically created under the respective subdirectories as follows:<\/p>\n<ul>\n<li>The private key: <code>\/etc\/letsencrypt\/live\/www.example.com\/privkey.pem<\/code><\/li>\n<li>The certificate: <code>\/etc\/letsencrypt\/live\/www.example.com\/fullchain.pem<\/code><\/li>\n<\/ul>\n<p>Now that you have your Let's Encrypt private key file and your certificate file, you can install your certificate on your web server.<\/p>\n<h3>\"Only Domain Names Are Supported, Not IP Addresses\" Certbot Error<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10091\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/only-domain-names-1024x456.png\" alt=\"Only domain names are supported, not IP addresses\" width=\"700\" height=\"312\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/only-domain-names-1024x456.png 1024w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/only-domain-names-300x134.png 300w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/only-domain-names-768x342.png 768w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/only-domain-names-1536x684.png 1536w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/only-domain-names.png 2048w\" sizes=\"auto, (max-width: 700px) 100vw, 700px\" \/><\/p>\n<p>The \"Only domain names are supported, not IP addresses\" error in Certbot occurs because Let\u2019s Encrypt does not issue SSL certificates for IP addresses. Certificates are only provided for fully qualified domain names (FQDNs). To resolve this, ensure you are using a valid domain name instead of an IP address when requesting a certificate. Register a domain if needed.<\/p>\n<h2>Step 3: Configuring Apache with Let's Encrypt Certificates<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10205 size-full\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/2-1.jpg\" alt=\"apache let's encrypt on ubuntu\" width=\"579\" height=\"386\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/2-1.jpg 579w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/2-1-300x200.jpg 300w\" sizes=\"auto, (max-width: 579px) 100vw, 579px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Now that you\u2019ve created a Let\u2019s Encrypt certificate, you can configure your Apache server to use it and enable HTTPS on your website.<\/p>\n<p>First, you'll need to modify Apache's default configuration file to integrate your newly acquired Let's Encrypt SSL certificate. This configuration file controls how Apache handles incoming requests and determines which virtual hosts use HTTPS encryption:<\/p>\n<pre><code>sudo nano \/etc\/apache2\/sites-enabled\/000-default.conf<\/code><\/pre>\n<p>Make sure you set up a domain, and then replace the key and the certificate paths with the Let\u2019s Encrypt private key file and the certificate file (the changes you have to make are highlighted in <mark>yellow<\/mark> in the code below):<\/p>\n<pre><code>&lt;VirtualHost *:80&gt;\r\n        Define servername <mark>www.example.com<\/mark>\r\n        ServerName ${SERVERNAME}\r\n        RewriteEngine on\r\n        RewriteRule ^\/.*$ https:\/\/\\${SERVERNAME}%{SCRIPT_FILENAME}?%{QUERY_STRING} [R=301]\r\n        ErrorLog ${APACHE_LOG_DIR}\/error.log\r\n        CustomLog ${APACHE_LOG_DIR}\/access.log combined\r\n&lt;\/VirtualHost&gt;\r\n&lt;VirtualHost *:443&gt;\r\n        SSLEngine On\r\n        SSLCertificateFile <mark>\/etc\/letsencrypt\/live\/www.example.com\/fullchain.pem<\/mark>\r\n        SSLCertificateKeyFile <mark>\/etc\/letsencrypt\/live\/www.example.com\/privkey.pem<\/mark>\r\n        ServerName ${SERVERNAME}\r\n        DocumentRoot \/var\/www\/html\r\n        ErrorLog ${APACHE_LOG_DIR}\/error.log\r\n        CustomLog ${APACHE_LOG_DIR}\/access.log combined\r\n&lt;\/VirtualHost&gt;<\/code><\/pre>\n<p>Here, you set the <code>SSLCertificateFile<\/code> directive to the path of the Let\u2019s Encrypt certificate file, and you set the <code>SSLCertificateKeyFile<\/code> directive to the private key\u2019s path.<br \/>\nNext, test for configuration errors:<\/p>\n<pre><code>sudo apache2ctl configtest<\/code><\/pre>\n<p>You should receive an output that contains the text <code>Syntax OK<\/code>, which means you can safely reload Apache, otherwise, you will get a very specific description pointing out the error you have to fix.<br \/>\nNext, restart Apache:<\/p>\n<pre><code>sudo systemctl restart apache2<\/code><\/pre>\n<p>Now, reload your website in the browser. You will notice a secured padlock with a valid certificate message as you can see in the following example, which was taken from the Google Chrome browser:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-10096\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure.webp\" alt=\"Apache let's encrypt success\" width=\"927\" height=\"345\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure.webp 927w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure-300x112.webp 300w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure-768x286.webp 768w\" sizes=\"auto, (max-width: 927px) 100vw, 927px\" \/><\/p>\n<p>With this, you now have HTTPS enabled in your Apache web server, and you can now secure your web traffic, which establishes customer trust and protects both your internal and public data.<\/p>\n<h2>Step 3.2: Configuring Nginx with Let's Encrypt Certificates<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10207 size-full\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/3.jpg\" alt=\"nginx let's encrypt on ubuntu\" width=\"579\" height=\"386\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/3.jpg 579w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/3-300x200.jpg 300w\" sizes=\"auto, (max-width: 579px) 100vw, 579px\" \/><\/p>\n<p>To configure your Let\u2019s Encrypt certificate with your NGINX server and enable HTTPS on your website. First, edit NGINX\u2019s default configuration file:<\/p>\n<pre><code>sudo nano \/etc\/nginx\/sites-enabled\/default<\/code><\/pre>\n<p>Set up your domain name. Then replace the private key and the certificate paths with the Let\u2019s Encrypt private key file and the certificate file generated by Certbot (the changes you have to make are highlighted in <mark>yellow<\/mark> in the code below):<\/p>\n<pre><code>server {\r\n   listen 80;\r\n   listen [::]:80;\r\n   server_name <mark>www.example.com<\/mark>;\r\n   access_log off;\r\n   location \/ {\r\n         rewrite ^ https:\/\/$host$request_uri? permanent;\r\n   }\r\n}\r\n\r\nserver {\r\n    listen 443 ssl;\r\n    listen [::]:443 ssl;\r\n    server_name <mark>www.example.com<\/mark>;\r\n    root \/var\/www\/html;\r\n    index index.php index.html index.htm index.nginx-debian.html;\r\n    autoindex off;\r\n    ssl_certificate <mark>\/etc\/letsencrypt\/live\/www.example.com\/fullchain.pem<\/mark>;\r\n    ssl_certificate_key <mark>\/etc\/letsencrypt\/live\/www.example.com\/privkey.pem<\/mark>;\r\n    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;\r\n    ssl_ciphers HIGH:!aNULL:!MD5;\r\n\r\n    location ~ \\.php$ {\r\n         include snippets\/fastcgi-php.conf;\r\n         fastcgi_pass unix:\/var\/run\/php\/php-fpm.sock;\r\n         fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\r\n         include fastcgi_params;\r\n    }\r\n}<\/code><\/pre>\n<p>Here, you set the <code>ssl_certificate<\/code> directive to the Let\u2019s Encrypt certificate file path you created earlier, and the <code>ssl_certificate_key<\/code> directive to the Let\u2019s Encrypt private key file path.<br \/>\nWith the configuration file modified, check for syntax errors in it using the following command:<\/p>\n<pre><code>sudo nginx -t<\/code><\/pre>\n<p>The output should let you know that the configuration file test is successful.<\/p>\n<p>Now, restart NGINX:<\/p>\n<pre><code>sudo systemctl restart nginx<\/code><\/pre>\n<p>Reload your browser and you will notice a secured padlock with a valid certificate message.<\/p>\n<h2>Step 4: Verifying Your Let's Encrypt Certificate Information<\/h2>\n<p>In the pop-up that comes up when clicking the padlock or settings icon on the left side of the URL, click on <strong>\"Certificate is secure\"<\/strong>\u00a0or <strong>\"Connection is Secure\"<\/strong> depending on your browser. This will give you detailed information on the CA certificate:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-10097 size-full\" src=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure_nginx.webp\" alt=\"Successful install of let's encrypt on ubuntu\" width=\"541\" height=\"666\" srcset=\"https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure_nginx.webp 541w, https:\/\/www.ssdnodes.com\/wp-content\/uploads\/2024\/07\/secure_nginx-244x300.webp 244w\" sizes=\"auto, (max-width: 541px) 100vw, 541px\" \/><\/p>\n<h3>Congrats!<\/h3>\n<p>Your Ubuntu server's Apache or Nginx web server has become CA certified with Let's Encrypt, and you can now securely transfer data through HTTPS, and protect your online transactions, and with best security practices, you can handle paid subscriptions, eCommerce orders, memberships, or charity and online fundraising.<\/p>\n<h2>Installing a non-Let's-Encrypt CA Certificates<\/h2>\n<p>If you are looking to install a non-Let's-Encrypt CA Certificate you'll generally need to do the following:<\/p>\n<h3>1) Creating a Certificate Signing Request (CSR)<\/h3>\n<p>The CSR contains information (e.g. common name, organization, country) which the Certificate Authority (CA) will use to create your certificate. You generate it on the server where you want to install the certificate. It includes the public key that will be part of your certificate, and is signed with the corresponding private key.<br \/>\nCheck out <strong><a href=\"https:\/\/www.ssdnodes.com\/blog\/create-a-self-signed-certificate-on-ubuntu-for-apache-and-nginx\/\">How to Create a Self-Signed Certificate<\/a>, <\/strong>which describes CSR creation for self-signed certificates (which also applies to CA certificates).<\/p>\n<h3>2) Uploading the CSR to the Certificate Authority (CA)<\/h3>\n<p>Please refer to the documentation of the certificate authority of your choice, and follow their instructions to properly upload your certificate signing request, along with any additional information.<\/p>\n<p>Once the CSR is uploaded, the CA replies with your final certificate ready to use.<\/p>\n<p>&nbsp;<\/p>\n<h2>FAQ<\/h2>\n<h3>What are the differences between Let's Encrypt Certificates vs Paid TLS\/SSL Certificates?<\/h3>\n<p>Although Let's Encrypt provides free SSL certificates. Paid TLS\/SSL certificates often give you additional features such as extended validation and warranty. These paid TLS\/SSL certificates are usually suitable for businesses needing higher trust levels. Both types of certificates encrypt data, but paid SSLs often come with better customer support and additional security features. If you have a business, it is better to use a paid certificate. To get affordable TLS\/SSL certificates, check out our <a href=\"https:\/\/ssdnodes.com\/\" target=\"_blank\" rel=\"noopener\">website<\/a>.<\/p>\n<h3>Is Let's Encrypt safe?<\/h3>\n<p>Yes, Let's Encrypt is safe. It provides the same level of encryption as paid SSL certificates. It is backed by major tech companies and regularly audited for security. Automatic renewals ensure your site stays secure. However, it lacks some advanced features offered by paid certificates. For most websites, Let's Encrypt is a reliable and secure option.<\/p>\n<h3>What to do when Let's Encrypt Root Certificate is expiring?<\/h3>\n<p>Let's Encrypt's root certificate expiration is a known issue. Ensure your systems are updated to trust the new root certificate. Older devices might face connectivity issues. Regularly check for updates and ensure compatibility with new certificates. This change is a normal part of maintaining secure encryption. Proper updates will keep your site secure and trusted.<\/p>\n<h3>How to perform Let's Encrypt renewals with Certbot?<\/h3>\n<p>Renewing Let's Encrypt certificates with Certbot is straightforward. Certbot automatically handles renewals for you. By default, it checks for renewal every day and renews certificates that are within 30 days of expiring. Ensure your server is configured to allow automatic renewals. Manual renewal can be done if needed, but automation is recommended for continuous security.<\/p>\n<h3>Does Let's Encrypt offer Wildcard Certificates?<\/h3>\n<p>Let's Encrypt offers wildcard certificates, securing multiple subdomains under a single domain. This simplifies certificate management. To obtain a wildcard certificate, use DNS-based domain validation. Ensure your DNS provider supports the necessary API calls. Wildcard certificates are beneficial for sites with numerous subdomains, reducing the need for separate certificates for each one.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Effortless SSL\/TLS Encryption: Installing Let\u2019s Encrypt on Ubuntu 24.04 with Certbot for Apache and Nginx.<\/p>\n","protected":false},"author":19,"featured_media":10202,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[18,30],"tags":[202,200,201,185],"class_list":["post-9991","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-tutorials","tag-ca-ssl","tag-https","tag-self-signed-ssl","tag-ubuntu"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts\/9991","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/comments?post=9991"}],"version-history":[{"count":35,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts\/9991\/revisions"}],"predecessor-version":[{"id":12709,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/posts\/9991\/revisions\/12709"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/media\/10202"}],"wp:attachment":[{"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/media?parent=9991"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/categories?post=9991"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ssdnodes.com\/wp-json\/wp\/v2\/tags?post=9991"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}