{"id":23600,"date":"2025-06-02T11:46:54","date_gmt":"2025-06-02T11:46:54","guid":{"rendered":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/?lw_help_doc=security\/firewall-management\/iptables-firewall"},"modified":"2026-06-30T16:37:39","modified_gmt":"2026-06-30T20:37:39","slug":"iptables-firewall","status":"publish","type":"lw_help_doc","link":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/","title":{"rendered":"Manage your server’s firewall with iptables"},"content":{"rendered":"\n

iptables<\/code> is a powerful, command-line firewall utility built into Linux operating systems, allowing you to set up, maintain, and inspect the tables of IP packet filter rules in the Linux kernel. Understanding iptables<\/code> improves your ability to secure your server and manage your network, enabling you to control access to services, block malicious traffic, and ensure your server communicates securely.<\/p>\n\n\n\n

Basic concepts: tables and chains<\/h2>\n\n\n\n

iptables<\/code> organizes its rules into tables<\/strong>, and within each table, there are chains<\/strong>.<\/p>\n\n\n\n

    \n
  • Tables:<\/strong> There are three main tables used for basic firewalling:\n
      \n
    • filter<\/code> (Default):<\/strong> This is the most common table and is used for general packet filtering (allowing or denying traffic). If you don’t specify a table, iptables<\/code> uses the filter<\/code> table by default.<\/li>\n\n\n\n
    • nat<\/code> (Network Address Translation):<\/strong> Used for modifying packet addresses (e.g., port forwarding, masquerading).<\/li>\n\n\n\n
    • mangle<\/code>:<\/strong> Used for modifying packet headers (e.g., changing Quality of Service bits).
      <\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • Chains:<\/strong> Within the filter<\/code> table, there are three built-in chains that define where rules are applied:\n
        \n
      • INPUT<\/code>:<\/strong> Rules in this chain apply to packets entering<\/strong> the server, destined for a local process. This is the most frequently modified chain for server security.<\/li>\n\n\n\n
      • OUTPUT<\/code>:<\/strong> Rules in this chain apply to packets originating from<\/strong> the server, going to an external destination.<\/li>\n\n\n\n
      • FORWARD<\/code>:<\/strong> Rules in this chain apply to packets that are being routed through<\/strong> the server (i.e., not destined for the server itself, but passing through to another network). This is typically used on routers or gateways.
        <\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Policies:<\/strong> Each chain has a default policy (e.g., ACCEPT<\/code>, DROP<\/code>, REJECT<\/code>).\n
          \n
        • ACCEPT<\/code>:<\/strong> Allows the packet to pass.<\/li>\n\n\n\n
        • DROP<\/code>:<\/strong> Silently discards the packet. The sender receives no notification.<\/li>\n\n\n\n
        • REJECT<\/code>:<\/strong> Discards the packet and sends an error message (e.g., ICMP port unreachable) back to the sender.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

          Rule matching directives<\/h3>\n\n\n\n

          Use various directives when creating iptables<\/code> rules to specify what kind of traffic the rule should match:<\/p>\n\n\n\n

            \n
          • [!] -p, --protocol protocol<\/code>:<\/strong> Specifies the protocol (e.g., tcp<\/code>, udp<\/code>, icmp<\/code>, all<\/code>). The !<\/code> inverts the match.<\/li>\n\n\n\n
          • [!] -s, --source address[\/mask]<\/code>:<\/strong> Specifies the source IP address or network from which the packet originates.<\/li>\n\n\n\n
          • [!] -d, --destination address[\/mask]<\/code>:<\/strong> Specifies the destination IP address or network where the packet is headed.<\/li>\n\n\n\n
          • -j, --jump target<\/code>:<\/strong> Specifies the action to take if the packet matches the rule. Common targets are ACCEPT<\/code>, DROP<\/code>, REJECT<\/code>, or jumping to a user-defined chain.<\/li>\n\n\n\n
          • [!] --dport port<\/code>:<\/strong> (Used with -p tcp<\/code> or -p udp<\/code>) Specifies the destination port number or service name (e.g., 80<\/code>, ssh<\/code>).<\/li>\n\n\n\n
          • [!] --sport port<\/code>:<\/strong> (Used with -p tcp<\/code> or -p udp<\/code>) Specifies the source port number or service name.<\/li>\n\n\n\n
          • [!] -i, --in-interface name<\/code>:<\/strong> Matches packets received via a specific network interface (e.g., eth0<\/code>).<\/li>\n\n\n\n
          • [!] -o, --out-interface name<\/code>:<\/strong> Matches packets being sent via a specific network interface.<\/li>\n<\/ul>\n\n\n\n

            Common iptables commands<\/h2>\n\n\n\n

            Here are the most frequently used iptables<\/code> commands for managing your firewall rules:<\/p>\n\n\n\n

              \n
            • -L<\/code> (List Rules):<\/strong> Lists all rules in a specified chain or all chains if none is specified.\n
                \n
              • iptables -L INPUT<\/code>: Lists all rules in the INPUT<\/code> chain.<\/li>\n\n\n\n
              • iptables -L -v -n<\/code>: Lists all rules in all chains with verbose (detailed) and numeric (IPs instead of hostnames) output. This is very useful for troubleshooting.
                <\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • -F<\/code> (Flush Rules):<\/strong> Deletes all rules from a specified chain. If no chain is specified, it flushes all rules from all chains.\n
                  \n
                • iptables -F INPUT<\/code>: Flushes all rules from the INPUT<\/code> chain.
                  <\/li>\n<\/ul>\n<\/li>\n\n\n\n
                • -A<\/code> (Append Rule):<\/strong> Adds a new rule to the end of a specified chain.\n
                    \n
                  • iptables -A INPUT -p tcp --dport 80 -j ACCEPT<\/code>:
                    Appends a rule to the INPUT<\/code> chain to accept incoming TCP traffic on port 80.
                    <\/li>\n<\/ul>\n<\/li>\n\n\n\n
                  • -D<\/code> (Delete Rule):<\/strong> Deletes a rule from a specified chain. You can specify the rule by its exact description or by its line number (obtained with iptables -L --line-numbers<\/code>).\n
                      \n
                    • iptables -D INPUT 5<\/code>: Deletes the rule at line number 5 from the INPUT<\/code> chain.
                      <\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • -I<\/code> (Insert Rule):<\/strong> Inserts a new rule at a specific line number in a chain. If no line number is given, it inserts the rule at the top (line 1).\n
                        \n
                      • iptables -I INPUT 1 -p tcp --dport 22 -j ACCEPT<\/code>: Inserts a rule to accept SSH traffic at the very beginning of the INPUT<\/code> chain.
                        <\/li>\n<\/ul>\n<\/li>\n\n\n\n
                      • -P<\/code> (Set Policy):<\/strong> Sets the default policy for a chain.\n
                          \n
                        • iptables -P INPUT DROP<\/code>: Sets the default policy for the INPUT<\/code> chain to DROP<\/code> (meaning all incoming traffic is blocked by default unless explicitly allowed by a rule).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

                          Connection tracking states<\/h2>\n\n\n\n

                          iptables<\/code> can track the state of network connections, allowing for more intelligent rule sets. This is managed by the conntrack<\/code> module.<\/p>\n\n\n\n

                            \n
                          • NEW<\/code>:<\/strong> A packet that is starting a new connection.<\/li>\n\n\n\n
                          • ESTABLISHED<\/code>:<\/strong> A packet that belongs to an existing, established connection (traffic has been seen in both directions).<\/li>\n\n\n\n
                          • RELATED<\/code>:<\/strong> A packet that is starting a new connection but is related to an existing one (e.g., an FTP data transfer connection opening after a control connection).<\/li>\n\n\n\n
                          • INVALID<\/code>:<\/strong> A packet that does not belong to any known connection or is malformed. These are often dropped for security.<\/li>\n<\/ul>\n\n\n
                            \n\n
                            <\/div><\/div>\n\n<\/div><\/div>\n\n\n

                            Save rules to make them persistent<\/h2>\n\n\n\n

                            Rules you add with iptables<\/code> commands are active immediately but are not persistent<\/strong> across server reboots. To make them permanent, you need to save them.<\/p>\n\n\n\n

                            CentOS\/RHEL<\/strong><\/h3>\n\n\n\n
                              \n
                            1. Save the current rules to \/etc\/sysconfig\/iptables<\/code>:
                              service iptables save<\/strong><\/code>
                              <\/li>\n\n\n\n
                            2. Ensure iptables<\/code> starts on boot:
                              chkconfig iptables on<\/strong><\/code><\/li>\n<\/ol>\n\n\n\n

                              Backup and Restore Rules<\/strong><\/h2>\n\n\n\n
                                \n
                              • Back up your current iptables<\/code> rules:
                                iptables-save > \/root\/my_iptables_rules.bak<\/strong><\/code>
                                <\/li>\n\n\n\n
                              • Restore previously backed up rules:
                                iptables-restore < \/root\/my_iptables_rules.bak<\/strong><\/code><\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n

                                <\/p>\n\n\n\n

                                Practical iptables examples<\/strong><\/p>\n

                                Here are common scenarios and how to implement them with iptables<\/code>.<\/p>\n

                                Drop all incoming traffic to a specific port<\/strong><\/strong><\/summary>
                                \n

                                Port 25<\/code> is used in the following example, but any port can be used. The service name can be used (ex. smtp<\/code> instead of 25)<\/code> if the service name is in \/etc\/services<\/code>.<\/p>\n\n

                                iptables -A INPUT -p tcp --dport 25 -j DROP<\/code><\/p>\n<\/div><\/details>

                                Lock down SSH access<\/strong><\/strong> to specific IP addresses <\/strong><\/strong><\/summary>
                                \n

                                This requires two rules: one to allow the trusted IP, and a second, broader rule to drop all other SSH attempts. The order of rules matters!

                                The IP address 192.168.1.3 is used in this example, but any IP that is trusted can be used:
                                iptables -A INPUT -p tcp -s 192.168.1.3 --dport 22 -j ACCEPT <\/code><\/strong>
                                iptables -A INPUT -p tcp --dport 22 -j DROP<\/code><\/strong><\/p>\n<\/div><\/details>

                                Block a specific IP address<\/strong><\/strong><\/summary>
                                \n

                                Insert a rule at the top of the INPUT<\/code> chain to immediately drop all traffic from a malicious IP.

                                The IP address 192.0.2.50 is used in this example, but any potentially malicious IP can be used:
                                iptables -I INPUT -s 192.0.2.50 -j DROP<\/strong><\/code><\/p>\n<\/div><\/details><\/div><\/div>\n\n\n\n

                                <\/p>\n\n\n\n

                                \n\n\n\n

                                <\/p>\n\n\n\n

                                Troubleshooting iptables<\/strong><\/p>

                                Clearing Your Firewall (for Debugging)<\/strong><\/strong><\/strong><\/summary>
                                \n

                                If you suspect your firewall rules are causing issues, you can temporarily clear them.<\/p>\n\n

                                <\/svg><\/span><\/div><\/div><\/div><\/div>
                                Note<\/span>

                                Use with extreme caution on production servers, as this opens all ports!<\/strong> Be sure to take a backup.<\/strong><\/p><\/div><\/span><\/div>\n\n

                                <\/p>\n\n

                                The following commands will reset your iptables firewall rule set:<\/p>\n\n

                                iptables -P INPUT ACCEPT    # Set default policy to ACCEPT for incoming
                                iptables -P OUTPUT ACCEPT   # Set default policy to ACCEPT for outgoing
                                iptables -P FORWARD ACCEPT  # Set default policy to ACCEPT for forwarding
                                iptables -F                 # Flush all rules from all chains
                                iptables -X                 # Delete all user-defined chains
                                iptables -Z                 # Zero out all packet and byte counters<\/code><\/pre>\n<\/div><\/details>
                                “Resource temporarily unavailable” Error<\/strong><\/strong><\/strong><\/summary>
                                \n
                                If you see messages like Starting APF:iptables: Resource temporarily unavailable<\/code> when restarting your firewall, it often means the server is low on available memory. Check your server’s memory usage. If it’s critically low, temporarily shut down non-essential services, restart the firewall, and then bring your services back online.<\/p>\n<\/div><\/details>
                                Trouble with IP Addresses Ending in .255<\/strong><\/strong><\/strong><\/summary>
                                \n
                                Some firewall configurations (especially older ones or those with default rules) might implicitly drop traffic to IP addresses ending in .255<\/code> (which are often used as broadcast addresses). If you have a legitimate server IP ending in .255<\/code> and experience connectivity issues, you might need to remove these blocking rules.<\/p>\n\n
                                  \n
                                1. Find the rule’s line number:
                                  iptables -L INPUT --line-numbers | grep \".255\"
                                  <\/code>\n
                                    \n
                                  • You might see output similar to this: 
                                    27 DROP icmp -- anywhere 0.0.0.255\/0.0.0.255
                                    28 DROP all -- anywhere 0.0.0.255\/0.0.0.255<\/code>
                                    <\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                  • Delete the first rule by its line number. Then, delete the next rule, remembering that its line number will have shifted up by one.
                                    iptables -D INPUT 27 # Deletes the first rule (e.g., original was on line 27)
                                    iptables -D INPUT 27 # Deletes the new rule at line 27 (original was on line 28)<\/code><\/li>\n<\/ol>\n\n
                                    This will allow traffic to the .255 IP to route properly.<\/p>\n<\/div><\/details><\/div><\/div>\n\n\n\n
                                    <\/p>\n\n\n\n
                                    Conclusion<\/h3>\n\n\n\n
                                    iptables<\/code> is a fundamental tool for securing and managing network traffic on your Linux server. By understanding its basic concepts, commands, and troubleshooting techniques, you can effectively control access, protect your services, and diagnose connectivity issues. Always exercise caution when modifying firewall rules, and remember to save your changes to ensure they persist across reboots. <\/p>\n","protected":false},"excerpt":{"rendered":"
                                    iptables can act as your server’s gatekeeper, deciding which network traffic is allowed in, out, or through your server.<\/p>\n","protected":false},"author":133,"featured_media":0,"parent":23088,"menu_order":0,"template":"","meta":{"footnotes":"","_nx_search_keywords":"","_nx_search_boost":0},"vertical":[256],"lw_resource_category":[3031,2750,2752,2764],"lw_resource_topic":[],"lw_resource_section":[3561],"class_list":["post-23600","lw_help_doc","type-lw_help_doc","status-publish","hentry","vertical-hosting","lw_resource_category-firewalls","lw_resource_category-security","lw_resource_category-troubleshooting","lw_resource_category-tutorials","lw_resource_section-security"],"yoast_head":"\nManage your server's firewall with iptables - Nexcess Documentation<\/title>\n<meta name=\"robots\" content=\"noindex, follow\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Manage your server's firewall with iptables\" \/>\n<meta property=\"og:description\" content=\"iptables can act as your server's gatekeeper, deciding which network traffic is allowed in, out, or through your server.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/\" \/>\n<meta property=\"og:site_name\" content=\"Nexcess Documentation\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-30T20:37:39+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/firewall-management\\\/iptables-firewall\\\/\",\"url\":\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/firewall-management\\\/iptables-firewall\\\/\",\"name\":\"Manage your server's firewall with iptables - Nexcess Documentation\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/#website\"},\"datePublished\":\"2025-06-02T11:46:54+00:00\",\"dateModified\":\"2026-06-30T20:37:39+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/firewall-management\\\/iptables-firewall\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/firewall-management\\\/iptables-firewall\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/firewall-management\\\/iptables-firewall\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/docs.nexcess.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Security Overview\",\"item\":\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Firewall Management\",\"item\":\"https:\\\/\\\/docs.nexcess.com\\\/hosting\\\/security\\\/firewall-management\\\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Manage your server’s firewall with iptables\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/#website\",\"url\":\"https:\\\/\\\/docs.nexcess.com\\\/\",\"name\":\"Nexcess Documentation\",\"description\":\"Search the docs, or browse by product, category, and topic across Hosting and WordPress.\",\"publisher\":{\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/docs.nexcess.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/#organization\",\"name\":\"Nexcess Documentation\",\"url\":\"https:\\\/\\\/docs.nexcess.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/docs.nexcess.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/favicon-1.webp\",\"contentUrl\":\"https:\\\/\\\/docs.nexcess.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/favicon-1.webp\",\"width\":512,\"height\":512,\"caption\":\"Nexcess Documentation\"},\"image\":{\"@id\":\"https:\\\/\\\/docs.nexcess.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Manage your server's firewall with iptables - Nexcess Documentation","robots":{"index":"noindex","follow":"follow"},"og_locale":"en_US","og_type":"article","og_title":"Manage your server's firewall with iptables","og_description":"iptables can act as your server's gatekeeper, deciding which network traffic is allowed in, out, or through your server.","og_url":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/","og_site_name":"Nexcess Documentation","article_modified_time":"2026-06-30T20:37:39+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/","url":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/","name":"Manage your server's firewall with iptables - Nexcess Documentation","isPartOf":{"@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/#website"},"datePublished":"2025-06-02T11:46:54+00:00","dateModified":"2026-06-30T20:37:39+00:00","breadcrumb":{"@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/iptables-firewall\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/"},{"@type":"ListItem","position":2,"name":"Security Overview","item":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/"},{"@type":"ListItem","position":3,"name":"Firewall Management","item":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/hosting\/security\/firewall-management\/"},{"@type":"ListItem","position":4,"name":"Manage your server’s firewall with iptables"}]},{"@type":"WebSite","@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/#website","url":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/","name":"Nexcess Documentation","description":"Search the docs, or browse by product, category, and topic across Hosting and WordPress.","publisher":{"@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/#organization","name":"Nexcess Documentation","url":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/#\/schema\/logo\/image\/","url":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-content\/uploads\/2026\/07\/favicon-1.webp","contentUrl":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-content\/uploads\/2026\/07\/favicon-1.webp","width":512,"height":512,"caption":"Nexcess Documentation"},"image":{"@id":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_help_doc\/23600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_help_doc"}],"about":[{"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/types\/lw_help_doc"}],"author":[{"embeddable":true,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/users\/133"}],"version-history":[{"count":1,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_help_doc\/23600\/revisions"}],"predecessor-version":[{"id":47324,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_help_doc\/23600\/revisions\/47324"}],"up":[{"embeddable":true,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_help_doc\/23088"}],"wp:attachment":[{"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/media?parent=23600"}],"wp:term":[{"taxonomy":"vertical","embeddable":true,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/vertical?post=23600"},{"taxonomy":"lw_resource_category","embeddable":true,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_resource_category?post=23600"},{"taxonomy":"lw_resource_topic","embeddable":true,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_resource_topic?post=23600"},{"taxonomy":"lw_resource_section","embeddable":true,"href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/docs.nexcess.com\/wp-json\/wp\/v2\/lw_resource_section?post=23600"}],"curies":[{"name":"wp","href":"https:\/\/round-lake.dustinice.workers.dev:443\/https\/api.w.org\/{rel}","templated":true}]}}