{"id":13626,"date":"2026-02-28T10:31:49","date_gmt":"2026-02-28T05:01:49","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=13626"},"modified":"2026-02-28T10:31:51","modified_gmt":"2026-02-28T05:01:51","slug":"fix-firewalld-on-linux","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/fix-firewalld-on-linux","title":{"rendered":"How to Fix FirewallD on Linux Server Without Breaking SSH Access"},"content":{"rendered":"\n<p><strong>To fix FirewallD on a Linux server<\/strong>, start and enable the service, review logs for errors, remove conflicts with other firewalls (UFW, iptables services, nftables), correct zones and rules, then reload and test. <\/p>\n\n\n\n<p>Use systemctl and firewall cmd to diagnose, validate configuration, and apply permanent changes safely without breaking SSH access. If you\u2019re searching for how to fix FirewallD on Linux Server, this guide walks you through quick wins and deep troubleshooting.<\/p>\n\n\n\n<p>We\u2019ll verify the service, check logs, fix zone\/rule issues, resolve conflicts, and apply best practices so your Linux firewall protects services without blocking legitimate traffic.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"quick-fix-checklist-use-safely-over-ssh\">Quick Fix Checklist (Use Safely Over SSH)<\/h2>\n\n\n\n<p>Before you go deep, try these safe, common fixes. Keep your console open or ensure SSH is allowed (port 22) to avoid lockouts.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1276\" height=\"623\" src=\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/Quick-Fix-Checklist-Use-Safely-Over-SSH.jpg\" alt=\"Fix FirewallD on Linux Server\" class=\"wp-image-19134\" srcset=\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/Quick-Fix-Checklist-Use-Safely-Over-SSH.jpg 1276w, https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/Quick-Fix-Checklist-Use-Safely-Over-SSH-150x73.jpg 150w\" sizes=\"auto, (max-width: 1276px) 100vw, 1276px\" \/><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm service status and start it if needed.<\/li>\n\n\n\n<li>Check logs for immediate error clues.<\/li>\n\n\n\n<li>Disable conflicting firewalls (UFW, iptables services, nftables service).<\/li>\n\n\n\n<li>Validate and reload configuration.<\/li>\n\n\n\n<li>Ensure your interface is in the correct zone and your ports\/services are allowed.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># 1) Service status and start\nsudo systemctl status firewalld\nsudo systemctl start firewalld\nsudo systemctl enable firewalld\n\n# 2) Logs\nsudo journalctl -u firewalld -b --no-pager\n\n# 3) Conflicts (example fixes)\nsudo systemctl stop ufw 2&gt;\/dev\/null; sudo systemctl disable ufw 2&gt;\/dev\/null\nsudo systemctl stop iptables ip6tables ebtables 2&gt;\/dev\/null; sudo systemctl disable iptables ip6tables ebtables 2&gt;\/dev\/null\nsudo systemctl stop nftables 2&gt;\/dev\/null; sudo systemctl disable nftables 2&gt;\/dev\/null\n\n# 4) Validate and reload rules\nsudo firewall-cmd --check-config\nsudo firewall-cmd --reload\n\n# 5) Make sure SSH is allowed\nsudo firewall-cmd --zone=public --add-service=ssh --permanent\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"how-firewalld-works-so-you-dont-fix-the-wrong-thing\">How FirewallD Works (So You Don\u2019t Fix the Wrong Thing)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Zones:<\/strong> Logical trust levels (public, internal, trusted, dmz). Your interface (eth0, ens3, etc.) must be bound to the correct zone.<\/li>\n\n\n\n<li><strong>Runtime vs Permanent:<\/strong> Changes without <code>--permanent<\/code> last until the next reboot or reload. Save runtime to disk with <code>--runtime-to-permanent<\/code>.<\/li>\n\n\n\n<li><strong>Backends:<\/strong> Modern distros use nftables as the backend; older ones may use iptables. Don\u2019t run other firewall managers alongside firewalld.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Inspect zones and mappings\nsudo firewall-cmd --get-default-zone\nsudo firewall-cmd --get-active-zones\nsudo firewall-cmd --list-all --zone=public\n\n# Make permanent changes persist\nsudo firewall-cmd --runtime-to-permanent<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"fix-firewalld-not-starting\">Fix FirewallD Not Starting<\/h3>\n\n\n\n<p>When firewalld fails to start, it\u2019s usually a conflict, a corrupted config, or D-Bus\/back-end issues.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Check and unmask, then start\nsudo systemctl is-enabled firewalld\nsudo systemctl is-active firewalld\nsudo systemctl unmask firewalld\nsudo systemctl daemon-reload\nsudo systemctl restart firewalld\n\n# Look for errors (permissions, D-Bus, conflicts)\nsudo journalctl -xeu firewalld --no-pager\n\n# Verify D-Bus is healthy (do NOT restart D-Bus on remote production unless you have console access)\nsystemctl status dbus<\/code><\/pre>\n\n\n\n<p>If logs mention nft or iptables errors, stop and disable other firewall managers (UFW, iptables services, nftables) so firewalld has exclusive control. If configuration looks corrupted, validate and reset to defaults (see below).<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"fix-zone-and-rule-problems\">Fix Zone and Rule Problems<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"1-put-the-interface-in-the-correct-zone\">1) Put the interface in the correct zone<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># See interfaces active in zones\nsudo firewall-cmd --get-active-zones\n\n# Move your interface (e.g., eth0) to \"public\"\nsudo firewall-cmd --zone=public --change-interface=eth0\nsudo firewall-cmd --runtime-to-permanent\nsudo firewall-cmd --reload\n\n# NetworkManager users can bind zones to connections:\nnmcli connection show\nsudo nmcli connection modify &lt;CONNECTION_NAME&gt; connection.zone public\nsudo nmcli connection up &lt;CONNECTION_NAME&gt;<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"2-open-the-right-ports-services\">2) Open the right ports\/services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Services:<\/strong> Friendly bundles (ssh, http, https, dns, smtp).<\/li>\n\n\n\n<li><strong>Ports:<\/strong> Raw protocol\/port (e.g., tcp\/8080).<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Allow common services\nsudo firewall-cmd --zone=public --add-service=http --permanent\nsudo firewall-cmd --zone=public --add-service=https --permanent\n\n# Or open explicit ports\nsudo firewall-cmd --zone=public --add-port=8080\/tcp --permanent\n\n# Apply\nsudo firewall-cmd --reload\n\n# Check\nsudo firewall-cmd --zone=public --list-all<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"3-fix-runtime-vs-permanent-confusion\">3) Fix runtime vs permanent confusion<\/h3>\n\n\n\n<p>Rules added without <code>--permanent<\/code> vanish after a reload or reboot. Either use <code>--permanent<\/code> from the start or save runtime rules to disk:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-cmd --runtime-to-permanent\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"4-validate-and-reset-configuration\">4) Validate and reset configuration<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Validate\nsudo firewall-cmd --check-config\n\n# Reset to distribution defaults (back up first)\nsudo cp -a \/etc\/firewalld \/etc\/firewalld.backup.$(date +%F)\nsudo rm -rf \/etc\/firewalld\nsudo dnf reinstall -y firewalld || sudo apt-get install --reinstall -y firewalld\nsudo systemctl restart firewalld<\/code><\/pre>\n\n\n\n<p>Alternatively, use the offline tool when the service won\u2019t start:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-offline-cmd --set-default-zone=public\nsudo firewall-offline-cmd --add-service=ssh\nsudo systemctl restart firewalld<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"resolve-conflicts-with-other-firewalls\">Resolve Conflicts with Other Firewalls<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>UFW (Ubuntu\/Debian)<\/li>\n\n\n\n<li>iptables services (RHEL\/CentOS 7)<\/li>\n\n\n\n<li>nftables service (RHEL 8+\/Alma\/Rocky\/Debian\/Ubuntu)<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Stop\/disable other managers so firewalld is authoritative\nsudo systemctl stop ufw nftables iptables ip6tables ebtables\nsudo systemctl disable ufw nftables iptables ip6tables ebtables\n\n# Ensure firewalld takes control\nsudo systemctl restart firewalld\nsudo firewall-cmd --state<\/code><\/pre>\n\n\n\n<p><strong>Note:<\/strong> Cloud security groups (AWS, Azure, GCP, DigitalOcean) can still block traffic even if firewalld is correct. Check your provider\u2019s inbound rules.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"advanced-troubleshooting\">Advanced Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"check-selinux-denials\">Check SELinux denials<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Look for AVC denials related to firewalld or services\nsudo ausearch -m avc -ts recent 2&gt;\/dev\/null | tail -n 50\nsudo journalctl -t setroubleshoot --no-pager | tail -n 50<\/code><\/pre>\n\n\n\n<p>If you see SELinux denials for a service port, use the approved type or add it via <code>semanage port<\/code> (not by disabling SELinux).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"confirm-a-service-is-actually-listening\">Confirm a service is actually listening<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Is the application listening on the expected port?\nsudo ss -tulpen | grep -E ':80|:443|:22|:8080'\n\n# Test connectivity from local and remote\ncurl -I http:\/\/127.0.0.1\/\nnc -vz your.server.ip 80<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"increase-firewalld-logging-temporarily\">Increase firewalld logging temporarily<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Run with debug in foreground (for testing sessions)\nsudo systemctl stop firewalld\nsudo firewalld --debug\n# Ctrl+C to stop, then:\nsudo systemctl start firewalld<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"practical-examples-you-can-reuse\">Practical Examples You Can Reuse<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"allow-a-web-server-http-https\">Allow a web server (HTTP\/HTTPS)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo firewall-cmd --zone=public --add-service=http --permanent\nsudo firewall-cmd --zone=public --add-service=https --permanent\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"lock-down-ssh-to-a-trusted-ip\">Lock down SSH to a trusted IP<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Allow SSH only from 203.0.113.10\nsudo firewall-cmd --permanent --zone=public \\\n  --add-rich-rule='rule family=\"ipv4\" source address=\"203.0.113.10\" service name=\"ssh\" accept'\n# Drop others (ensure you have console access first!)\nsudo firewall-cmd --permanent --zone=public \\\n  --add-rich-rule='rule family=\"ipv4\" service name=\"ssh\" drop'\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"port-forwarding-and-masquerading-nat\">Port forwarding and masquerading (NAT)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Enable masquerade in the public zone\nsudo firewall-cmd --permanent --zone=public --add-masquerade\n\n# Forward external 8080 -&gt; internal 10.0.0.5:80\nsudo firewall-cmd --permanent --zone=public \\\n  --add-forward-port=port=8080:proto=tcp:toaddr=10.0.0.5:toport=80\n\nsudo firewall-cmd --reload<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"best-practices-for-stability-and-security\">Best Practices for Stability and Security<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Always allow SSH before making changes. Test from a second session.<\/li>\n\n\n\n<li>Use zones to separate WAN facing and internal interfaces.<\/li>\n\n\n\n<li>Prefer services over raw ports when available; they track protocol changes.<\/li>\n\n\n\n<li>Make permanent changes and back up <code>\/etc\/firewalld<\/code> before upgrades.<\/li>\n\n\n\n<li>Avoid running multiple firewall managers. Firewalld should be authoritative.<\/li>\n\n\n\n<li>Document rules and use version control for <code>\/etc\/firewalld\/*.xml<\/code>.<\/li>\n<\/ul>\n\n\n\n<p>Need a hand? On <strong><a href=\"https:\/\/www.youstable.com\/dedicated-servers\/\">YouStable\u2019s managed VPS and dedicated servers<\/a><\/strong>, our support team can audit your FirewallD, fix conflicts, and align rules with your stack and cloud security groups without downtime.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"when-to-contact-your-host\">When to Contact Your Host<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Firewalld won\u2019t start even after disabling conflicts and validating config.<\/li>\n\n\n\n<li>You\u2019re locked out or worried about losing <a href=\"https:\/\/www.youstable.com\/blog\/how-to-enable-ssh-access-for-clients-or-users\/\">SSH access<\/a>.<\/li>\n\n\n\n<li><strong>Complex needs:<\/strong> multi-NIC zone design, NAT\/forwarding, or compliance.<\/li>\n\n\n\n<li>You want 24\/7 monitoring and incident response (recommended for production).<\/li>\n<\/ul>\n\n\n\n<p>If you\u2019re hosted with <strong><a href=\"https:\/\/www.youstable.com\/\">YouStable<\/a><\/strong>, open a ticket and we\u2019ll review your logs, rules, interfaces, and provider firewalls end to end. We fix the root cause, not just the symptoms.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"faqs\">FAQs<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1765867955587\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"why-is-firewalld-not-starting-on-my-server\">Why is FirewallD not starting on my server?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Most often due to conflicts with UFW\/iptables\/nftables services, corrupted configs, or backend\/D-Bus errors. Check logs with <code>journalctl -xeu firewalld<\/code>, disable other firewall managers, validate with <code>firewall-cmd --check-config<\/code>, and restart. If configs are broken, reset to defaults and reapply rules.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765867970800\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-do-i-open-a-port-in-firewalld-permanently\">How do I open a port in FirewallD permanently?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Use <code>--permanent<\/code> with your zone, then reload. Example: <code>firewall-cmd --zone=public --add-port=8080\/tcp --permanent<\/code> followed by <code>firewall-cmd --reload<\/code>. Prefer services (like http\/https) when available.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765868014666\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-can-i-reset-firewalld-to-factory-defaults\">How can I reset FirewallD to factory defaults?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Back up <code>\/etc\/firewalld<\/code>, then reinstall or restore default configs: <code>cp -a \/etc\/firewalld \/etc\/firewalld.backup.$(date +%F)<\/code>, remove the directory, reinstall firewalld, and restart the service. Recreate rules carefully and test SSH access.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765868026280\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"whats-the-difference-between-runtime-and-permanent-rules\">What\u2019s the difference between runtime and permanent rules?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Runtime rules apply immediately but vanish after a reload or reboot. Permanent rules persist on disk and load at boot. Either use <code>--permanent<\/code> when adding rules or run <code>firewall-cmd --runtime-to-permanent<\/code> to save what\u2019s currently active.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765868044697\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-do-i-check-which-zone-my-interface-is-using\">How do I check which zone my interface is using?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Run <code>firewall-cmd --get-active-zones<\/code> to see interfaces by zone. If the interface is in the wrong zone, change it with <code>firewall-cmd --zone=public --change-interface=eth0<\/code> (replace <code>eth0<\/code> as appropriate), make it permanent, and reload.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>To fix FirewallD on a Linux server, start and enable the service, review logs for errors, remove conflicts with other [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":19133,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"iawp_total_views":1,"footnotes":""},"categories":[350],"tags":[],"class_list":["post-13626","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledgebase"],"acf":[],"featured_image_src":"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/Fix-FirewallD-on-Linux-Server.jpg","author_info":{"display_name":"Sanjeet Chauhan","author_link":"https:\/\/www.youstable.com\/blog\/author\/sanjeet"},"_links":{"self":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13626","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/comments?post=13626"}],"version-history":[{"count":5,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13626\/revisions"}],"predecessor-version":[{"id":19135,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13626\/revisions\/19135"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media\/19133"}],"wp:attachment":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media?parent=13626"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/categories?post=13626"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/tags?post=13626"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}