--- title: "View and edit a load balancer's details" description: "Read an E2E load balancer's Info tab, rename it, change its timeouts, and turn BitNinja on or off for it in MyAccount." content_type: "how-to" product: "load-balancer" platform: "MyAccount" url: "/myaccount/load-balancer/how-to/view-and-edit-details/" topic: ["operate"] relationships: {"requires":["/myaccount/load-balancer/how-to/create-an-application-load-balancer/"]} --- # View and edit a load balancer's details A load balancer's **Info** tab shows its addresses, plan, and settings, and lets you change its name, its timeouts, and BitNinja. It is available in every status. The frontend protocol and the SSL certificate are edited on the same tab; see [Add an SSL certificate](/myaccount/load-balancer/how-to/add-an-ssl-certificate/). ## Before you begin - The load balancer is powered on and has left **Creating**, **Deploying**, or **Upgrading**, since the **Info** tab can be edited only then. Otherwise, an edit is refused with a message that names the status, such as: ```text You can't edit Load Balancer in 'Powered off' state. ``` - Your role in the project has the update permission for **Load Balancers**. ## Read the Info tab In MyAccount, under **Compute**, click **Load Balancers**, click the load balancer, and open its **Info** tab. The **Basic** panel shows: - **Load Balancer Name**, with the type under it. - **Public IP**, on an external load balancer, with **Reserve Public IP** to keep the address. It reads **None** when there is no public IP. - **Private IP**, the load balancer's private IP while no VPC is attached. With a VPC, it reads **Not Assigned**, and the VPC address is in the list's **Private IP** column and on the **Network** tab. - **Plan Name**, with **Upgrade Plan**, and **Configuration**, the plan's RAM, vCPU, and storage. - **Price**, and on a committed plan **Active Committed Plan**, **Committed Period Ends On**, and **Committed Node Settings**. See [Use committed billing](/myaccount/load-balancer/how-to/use-committed-billing/). - **Access Details**, which says whether access logs are on. See [Save access logs to a bucket](/myaccount/load-balancer/how-to/save-access-logs-to-a-bucket/). - **Frontend Protocol**: **HTTP**, **HTTPS**, or **BOTH** on an Application Load Balancer, and **TCP** on a Network Load Balancer. - **SSL**, on an Application Load Balancer: the certificate it uses. - **LB Listening Port**: 80 for **HTTP**, and 443 for **HTTPS** or **Both (HTTP and HTTPS)**. On a Network Load Balancer, the first backend group's listening port. - **Created On**, and **Last modified on**, when the load balancer's settings were last saved. It moves with each saved change, such as an edit, a VPC or access-log change, **Power Off**, **Start**, or **Upgrade Plan**, and stays as it is when a deploy finishes. The **Peak Performance Features** panel shows **Bitninja**, **HTTP Redirect** on an Application Load Balancer, and the four timeouts, each with **Edit**. ## Rename the load balancer 1. On the **Info** tab, click **Edit** beside **Load Balancer Name**. 2. Enter the new **Name**, up to 50 characters, using letters, digits, underscores, and hyphens. Leave the other fields as they are. 3. Click **Submit**. Saving starts **Deploying**, which takes about 5 to 10 minutes. If nothing changed, **You have not made any changes.** shows instead. ## Change the timeouts 1. On the **Info** tab, under **Peak Performance Features**, click **Edit** beside a timeout. 2. Enter new values for the timeouts you want to change. Each takes 60 to 10000 seconds. 3. Click **Submit**. The load balancer reads **Deploying** until the change is applied. A timeout change takes about 35 seconds to go from **Deploying** back to **Running**. Connections already open through the load balancer are kept while it applies the new timeouts. When users of a slow page see a timeout from the load balancer, raise **Server Timeout** first, since it sets how long the load balancer waits for your server to reply. For what the other timeouts do, see the timeouts in [Create an Application Load Balancer](/myaccount/load-balancer/how-to/create-an-application-load-balancer/#optional-change-the-timeouts). ## Turn BitNinja on or off BitNinja is a security service that guards servers against attacks. Each load balancer has its own BitNinja licence, charged per calendar month while it is active. For current prices, see [E2E's pricing page](https://www.e2enetworks.com/pricing). **Bitninja** under **Peak Performance Features** reads **Enabled** or **Disabled**. To turn it on: 1. Click **Buy** beside **Bitninja**. **BitNinja** opens with the monthly charge for the licence, taken from your infra credits on a prepaid account. 2. Click **Buy**. **License purchased successfully** confirms it, and E2E emails you about the activation. Click **ok**. 3. Follow the instructions in the email to finish activating BitNinja on the load balancer. The load balancer keeps its status while BitNinja is set up. To turn BitNinja off, click **Terminate** beside **Bitninja**, and confirm with **Terminate**. You lose BitNinja's protection, and buying it again later is charged as a new licence. **License terminated successfully** confirms it. You can also turn it on when you create the load balancer, by ticking **Bitninja** on **Peak Performance Features**. Deleting the load balancer also deletes its BitNinja licence. ## Check your change When the load balancer reads **Running** again, the **Info** tab shows the new name or timeouts, and **Last modified on** shows when you saved the change. **Bitninja** shows whether BitNinja is **Enabled** or **Disabled**. To change its plan, see [Power off, start, or upgrade a load balancer](/myaccount/load-balancer/how-to/power-off-start-or-upgrade/). If a change is refused, see [Troubleshooting Load Balancer](/myaccount/load-balancer/troubleshooting/load-balancer/).