{"id":207,"date":"2021-07-23T12:19:20","date_gmt":"2021-07-23T12:19:20","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/reserved-invalid-and-misconfigured-usernames\/"},"modified":"2021-07-23T12:19:20","modified_gmt":"2021-07-23T12:19:20","slug":"reserved-invalid-and-misconfigured-usernames","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/reserved-invalid-and-misconfigured-usernames\/","title":{"rendered":"Reserved, Invalid, and Misconfigured Usernames"},"content":{"rendered":"<\/p>\n
\n
<\/div>\n
\n

Overview<\/h2>\n

This document explains cPanel & WHM\u2019s username restrictions and what to do if you encounter an invalid, reserved, or misconfigured username.<\/p>\n

Basic restrictions<\/h2>\n

cPanel & WHM applies the following rules when you create or modify a cPanel or WHM username:<\/p>\n

Usernames may only<\/strong> use lower letters (a\u2013z<\/code>) and digits (0\u20139<\/code>).<\/p>\n

    \n
  • Usernames cannot<\/strong> contain more than 16 characters.<\/li>\n
  • Usernames cannot<\/strong> begin with a digit (0\u20139<\/code>) or the string test<\/code>.<\/li>\n
  • Usernames cannot<\/strong> end with the string assword<\/code>.<\/li>\n<\/ul>\n

    Special cases<\/h3>\n
      \n
    • You cannot<\/strong> create a username with the hyphen character (-<\/code>), but you can change an account\u2019s name to use a hyphen when you transfer that account to another system.<\/li>\n
    • To allow usernames over eight characters in length, set the LONGUSERS: 1<\/code> environment variable in the \/var\/cpanel\/whm\/nvdata\/root.yaml<\/code> file.<\/li>\n
    • If you plan to use MySQL\u00ae or PostgreSQL\u00ae as a database engine, the first eight characters must<\/strong> be unique on the system.\n
      \n
      Note:<\/div>\n
      \n

      You can disable database prefixing with the Add prefix to names of new databases and database users option in the SQL section of WHM\u2019s Tweak Settings<\/em> interface (WHM >> Home >> Server Configuration >> Tweak Settings<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n

    • To allow leading digits in a username, create the \/etc\/allowstupidstuff<\/code> touch file.<\/li>\n<\/ul>\n

      Reserved usernames<\/h2>\n
      \n
      Important:<\/div>\n
      \n During TSR-2017-0006, we expanded the list of reserved usernames to include email aliases listed in the \/etc\/aliases<\/code> and \/etc\/localaliases<\/code> files. The system will also reserve usernames that are aliased to a reserved username.\n <\/div>\n<\/div>\n

      cPanel & WHM reserves some usernames for the system\u2019s use, and you cannot use them for cPanel or WHM accounts. This list of reserved usernames can grow over time, and new versions of cPanel & WHM may add to this list.<\/p>\n

      cPanel & WHM checks the following files to determine whether to reserve or restrict a username or alias:<\/p>\n

        \n
      • \/usr\/local\/cpanel\/Cpanel\/Validate\/Username\/Core.pm<\/code><\/li>\n
      • \/etc\/aliases<\/code><\/li>\n
      • \/etc\/localaliases<\/code><\/li>\n<\/ul>\n

        Reserved aliases<\/h3>\n

        By default, the system reserves the following list of aliases:<\/p>\n\n\n\n\n\n\n\n\n\n
        Username<\/th>\nAlias<\/th>\n<\/tr>\n<\/thead>\n
        root<\/code><\/td>\nabuse, adm, amandabackup, apache, bin, canna, daemon, dbus, decode, desktop, dovecot, dumper, fax, ftp, games, gdm, gopher, halt, hostmaster, ident, ingres, ldap, lp, mail, mailnull, manager, mysql, named, netdump, news, nfsnobody, nobody, noc, nscd, ntp, nut, operator, pcap, postfix, postgres, postmaster, privoxy, pvm, quagga, radiusd, radvd, root, rpc, rpcuser, rpm, security, shutdown, smmsp, squid, sshd, sync, system, toor, uucp, vcsa, webalizer, webmaster, wnn, xfs<\/code><\/td>\n<\/tr>\n
        postmaster<\/code><\/td>\ninfo, mailer-daemon, marketing, sales, support<\/code><\/td>\n<\/tr>\n
        news<\/code><\/td>\nnewsadm, newsadmin, usenet<\/code><\/td>\n<\/tr>\n
        ftp<\/code><\/td>\nftp-adm, ftp-admin, ftpadm, ftpadmin<\/code><\/td>\n<\/tr>\n
        webmaster<\/code><\/td>\nwww<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Resolve problems<\/h2>\n

        To resolve issues with invalid, reserved, or restricted usernames or aliases, perform run the following command as the root user to rename the account:\n<\/p>\n

        \n
        whmapi1 modifyacct user=<\/span>username newuser=<\/span>newusername<\/code><\/pre>\n<\/div>\n
        \n
        Note:<\/div>\n
        \n
        In this example, username<\/code> represents the current (restricted) username, and newusername<\/code> represents the new username that you wish to assign to the account.<\/p>\n<\/p><\/div>\n<\/div>\n
        Remove username aliases<\/h3>\n
        You can also remove reserved aliases from the \/etc\/aliases<\/code> and \/etc\/localaliases<\/code> files.<\/p>\n
        Misconfigured usernames<\/h3>\n
        Misconfigured usernames do not possess some information or exist in an incomplete state. To fix a misconfigured username, run the following command as the root user:\n<\/p>\n
        \n
        \/usr\/local\/cpanel\/scripts\/updateuserdomains --force<\/code><\/pre>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"
        Overview This document explains cPanel & WHM\u2019s username restrictions and what to do if you encounter an invalid, reserved, or misconfigured username. Basic restrictions cPanel & WHM applies the following rules when you create or modify a cPanel or WHM username: Usernames may only use lower letters (a\u2013z) and digits (0\u20139). Usernames cannot contain more …<\/p>\n","protected":false},"author":1,"featured_media":208,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/207"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=207"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/207\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/208"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}