{"id":167,"date":"2026-06-01T12:30:35","date_gmt":"2026-06-01T09:30:35","guid":{"rendered":"https:\/\/mini-bucket.ru\/wiki\/?post_type=knowledgebase&p=167"},"modified":"2026-06-01T18:00:43","modified_gmt":"2026-06-01T15:00:43","slug":"mini-bucket-multi-net","status":"publish","type":"knowledgebase","link":"https:\/\/mini-bucket.ru\/wiki\/knowledge-base\/about-mini-bucket\/mini-bucket-multi-net\/","title":{"rendered":"Mini Bucket Multi-Net"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

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

What is it?<\/strong><\/h1>\n\n\n\n

Host Manager<\/strong> is a tool that turns multiple independent servers into a single manageable network. You log into one server (your “command center”), see a list of all connected servers, select any server \u2014 and get full access to its control panel<\/strong>, as if you logged into it directly. Switching between servers happens instantly, like switching between browser tabs.<\/p>\n\n\n\n

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

\n\n\n\n

The Main Idea<\/strong><\/h2>\n\n\n\n

You have many servers spread across different offices, cities, or even countries. Instead of remembering 10 addresses, 10 passwords, and keeping 10 browser bookmarks, you log into one<\/strong> server and from there manage all the others<\/strong>.<\/p>\n\n\n\n

But most importantly \u2014 the architecture does not restrict you with a rigid hierarchy. You decide who manages whom.<\/strong><\/p>\n\n\n\n

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

\n\n\n\n

What can you do?<\/strong><\/h2>\n\n\n\n

1. Switch between servers like browser tabs<\/strong><\/h3>\n\n\n\n
    \n
  • Open the control panel on your main server<\/li>\n\n\n\n
  • See a list of all connected servers<\/li>\n\n\n\n
  • Click on any server \u2014 the interface\u00a0switches<\/strong>\u00a0to managing that server<\/li>\n\n\n\n
  • Get access to all its functions: metrics, settings, file management, backups \u2014\u00a0everything<\/strong>\u00a0you have on your main server<\/li>\n<\/ul>\n\n\n\n

    2. Remember nothing<\/strong><\/h3>\n\n\n\n
      \n
    • No need to remember each server’s IP address<\/li>\n\n\n\n
    • No need to store separate logins and passwords<\/li>\n\n\n\n
    • No need to keep 10 browser tabs open<\/li>\n<\/ul>\n\n\n\n

      3. Build flexible hierarchies with unlimited nesting<\/strong><\/h3>\n\n\n\n

      The system does not limit you to a “one master \u2014 all others are slaves” scheme. You can build any structure:<\/p>\n\n\n\n

        \n
      • A Level 10 server obeys its direct master (Level 10)<\/li>\n\n\n\n
      • And simultaneously \u2014 a Level 8 server<\/li>\n\n\n\n
      • And a Level 5 server<\/li>\n\n\n\n
      • And the main Level 0 server<\/li>\n<\/ul>\n\n\n\n

        One server can be a slave to multiple masters at different levels.<\/strong><\/p>\n\n\n\n

        4. Be both a master and a slave simultaneously<\/strong><\/h3>\n\n\n\n
          \n
        • A Level 7 slave can be a master for a Level 3 slave<\/li>\n\n\n\n
        • The same server \u2014 both obeys others and manages others<\/li>\n<\/ul>\n\n\n\n

          5. Transfer control temporarily<\/strong><\/h3>\n\n\n\n
            \n
          • If a regional administrator goes on vacation \u2014 another temporarily gets control of their servers<\/li>\n\n\n\n
          • When the first returns \u2014 control is transferred back<\/li>\n<\/ul>\n\n\n\n

            6. Control access selectively<\/strong><\/h3>\n\n\n\n
              \n
            • Each server decides who can manage it<\/li>\n\n\n\n
            • You can give access to the main office but not to an intermediate level<\/li>\n\n\n\n
            • Or vice versa<\/li>\n<\/ul>\n\n\n\n

              7. Accept or reject connection requests<\/strong><\/h3>\n\n\n\n
                \n
              • When another server wants to connect to you \u2014 you receive a request<\/li>\n\n\n\n
              • You decide: do you trust this server or not?<\/li>\n\n\n\n
              • All unconfirmed requests sit in a queue and don’t interfere with work<\/li>\n<\/ul>\n\n\n\n

                8. Rotate access keys (for security)<\/strong><\/h3>\n\n\n\n
                  \n
                • If an access key is compromised \u2014 you generate a new one with one click<\/li>\n<\/ul>\n\n\n\n

                  9. Turn “reception mode” on or off<\/strong><\/h3>\n\n\n\n
                    \n
                  • There is a switch that allows or denies other servers from sending you connection requests<\/li>\n<\/ul>\n\n\n\n

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

                    \n\n\n\n

                    Key Principle: Multiple Masters, Not Automatic Hierarchy<\/strong><\/h2>\n\n\n\n

                    The system does not build hierarchy automatically “from top to bottom.”<\/strong><\/p>\n\n\n\n

                    If a Level 0 master wants to manage a Level 10 slave, it is not enough for the Level 0 master to be “higher up the chain.”<\/p>\n\n\n\n

                    For direct management, each master must be explicitly added to the target server’s master list.<\/strong><\/p>\n\n\n\n

                    How it works<\/strong><\/h3>\n\n\n\n

                    On the Slave 10<\/strong> server, in its control panel, the master list might look like:<\/p>\n\n\n\n

                    My masters (who can manage me):\n\u251c\u2500\u2500 Master 10 (direct supervisor)\n\u251c\u2500\u2500 Master 5  (higher-level administrator)\n\u251c\u2500\u2500 Master 0  (main IT director)\n\u2514\u2500\u2500 Master 8  (neighboring regional administrator, temporary)<\/pre>\n\n\n\n
                    All of them can switch to Slave 10 and manage it as their own.<\/p>\n\n\n\n
                    Why this approach?<\/strong><\/h3>\n\n\n\n
                    Automatic Hierarchy (Traditional Systems)<\/th>Flexible Scheme (Host Manager)<\/th><\/tr><\/thead>
                    Master 0 automatically manages EVERYTHING<\/td>Master 0 only manages those explicitly added to him<\/td><\/tr>
                    Cannot exclude anyone from management<\/td>Can grant access selectively<\/td><\/tr>
                    Everyone sees everything (or nothing)<\/td>Each sees exactly what they are allowed to see<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                    <\/p>\n\n\n\n
                    \n\n\n\n
                    Who is this for?<\/strong><\/h2>\n\n\n\n
                    User<\/th>How they use it<\/th><\/tr><\/thead>
                    System Administrator<\/strong><\/td>Manages dozens of servers from one panel, switching between them instantly<\/td><\/tr>
                    Company Owner<\/strong><\/td>Keeps office server, cloud server, and backup server under control from one place<\/td><\/tr>
                    IT Integrator<\/strong><\/td>Sets up a single management point for multiple client sites<\/td><\/tr>
                    Large Organization with Branches<\/strong><\/td>Builds hierarchy: HQ \u2192 Regions \u2192 Cities \u2192 Departments<\/td><\/tr>
                    Homelab Enthusiast<\/strong><\/td>Connects home NAS, cottage server, and VPS into one network<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                    <\/p>\n\n\n\n
                    \n\n\n\n
                    Real-World Examples<\/strong><\/h2>\n\n\n\n
                    Example 1: Simple Network<\/strong><\/h3>\n\n\n\n
                    \n
                    You have three servers: at the office, in the cloud, and at a partner’s site.<\/p>\n\n\n\n
                    Without Host Manager:<\/strong> Three different addresses, three passwords, three browser tabs.<\/p>\n\n\n\n
                    With Host Manager:<\/strong> Log into your office server, see a list of three servers. Click on the cloud server \u2014 the panel switches to it. Click on the partner’s server \u2014 switches to it. All functions \u2014 right there.<\/p>\n<\/blockquote>\n\n\n\n
                    Example 2: Large Retail Chain<\/strong><\/h3>\n\n\n\n
                    \n
                    Levels:<\/strong><\/p>\n\n\n\n
                      \n
                    • Level 0 \u2014 Headquarters (IT Director)<\/li>\n\n\n\n
                    • Level 1 \u2014 5 Regional Centers (Regional Administrators)<\/li>\n\n\n\n
                    • Level 2 \u2014 50 Stores (each with its own server)<\/li>\n<\/ul>\n\n\n\n
                      What you get:<\/strong><\/p>\n\n\n\n
                        \n
                      • Regional administrator manages stores in their region<\/li>\n\n\n\n
                      • Neighboring regional administrator temporarily gets control while a colleague is on vacation<\/li>\n\n\n\n
                      • Main IT director can take direct control of any store at any moment<\/li>\n\n\n\n
                      • A store can simultaneously obey both its regional administrator and headquarters<\/li>\n<\/ul>\n<\/blockquote>\n\n\n\n
                        Example 3: Temporary Management Transfer<\/strong><\/h3>\n\n\n\n
                        \n
                        Situation:<\/strong> A regional administrator is sick or on vacation.<\/p>\n\n\n\n
                        Solution:<\/strong> On the servers they managed, an additional master is temporarily added \u2014 the substitute administrator. When the first returns \u2014 the additional master is removed.<\/p>\n<\/blockquote>\n\n\n\n
                        Example 4: Selective Access<\/strong><\/h3>\n\n\n\n
                        \n
                        Situation:<\/strong> Headquarters should not see every small server in the branches \u2014 only key nodes.<\/p>\n\n\n\n
                        Solution:<\/strong> Headquarters is added as a master only on those servers that should be visible to them. The rest remain “invisible” to headquarters.<\/p>\n<\/blockquote>\n\n\n\n
                        <\/p>\n\n\n\n
                        \n\n\n\n
                        What you get in the end<\/strong><\/h2>\n\n\n\n
                        Capability<\/th>How it’s implemented<\/th><\/tr><\/thead>
                        Single point of entry<\/td>One server \u2014 access to all<\/td><\/tr>
                        Instant switching<\/td>Click on a server \u2014 you manage it<\/td><\/tr>
                        Unlimited nesting<\/td>Level 10 server can be managed from any level<\/td><\/tr>
                        Multiple masters per slave<\/td>Server can obey any number of masters<\/td><\/tr>
                        Temporary control transfer<\/td>Add temporary master \u2192 remove later<\/td><\/tr>
                        Selective access<\/td>Don’t add a master to the server’s list<\/td><\/tr>
                        No automatic inheritance<\/td>Each relationship is created manually<\/td><\/tr>
                        Full functionality on remote server<\/td>Not limited monitoring, but full management<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                        <\/p>\n\n\n\n
                        \n\n\n\n
                        Brief overview of the connection process<\/strong><\/h2>\n\n\n\n
                        To add a new server to your “command center”:<\/p>\n\n\n\n
                          \n
                        1. The remote server sends a connection request<\/li>\n\n\n\n
                        2. You see this request in your panel<\/li>\n\n\n\n
                        3. You review and accept it (if you trust it)<\/li>\n\n\n\n
                        4. After this, the server appears in your list<\/li>\n\n\n\n
                        5. You can switch to it and manage it<\/li>\n<\/ol>\n\n\n\n
                          Important:<\/strong> If you want this server to also be able to manage you \u2014 you need to add the reverse connection as well.<\/p>\n\n\n\n
                          <\/p>\n\n\n\n
                          \n\n\n\n
                          Important Warning<\/strong><\/h3>\n\n\n\n
                          For Host Manager to work correctly, all hosts (servers) in the network must meet the following requirements:<\/p>\n\n\n\n
                          Requirement<\/th>Description<\/th><\/tr><\/thead>
                          HTTPS<\/strong><\/td>All hosts must be configured to use HTTPS. HTTP is not supported for cross-server communication.<\/td><\/tr>
                          DNS names<\/strong><\/td>Each host must have a DNS name (domain). Using IP addresses is not allowed for proper server switching functionality.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          About Certificates<\/strong><\/h3>\n\n\n\n
                            \n
                          • Both\u00a0paid<\/strong>\u00a0(issued by a trusted Certificate Authority) and\u00a0self-signed<\/strong>\u00a0certificates are acceptable.<\/li>\n\n\n\n
                          • When using self-signed certificates,\u00a0it is strongly recommended to add them to the trusted store<\/strong>\u00a0on all hosts that will connect to them.<\/li>\n\n\n\n
                          • This will prevent browser warnings and errors when switching between servers.<\/li>\n<\/ul>\n\n\n\n
                            \n
                            Note:<\/strong> Without properly configured DNS names and HTTPS, cross-server switching may work incorrectly or be completely unavailable.<\/p>\n<\/blockquote>\n\n\n\n
                            <\/p>\n\n\n\n
                            \n\n\n\n
                            Post date: 01.06.2026<\/p>\n\n\n\n
                            <\/p>\n","protected":false},"excerpt":{"rendered":"
                            What is it? Host Manager is a tool that turns multiple independent servers into a single manageable network. You log into one server (your “command center”), see a list of all connected servers, select any server \u2014 and get full access to its control panel, as if you logged into it directly. Switching between servers happens instantly, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","knowledgebase_cat":[35],"class_list":["post-167","knowledgebase","type-knowledgebase","status-publish","hentry","knowledgebase_cat-about-mini-bucket"],"_links":{"self":[{"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/knowledgebase\/167","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/knowledgebase"}],"about":[{"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/types\/knowledgebase"}],"author":[{"embeddable":true,"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/comments?post=167"}],"version-history":[{"count":4,"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/knowledgebase\/167\/revisions"}],"predecessor-version":[{"id":176,"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/knowledgebase\/167\/revisions\/176"}],"wp:attachment":[{"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/media?parent=167"}],"wp:term":[{"taxonomy":"knowledgebase_cat","embeddable":true,"href":"https:\/\/mini-bucket.ru\/wiki\/wp-json\/wp\/v2\/knowledgebase_cat?post=167"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}