{"id":13629,"date":"2026-02-25T10:25:11","date_gmt":"2026-02-25T04:55:11","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=13629"},"modified":"2026-09-07T11:07:22","modified_gmt":"2026-09-07T05:37:22","slug":"fix-ufw-on-linux","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/fix-ufw-on-linux\/","title":{"rendered":"How to Fix UFW on Linux Server with iptables or nftables Backend"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>To fix UFW on a Linux server<\/strong>, verify the firewall is active, allow SSH, review rule order, check the backend (iptables or nftables), remove conflicts (firewalld\/Docker rules), account for cloud provider firewalls, then reload and test.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Start with: allow SSH, default deny incoming, permit required ports, enable UFW, and log\/monitor for drops.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, you\u2019ll learn how to fix UFW on a Linux server step by step. We\u2019ll cover quick checks, common issues (rules not working, SSH lockouts, Docker bypassing UFW), the iptables vs nftables backend, and a safe rebuild procedure. Whether you\u2019re on Ubuntu, Debian, or a YouStable VPS, these practical fixes will get your firewall working securely.<\/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-run-these-first\">Quick Fix Checklist (Run These First)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These commands resolve most UFW troubleshooting issues quickly. Use a second SSH session while testing to avoid lockouts.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1) See UFW status and backend\nufw --version\nufw status verbose\n\n# 2) Make sure SSH stays open\nufw allow OpenSSH || ufw allow 22\/tcp\n\n# 3) Set secure defaults\nufw default deny incoming\nufw default allow outgoing\n\n# 4) Allow required services\nufw allow 80\/tcp    # HTTP\nufw allow 443\/tcp   # HTTPS\n\n# 5) Enable UFW and logging\nufw enable\nufw logging on\n\n# 6) Reload and verify\nufw reload\nufw status numbered\nsudo ss -tulpn | grep -E ':22|:80|:443'   # Confirm services listen\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If traffic still isn\u2019t passing, continue with the diagnostics 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=\"diagnose-common-ufw-issues\">Diagnose Common UFW Issues<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"1-locked-out-of-ssh-or-cant-connect\">1) Locked out of SSH (or can\u2019t connect)?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Always allow <a href=\"https:\/\/www.youstable.com\/blog\/how-to-enable-ssh-access-for-clients-or-users\">SSH before enabling<\/a> UFW. On many distros, the AppProfile \u201cOpenSSH\u201d maps to port 22\/tcp:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ufw allow OpenSSH\n# or\nufw allow 22\/tcp\nufw reload\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>If you changed SSH to a custom port (e.g., 2222):<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ufw allow 2222\/tcp\nufw reload\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Still stuck? Your ISP or cloud firewall may block 22; verify provider side rules (see below).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"2-ufw-rules-are-not-working-due-to-rule-order\">2) UFW rules are not working due to rule order<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">UFW is order sensitive. A broad deny above a specific allow will block traffic. Inspect and re-order rules:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ufw status numbered\n# Delete a wrong rule (replace N with the rule number)\nufw delete N\n\n# Insert a rule at the top (position 1)\nufw insert 1 allow 443\/tcp\nufw reload\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you prefer a clean slate, jump to the reset section below.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"3-ufw-inactive-or-not-starting-at-boot\">3) UFW inactive or not starting at boot<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Make UFW persistent and ensure it loads early during boot:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl enable ufw\nsystemctl start ufw\nufw enable\nsystemctl status ufw --no-pager\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"4-iptables-vs-nftables-backend-mismatch\">4) iptables vs nftables backend mismatch<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Modern UFW can manage iptables (legacy) or nftables. Check which backend you\u2019re on:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ufw --version\n# Look for: \"backend: nftables\" or \"backend: iptables\"\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If other tools manage the same backend (e.g., firewalld, raw iptables scripts), conflicts occur. Pick one firewall manager and disable the rest:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># If firewalld is present, stop and disable it (use with caution)\nsystemctl stop firewalld\nsystemctl disable firewalld\n\n# Flush custom iptables\/nftables rules if needed (advanced)\niptables -F; iptables -t nat -F; iptables -t mangle -F\nnft flush ruleset\nufw reload\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Note: <\/strong>Flushing rules can impact production traffic. Schedule a maintenance window or use a staging server first.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"5-cloud-firewall-or-network-acls-blocking-traffic\">5) Cloud firewall or network ACLs blocking traffic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Many \u201cUFW not working\u201d cases are actually provider level blocks. Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AWS Security Groups and NACLs allow your ports\/IPs<\/li>\n\n\n\n<li>Azure NSGs and subnet rules permit inbound<\/li>\n\n\n\n<li>Google Cloud firewall rules allow traffic<\/li>\n\n\n\n<li>Your VPS panel firewall (e.g., YouStable Cloud\/VPS Firewall) mirrors the same ports<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Open both provider firewall and UFW to match your service ports.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"6-docker-bypassing-ufw\">6) Docker bypassing UFW<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Docker modifies iptables and can expose published ports before UFW rules. Two practical fixes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use the DOCKER USER chain to enforce policy before Docker rules<\/li>\n\n\n\n<li>Tighten UFW forwarding and explicitly allow only required bridges\/ports<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># Enforce a default drop for inbound to containers, then allow what you need\niptables -N DOCKER-USER 2&gt;\/dev\/null\niptables -C DOCKER-USER -j RETURN 2&gt;\/dev\/null || iptables -A DOCKER-USER -j RETURN\n\n# Example: allow only HTTPS (443) to containers\n# (Replace with specific interface\/bridge\/ports as needed)\n# iptables -I DOCKER-USER -p tcp --dport 443 -j ACCEPT\n\n# With UFW, ensure forwarding is controlled\nsed -i 's\/^DEFAULT_FORWARD_POLICY=.*\/DEFAULT_FORWARD_POLICY=\"DROP\"\/' \/etc\/default\/ufw\nufw reload\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you must expose Docker services publicly, prefer reverse proxies (Nginx\/Traefik) and allow only those front end ports via UFW.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"7-ipv6-disabled-or-partially-configured\">7) IPv6 disabled or partially configured<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If your server has IPv6 but UFW only filters IPv4, traffic can slip through. Enable IPv6 and reload:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -i '^IPV6=' \/etc\/default\/ufw || echo \"IPV6=yes\" &gt;&gt; \/etc\/default\/ufw\nsed -i 's\/^IPV6=.*\/IPV6=yes\/' \/etc\/default\/ufw\nufw disable &amp;&amp; ufw enable\nufw status verbose\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm your services are listening on IPv6 and that provider level IPv6 is allowed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"8-problem-running-ufw-init-or-missing-kernel-modules\">8) \u201cProblem running ufw-init\u201d or missing kernel modules<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ensure firewall tooling is installed and compatible with your kernel:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt-get update &amp;&amp; apt-get install -y ufw iptables nftables\nmodprobe nf_conntrack\njournalctl -u ufw -b --no-pager | tail -n 50\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On RHEL\/Rocky\/Alma, <a href=\"https:\/\/www.youstable.com\/blog\/install-ufw-on-linux\/\">install UFW<\/a> first or consider using firewalld if UFW is not supported by your stack.<\/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=\"safe-reset-and-rebuild-of-ufw-step-by-step\">Safe Reset and Rebuild of UFW (Step by Step)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your rules are messy or conflicting, a reset is often the fastest path to a secure, working configuration.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># 1) Reset all UFW rules (interactive)\nufw reset\n\n# 2) Set sane defaults\nufw default deny incoming\nufw default allow outgoing\n\n# 3) Keep SSH open (adjust port if custom)\nufw allow OpenSSH || ufw allow 22\/tcp\n\n# 4) Open necessary application ports\nufw allow 80\/tcp\nufw allow 443\/tcp\n# Examples:\n# ufw allow 3306\/tcp             # <a href=\"https:\/\/www.youstable.com\/blog\/mysql-commands\">MySQL<\/a> (prefer private network only)\n# ufw allow from 203.0.113.10 to any port 5432 proto tcp   # Restrict Postgres by IP\n\n# 5) Enable and log\nufw logging low\nufw enable\n\n# 6) Verify, then test externally\nufw status numbered\ncurl -I http:\/\/your-server-ip\ncurl -I https:\/\/your-domain\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tip: <\/strong>When exposing databases or admin panels, restrict by source IP to reduce attack surface.<\/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=\"real-world-scenarios-we-fix-at-youstable\">Real World Scenarios We Fix at YouStable<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"scenario-a-ufw-enabled-but-website-still-unreachable\">Scenario A: UFW enabled, but website still unreachable<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cause:<\/strong> Missing 80\/443 allows or provider firewall blocking. Fix: Allow ports in UFW and in the cloud firewall. Confirm Nginx\/Apache are listening on the correct IP\/port with ss -tulpn.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"scenario-b-fail2ban-not-banning-effectively\">Scenario B: Fail2ban not banning effectively<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cause:<\/strong> Fail2ban using iptables while UFW uses nftables (or vice versa). Fix: Align backends and set banaction to ufw in jail.local so bans show as UFW rules.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"scenario-c-docker-app-exposed-despite-ufw-denies\">Scenario C: Docker app exposed despite UFW denies<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cause:<\/strong> Docker publishes ports before UFW chains. Fix: Enforce DOCKER-USER policy, set UFW forward policy to DROP, and only allow explicit ports. Optionally place a reverse proxy in front and expose only 80\/443.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you host on YouStable, our support can review your UFW rules, provider firewalls, and Docker networking to harden your setup without downtime.<\/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=\"best-practices-for-a-secure-maintainable-ufw\">Best Practices for a Secure, Maintainable UFW<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Default deny inbound; allow only necessary ports<\/li>\n\n\n\n<li>Always allow SSH first and test in a second session<\/li>\n\n\n\n<li>Prefer IP-restricted rules for admin panels and databases<\/li>\n\n\n\n<li>Use numbered rules to manage order precisely<\/li>\n\n\n\n<li>Enable logging and watch \/var\/log\/ufw.log or journalctl -u ufw<\/li>\n\n\n\n<li>Keep IPv6 consistent with IPv4 policy (IPV6=yes)<\/li>\n\n\n\n<li>Avoid multiple firewall managers; pick UFW or firewalld, not both<\/li>\n\n\n\n<li>Document changes and back up rules before big edits<\/li>\n\n\n\n<li><strong>Use application profiles:<\/strong> ufw app list, ufw app info &#8220;OpenSSH&#8221;<\/li>\n\n\n\n<li>Pair with Fail2ban for SSH and web brute force protection<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"commands-reference-copy-paste\">Commands Reference (Copy Paste)<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code># See everything\nufw --version\nufw status verbose\njournalctl -u ufw -b --no-pager | tail -n 100\n\n# Core policy\nufw default deny incoming\nufw default allow outgoing\n\n# Allows\nufw allow OpenSSH\nufw allow 80\/tcp\nufw allow 443\/tcp\n\n# Restrict by IP\nufw allow from 203.0.113.10 to any port 22 proto tcp\n\n# Ordering\nufw status numbered\nufw insert 1 allow 443\/tcp\nufw delete 3\n\n# Service control\nsystemctl enable ufw\nsystemctl restart ufw\nufw reload\nufw disable &amp;&amp; ufw enable\n\n# Reset and rebuild\nufw reset\n<\/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=\"troubleshooting-ufw-not-working-on-different-distros\">Troubleshooting \u201cUFW Not Working\u201d on Different Distros<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"ubuntu-debian\">Ubuntu\/Debian<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">UFW is native here. Confirm backend, ensure no firewalld, and verify Docker behavior. AppProfiles like OpenSSH and Nginx Full simplify rules.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"rocky-alma-rhel\">Rocky\/Alma\/RHEL<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">firewalld is default. If you insist on UFW, ensure it\u2019s installed, firewalld disabled, and backends are consistent. Otherwise, consider staying with firewalld for native support.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"vps-and-cloud-environments\">VPS and Cloud Environments<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Mirror ports in both UFW and the provider firewall. On YouStable VPS, you can define instance level firewall rules from the panel for an extra layer of protection.<\/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=\"faq\">FAQ<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1765866188094\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"why-are-my-ufw-rules-not-working\">Why are my UFW rules not working?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Top causes include wrong rule order, disabled UFW, conflicting firewalls (firewalld\/iptables scripts), Docker overriding chains, or provider firewall blocks. Check ufw status numbered, ufw u002du002dversion, and your cloud firewall to align all layers.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765866202823\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-do-i-allow-a-port-in-ufw-without-breaking-ssh\">How do I allow a port in UFW without breaking SSH?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>First allow SSH: ufw allow OpenSSH. Then add your new port: ufw allow 8080\/tcp. Finally, reload and verify with ufw reload and ufw status verbose. Always keep a second SSH session open while testing.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765866220764\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"does-ufw-work-with-nftables\">Does UFW work with nftables?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Yes, Modern UFW can manage nftables. Run ufw u002du002dversion to see the backend. Ensure other tools (firewalld, raw nft rules) don\u2019t conflict. Keep all components on the same backend (iptables-nft or nftables native).<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765866237800\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-do-i-fix-docker-bypassing-ufw\">How do I fix Docker bypassing UFW?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Use the DOCKER-USER chain to enforce policy before Docker rules and set UFW\u2019s forward policy to DROP. Then allow only explicit ports. Alternatively, place a reverse proxy in front and expose just 80\/443 via UFW.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765866253678\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"is-ufw-enough-for-production-servers\">Is UFW enough for production servers?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Yes, when configured correctly with default deny, strict allows, logging, and Fail2ban. For layered security, combine UFW with provider firewalls and WAF\/CDN at the edge. YouStable can help design a layered policy tailored to your workload.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>To fix UFW on a Linux server, verify the firewall is active, allow SSH, review rule order, check the backend [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":19048,"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":304,"footnotes":""},"categories":[350,2262],"tags":[],"class_list":["post-13629","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledgebase","category-kb-security"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13629","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=13629"}],"version-history":[{"count":1,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13629\/revisions"}],"predecessor-version":[{"id":22992,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13629\/revisions\/22992"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media\/19048"}],"wp:attachment":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media?parent=13629"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/categories?post=13629"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/tags?post=13629"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}