{"id":3523,"date":"2011-07-27T19:38:41","date_gmt":"2011-07-27T23:38:41","guid":{"rendered":"http:\/\/underhost.com\/blog\/?p=3523"},"modified":"2026-10-23T08:58:09","modified_gmt":"2026-10-23T12:58:09","slug":"how-to-fix-usr-bin-crontab-permissions-are-wrong-error-in-cpanel","status":"publish","type":"post","link":"https:\/\/underhost.com\/blog\/how-to-fix-usr-bin-crontab-permissions-are-wrong-error-in-cpanel\/","title":{"rendered":"Fix &#8220;\/usr\/bin\/crontab permissions are wrong&#8221; on cPanel and Linux Servers"},"content":{"rendered":"<div class=\"uh-blog-hero\" style=\"margin:0 0 40px;text-align:center;padding:48px 24px;border-radius:20px;background:linear-gradient(135deg,#0D1F3C 0%,#125A8A 58%,#176EA5 100%);color:#ffffff;box-shadow:0 20px 40px -15px rgba(13,31,60,0.28);position:relative;overflow:hidden;\">\n<div style=\"display:inline-flex;align-items:center;gap:8px;padding:7px 14px;margin-bottom:16px;border:1px solid rgba(0,212,255,0.32);border-radius:999px;color:#DFF8FF;font-size:12px;font-weight:800;letter-spacing:.06em;text-transform:uppercase;background:rgba(0,212,255,0.10);\"><i class=\"fas fa-sliders-h\" style=\"color:#00D4FF;\"><\/i> Control Panels<\/div>\n<h1 style=\"color:#ffffff;font-size:clamp(32px,5vw,46px);line-height:1.12;margin:0 0 14px;font-weight:800;\">Fix &#8220;\/usr\/bin\/crontab permissions are wrong&#8221; on cPanel and Linux Servers<\/h1>\n<p style=\"font-size:18px;color:#EAF6FF;max-width:800px;margin:0 auto;line-height:1.7;\">Encountering the &#8220;\/usr\/bin\/crontab permissions are wrong. Please set to 4755&#8221; error in cPanel? Follow this simple guide to resolve it on RedHat, CentOS, or Fedora servers.<\/p>\n<\/div>\n<div class=\"uh-blog-excerpt\" style=\"border-left:4px solid #00D4FF;padding:18px 20px;margin:0 0 34px;background:#F8FAFC;color:#1F2937;border-radius:0 14px 14px 0;box-shadow:0 8px 28px rgba(13,31,60,0.08);line-height:1.75;\"><strong style=\"color:#0D1F3C;\">Short answer:<\/strong> The <code>crontab<\/code> program must be owned by root with the setuid bit set (permissions <strong>4755<\/strong>, shown as <code>-rwsr-xr-x<\/code>). As root, check it with <code>ls -l \/usr\/bin\/crontab<\/code>. Restore the packaged permissions with <code>rpm --setperms cronie<\/code> on AlmaLinux, Rocky Linux and CloudLinux, or run <code>chmod 4755 \/usr\/bin\/crontab<\/code>. If the file is missing or damaged, reinstall the package with <code>dnf reinstall cronie<\/code>.<\/div>\n<nav aria-label=\"Table of contents\" class=\"uh-toc\" style=\"background:#ffffff;border:1px solid #E5E7EB;border-radius:16px;padding:20px 22px;margin:0 0 34px;box-shadow:0 4px 12px rgba(13,31,60,0.08);\">\n<div style=\"font-size:12px;font-weight:800;letter-spacing:.06em;text-transform:uppercase;color:#176EA5;margin-bottom:10px;\"><i class=\"fas fa-list\" style=\"color:#00D4FF;\"><\/i> In this guide<\/div>\n<ol style=\"margin:0;padding-left:20px;columns:2 260px;column-gap:28px;line-height:1.9;\">\n<li><a href=\"#what-the-error-means\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">What the error means<\/a><\/li>\n<li><a href=\"#common-causes\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Common causes<\/a><\/li>\n<li><a href=\"#step-1-check-the-current-permissions\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Step 1: check the current permissions<\/a><\/li>\n<li><a href=\"#step-2-let-the-package-manager-check-and-fix-it\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Step 2: let the package manager check and fix it<\/a><\/li>\n<li><a href=\"#step-3-or-set-the-permissions-by-hand\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Step 3: or set the permissions by hand<\/a><\/li>\n<li><a href=\"#step-4-reinstall-if-the-file-is-damaged\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Step 4: reinstall if the file is damaged<\/a><\/li>\n<li><a href=\"#step-5-make-sure-the-cron-service-runs\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Step 5: make sure the cron service runs<\/a><\/li>\n<li><a href=\"#step-6-test-with-a-real-job\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Step 6: test with a real job<\/a><\/li>\n<li><a href=\"#cron-jobs-in-cpanel\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">Cron jobs in cPanel<\/a><\/li>\n<li><a href=\"#if-many-files-lost-their-permissions\" style=\"color:#176EA5;text-decoration:none;font-weight:600;\">If many files lost their permissions<\/a><\/li>\n<\/ol>\n<\/nav>\n<div class=\"uh-post-content\" style=\"color:#1F2937;font-size:16px;line-height:1.75;\">\n<h2 id=\"what-the-error-means\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-exclamation-triangle\" style=\"color:#00D4FF;\"><\/i> What the error means<\/h2>\n<p style=\"margin:0 0 18px;\">Normal users edit their scheduled tasks with the <code>crontab<\/code> command. It writes to a protected folder, <code>\/var\/spool\/cron<\/code>, which only root can change. The setuid bit lets the program do that on the user&#8217;s behalf. If the bit is missing, or the file is not owned by root, crontab refuses to run and prints:<\/p>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code>\/usr\/bin\/crontab permissions are wrong. Please set to 4755<\/code><\/pre>\n<p style=\"margin:0 0 18px;\">On a cPanel server, account owners see the problem as errors when they add or edit jobs in <strong>Advanced &gt; Cron Jobs<\/strong>, or their existing jobs stop changing.<\/p>\n<h2 id=\"common-causes\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-angle-double-right\" style=\"color:#00D4FF;\"><\/i> Common causes<\/h2>\n<ul style=\"margin:0 0 24px;padding-left:22px;\">\n<li style=\"margin:0 0 8px;\">A recursive <code>chmod<\/code> or <code>chown<\/code> run on <code>\/usr<\/code> or <code>\/<\/code> by mistake.<\/li>\n<li style=\"margin:0 0 8px;\">A security script or hardening tool that removed setuid bits.<\/li>\n<li style=\"margin:0 0 8px;\">A restore or file copy that did not keep special permissions.<\/li>\n<li style=\"margin:0 0 8px;\">A damaged or partly updated cron package.<\/li>\n<\/ul>\n<h2 id=\"step-1-check-the-current-permissions\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-terminal\" style=\"color:#00D4FF;\"><\/i> Step 1: check the current permissions<\/h2>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code>ls -l \/usr\/bin\/crontab\n# Correct: -rwsr-xr-x. 1 root root ... \/usr\/bin\/crontab<\/code><\/pre>\n<p style=\"margin:0 0 18px;\">The <code>s<\/code> in the owner&#8217;s permissions is the setuid bit. If you see <code>-rwxr-xr-x<\/code>, or an owner other than root, the permissions are wrong.<\/p>\n<h2 id=\"step-2-let-the-package-manager-check-and-fix-it\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-terminal\" style=\"color:#00D4FF;\"><\/i> Step 2: let the package manager check and fix it<\/h2>\n<p style=\"margin:0 0 18px;\">The cron package records the correct owner and permissions of its files. Compare them and restore them:<\/p>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code># AlmaLinux, Rocky Linux, CloudLinux, RHEL\nrpm -qf \/usr\/bin\/crontab          # which package owns the file (usually cronie)\nrpm -V cronie                     # lists files that differ from the package\nrpm --setugids cronie             # restore owners and groups\nrpm --setperms cronie             # restore permissions<\/code><\/pre>\n<p style=\"margin:0 0 18px;\"><code>rpm -V<\/code> prints nothing when everything matches. A line with <code>M<\/code> means the mode (permissions) changed.<\/p>\n<h2 id=\"step-3-or-set-the-permissions-by-hand\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-terminal\" style=\"color:#00D4FF;\"><\/i> Step 3: or set the permissions by hand<\/h2>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code>chown root:root \/usr\/bin\/crontab\nchmod 4755 \/usr\/bin\/crontab\nls -l \/usr\/bin\/crontab<\/code><\/pre>\n<h2 id=\"step-4-reinstall-if-the-file-is-damaged\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-terminal\" style=\"color:#00D4FF;\"><\/i> Step 4: reinstall if the file is damaged<\/h2>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code># AlmaLinux, Rocky Linux, CloudLinux\ndnf reinstall -y cronie crontabs\n\n# Debian and Ubuntu (package name: cron)\napt install --reinstall cron<\/code><\/pre>\n<p style=\"margin:0 0 18px;\">Old guides mention <code>vixie-cron<\/code>. That package belongs to CentOS 5 and 6; current systems use <code>cronie<\/code> on the Red Hat family and <code>cron<\/code> on Debian and Ubuntu.<\/p>\n<h2 id=\"step-5-make-sure-the-cron-service-runs\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-terminal\" style=\"color:#00D4FF;\"><\/i> Step 5: make sure the cron service runs<\/h2>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code>systemctl enable --now crond     # AlmaLinux, Rocky Linux, CloudLinux\nsystemctl status crond --no-pager\n\nsystemctl enable --now cron      # Debian and Ubuntu<\/code><\/pre>\n<h2 id=\"step-6-test-with-a-real-job\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-terminal\" style=\"color:#00D4FF;\"><\/i> Step 6: test with a real job<\/h2>\n<p style=\"margin:0 0 18px;\">As a normal user, or from cPanel&#8217;s Cron Jobs page, add a job that writes to a file every minute:<\/p>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code>* * * * * date &gt;&gt; $HOME\/cron-test.log<\/code><\/pre>\n<p style=\"margin:0 0 18px;\">After two minutes, check that <code>cron-test.log<\/code> has new lines, then delete the job and the file. On cPanel servers, also check that the user&#8217;s jobs are in <code>\/var\/spool\/cron\/USERNAME<\/code>.<\/p>\n<h2 id=\"cron-jobs-in-cpanel\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-angle-double-right\" style=\"color:#00D4FF;\"><\/i> Cron jobs in cPanel<\/h2>\n<p style=\"margin:0 0 18px;\">Account owners manage their jobs in cPanel under <strong>Advanced &gt; Cron Jobs<\/strong>. Set a cron email address there to receive the output of each job, which makes failed jobs easy to spot. Use full paths in commands, such as <code>\/usr\/local\/bin\/php<\/code>, because cron runs with a minimal environment.<\/p>\n<h2 id=\"if-many-files-lost-their-permissions\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-angle-double-right\" style=\"color:#00D4FF;\"><\/i> If many files lost their permissions<\/h2>\n<p style=\"margin:0 0 18px;\">If the cause was a recursive chmod or chown, other programs, such as <code>sudo<\/code>, <code>passwd<\/code> and <code>su<\/code>, are probably broken too. Check every installed package and restore them:<\/p>\n<pre style=\"background:#0D1F3C;color:#EAF6FF;padding:18px 20px;border-radius:14px;overflow-x:auto;line-height:1.7;font-size:15px;\"><code>rpm -Va | grep -E \"^.M\" | head -n 50     # files with changed permissions\nrpm -a --setperms                         # restore permissions for all packages\nrpm -a --setugids                         # restore owners and groups<\/code><\/pre>\n<p style=\"margin:0 0 18px;\">Run this carefully, and only on the Red Hat family. Restoring all packages also resets permissions you may have changed on purpose. On a badly damaged server, restoring from a backup can be quicker.<\/p>\n<div aria-hidden=\"true\" class=\"uh-section-divider\" style=\"width:min(100% - 32px, 1080px);margin:44px auto;display:grid;grid-template-columns:1fr 32px 1fr;align-items:center;gap:18px;pointer-events:none;\"><span style=\"height:1px;background:linear-gradient(90deg,transparent,rgba(0,212,255,0.40),rgba(23,110,165,0.24),transparent);\"><\/span><img alt=\"\" decoding=\"async\" height=\"32\" loading=\"lazy\" src=\"https:\/\/cdn.underhost.com\/android-chrome-192x192.webp\" style=\"width:32px;height:32px;display:block;border-radius:8px;filter:drop-shadow(0 0 14px rgba(0,212,255,0.30));\" width=\"32\"\/><span style=\"height:1px;background:linear-gradient(90deg,transparent,rgba(23,110,165,0.24),rgba(0,212,255,0.40),transparent);\"><\/span><\/div>\n<\/div>\n<div class=\"uh-blog-cta\" style=\"background:linear-gradient(135deg,#0D1F3C 0%,#125A8A 58%,#176EA5 100%);color:#ffffff;padding:36px 24px;border-radius:20px;text-align:center;margin:44px 0;box-shadow:0 20px 40px -15px rgba(13,31,60,0.32);\">\n<h2 style=\"margin:0 0 12px;font-size:28px;line-height:1.25;color:#ffffff;\">Need help with this?<\/h2>\n<p style=\"font-size:17px;margin:0 auto 22px;color:#EAF6FF;max-width:720px;line-height:1.7;\">Server permissions broken after a change? Our team can repair the system and check for other damage.<\/p>\n<p><a href=\"https:\/\/underhost.com\/server-management.php\" style=\"background:linear-gradient(90deg,#00D4FF,#0077FF);color:#ffffff;padding:13px 28px;border-radius:10px;text-decoration:none;font-weight:800;display:inline-block;margin:8px;\">See server management plans<\/a><a href=\"https:\/\/customerpanel.ca\/client\/\" style=\"background:transparent;color:#ffffff;padding:12px 28px;border-radius:10px;text-decoration:none;font-weight:800;display:inline-block;margin:8px;border:1px solid rgba(255,255,255,0.32);\">Contact @CustomerPanel<\/a><\/div>\n<div class=\"uh-faq-section\" id=\"faq\" style=\"margin:34px 0;scroll-margin-top:90px;\">\n<h2 style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:0 0 18px;border-bottom:2px solid rgba(0,212,255,0.22);padding-bottom:10px;\">Frequently asked questions<\/h2>\n<div style=\"margin-top:18px;background:#F8FAFC;padding:18px 20px;border-radius:14px;border:1px solid rgba(23,110,165,0.14);\">\n<h3 style=\"color:#0D1F3C;margin:0 0 8px;font-size:19px;\">What permissions should \/usr\/bin\/crontab have?<\/h3>\n<p style=\"margin:0;color:#1F2937;line-height:1.7;\">4755 (-rwsr-xr-x), owned by root, so normal users can manage their own cron jobs.<\/p>\n<\/div>\n<div style=\"margin-top:18px;background:#F8FAFC;padding:18px 20px;border-radius:14px;border:1px solid rgba(23,110,165,0.14);\">\n<h3 style=\"color:#0D1F3C;margin:0 0 8px;font-size:19px;\">Is vixie-cron still used?<\/h3>\n<p style=\"margin:0;color:#1F2937;line-height:1.7;\">No. Current Red Hat family systems use cronie, and Debian and Ubuntu use cron.<\/p>\n<\/div>\n<div style=\"margin-top:18px;background:#F8FAFC;padding:18px 20px;border-radius:14px;border:1px solid rgba(23,110,165,0.14);\">\n<h3 style=\"color:#0D1F3C;margin:0 0 8px;font-size:19px;\">How do I restore cron permissions safely?<\/h3>\n<p style=\"margin:0;color:#1F2937;line-height:1.7;\">Run rpm &#8211;setperms cronie and rpm &#8211;setugids cronie, or reinstall the package.<\/p>\n<\/div>\n<div style=\"margin-top:18px;background:#F8FAFC;padding:18px 20px;border-radius:14px;border:1px solid rgba(23,110,165,0.14);\">\n<h3 style=\"color:#0D1F3C;margin:0 0 8px;font-size:19px;\">Why do cPanel users get cron errors?<\/h3>\n<p style=\"margin:0;color:#1F2937;line-height:1.7;\">cPanel&#8217;s Cron Jobs page uses the crontab command. If its permissions are wrong, users cannot add or edit jobs.<\/p>\n<\/div>\n<div style=\"margin-top:18px;background:#F8FAFC;padding:18px 20px;border-radius:14px;border:1px solid rgba(23,110,165,0.14);\">\n<h3 style=\"color:#0D1F3C;margin:0 0 8px;font-size:19px;\">Do I need to restart cron after fixing permissions?<\/h3>\n<p style=\"margin:0;color:#1F2937;line-height:1.7;\">Not for the permissions themselves, but make sure crond is running and enabled.<\/p>\n<\/div>\n<\/div>\n<p><!-- uh-related-start --><\/p>\n<div style=\"background:#F4F8FC;border:1px solid #DCE7F3;border-radius:14px;padding:18px 22px;margin:32px 0 8px;\">\n<h2 style=\"margin:0 0 12px;font-size:22px;\">Related guides<\/h2>\n<ul style=\"margin:0;padding-left:20px;\">\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/underhost.com\/blog\/how-to-fix-cpanel-license-errors-after-ip-address-changes\/\">How to Fix cPanel License Errors After IP Address Changes<\/a><\/li>\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/underhost.com\/blog\/cpanel-tutorial-files-file-permissions\/\">cPanel Tutorial: Files &#8211; File Permissions<\/a><\/li>\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/underhost.com\/blog\/how-to-install-cpanel-on-centos-without-errors\/\">How to Install cPanel Without Errors<\/a><\/li>\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/underhost.com\/blog\/how-to-use-whms-email-deliverability-interface-to-fix-mail-dns-issues\/\">How to Use WHM\u2019s Email Deliverability Interface to Fix Mail DNS Issues<\/a><\/li>\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/underhost.com\/blog\/how-to-optimize-php-performance-in-cpanel-with-multiphp-manager-cloudlinux-php-selector\/\">How to Optimize PHP Performance in cPanel with MultiPHP Manager &amp; CloudLinux PHP Selector<\/a><\/li>\n<\/ul>\n<\/div>\n<p><!-- uh-related-end --><br \/>\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"What permissions should \/usr\/bin\/crontab have?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"4755 (-rwsr-xr-x), owned by root, so normal users can manage their own cron jobs.\"}}, {\"@type\": \"Question\", \"name\": \"Is vixie-cron still used?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Current Red Hat family systems use cronie, and Debian and Ubuntu use cron.\"}}, {\"@type\": \"Question\", \"name\": \"How do I restore cron permissions safely?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Run rpm --setperms cronie and rpm --setugids cronie, or reinstall the package.\"}}, {\"@type\": \"Question\", \"name\": \"Why do cPanel users get cron errors?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"cPanel's Cron Jobs page uses the crontab command. If its permissions are wrong, users cannot add or edit jobs.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need to restart cron after fixing permissions?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not for the permissions themselves, but make sure crond is running and enabled.\"}}]}<\/script><\/p>\n<h2 id=\"sources\" style=\"color:#0D1F3C;font-size:28px;line-height:1.25;margin:34px 0 14px;scroll-margin-top:90px;\"><i class=\"fas fa-book\" style=\"color:#00D4FF;\"><\/i> Sources<\/h2>\n<ul style=\"margin:0 0 24px;padding-left:22px;\">\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/man7.org\/linux\/man-pages\/man8\/rpm.8.html\">rpm manual page (verify and setperms options)<\/a><\/li>\n<li style=\"margin:0 0 8px;\"><a href=\"https:\/\/man7.org\/linux\/man-pages\/man1\/crontab.1.html\">crontab manual page<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Encountering the &#8220;\/usr\/bin\/crontab permissions are wrong. Please set to 4755&#8221; error in cPanel? Follow this simple guide to resolve it on RedHat, CentOS, or Fedora servers.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,202,25],"tags":[111,110,108,113,115,114],"class_list":["post-3523","post","type-post","status-publish","format-standard","hentry","category-control-panels","category-cpanel-whm","category-linux","tag-tag-almalinux","tag-tag-cloudlinux","tag-tag-cpanel","tag-tag-debian","tag-tag-linux-server","tag-tag-ubuntu"],"_links":{"self":[{"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/posts\/3523","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/comments?post=3523"}],"version-history":[{"count":9,"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/posts\/3523\/revisions"}],"predecessor-version":[{"id":6965,"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/posts\/3523\/revisions\/6965"}],"wp:attachment":[{"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/media?parent=3523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/categories?post=3523"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/underhost.com\/blog\/wp-json\/wp\/v2\/tags?post=3523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}