Version 3


    If you are running Jive in a multi-web app node cluster and a user is running into a problem then you may need to identify what web app node the user is logged into when they are experiencing the problem.


    Knowing what node a user is logged into can aid the troubleshooting and investigation process significantly. This can reduce the amount of logs you need to review or send to Jive Support, as well as potentially aid in identifying whether the issue is specific to a certain node or if it is affecting all web app nodes.



    When you are managing a Jive instance with multiple web app nodes, Jive requires that you set up a load balancer in front of the individual web app nodes. The load balancer will manage session affinity or sticky sessions. This is a feature of the load balancer that will assign a user to a specific web app node and keep them on that node as they continue to browse your Jive community.


    Jive Documentation: Configuring Session Affinity on a Load Balancer


    How to determine what node a user is on

    When you are using a load balancer with session affinity, the load balancer will save a special cookie to the end user's browser that it will later reference to keep the user on the same node as they browse from page to page.


    To determine what node a user is logged into you will need to find this cookie on the end user's browser and then inspect its contents to determine what web app node the load balancer is sending the user to.


    Please note, the specific steps in doing this will be different depending on what browsers your end users are using, what type of load balancer is used in your network, and how your load balancer is configured.  There are 4 general steps that are common for all cookie based load balancers:

    1. Find the load balancer cookie on the end user's browser
    2. Copy the cookie value
    3. Decrypt the cookie value (optional)
    4. Associate the decrypted cookie value to a specific web app address in your network


    Example of determining what node a user is logged in on

    In the example below we will be using Chrome, logging into Jive Community, which is using a F5 Load balancer.



    Using your browser's developer tools, or external development extensions, you can review a list of all cookies set for the site you are currently on.


    In this example, we know that the load balancer's cookie starts with BIGipServerpool...


    This is the cookie that the load balancer sets the first time you go to the Jive community and it later references to ensure that you stay on the same node from page to page:





    In chrome you can right click the cookie value and copy it to your clipboard.


    In this example, the value of the BIGip cookie is 3393367050.20480.0000


    You now need to decrypt the cookie value to something that tells you what node you are logged into.


    If you are using a F5 Load balancer then you can use the decryption tool at




    Here we can see that the cookie's decrypted value is


    This is the IP address of the web app node that the load balancer is sending you to for each page view.



    If this IP address is not enough information, you can use a command line look like nslookup to retrieve the hostname for a given IP address.  For example, you may run the following command:





    Finding cookies in different browsers

    There are a variety of ways of looking up cookies in your browser. If you are not able to find instructions for your browser below you may also find steps at 4 Ways to View Cookies - wikiHow or How do I view and control cookies in my web browser?


    1. Go to Settings > More Tools > Developer Tools
    2. In the developer tools panel go to Resources
    3. Expand Cookies on the left frame and select the domain for the page you are on
    4. Look for the load balancer cookie


    Screen Shot 2015-07-13 at 5.10.09 PM.png


    1. Go to Settings > Developer > Network
    2. Refresh the Jive page
    3. Select the network request for the HTML page on the left panel
    4. Select the Cookies tab on the right panel
    5. Look at the Request cookies in the right panel
    6. Look for the load balancer cookie

    Screen Shot 2015-07-13 at 5.14.01 PM.png

    Internet Explorer

    1. Go to Settings > F12 Developer Tools
    2. Select the Network tab
    3. Click the arrow to begin capturing network traffic
    4. Refresh the Jive page
    5. Scroll up to the top of the network panel and select the network request for the HTML page
    6. Double click the network request
    7. Select the Cookies tab in the panel
    8. Look for the load balancer cookie

    Screen Shot 2015-07-13 at 5.21.19 PM.png


    Related Materials

    How to Configure Your On-Prem Instance to Log into Individual Nodes for Testing