If you are experiencing latency or other issues while working within the ClickClaims CMS application that cannot be resolved by utilizing other standard troubleshooting means, a ClickClaims support representative may ask you to manually change the server with which you're currently accessing the website to see if this resolves the issue. Please follow the steps below to view the web server you are on and to manually change it.
Verifying Web Server:
To verify what web server you are automatically being directed to when in CMS, follow the directions below.
- Navigate to your ClickClaims CMS site and log in to the application.
- The web server you are currently accessing is displayed on the far right-hand side of the blue header beneath the page name.
- CP4291
- cp3271
Figure 1: Example web server
Changing Your Web Server:
For troubleshooting purposes, you may be asked to manually change to a different server. Please follow the steps below to accomplish this.
- After logging in to ClickClaims CMS, make note of the current server (see Figure 1 above).
- Then, click inside of the address bar and remove ALL of the URL text located AFTER "...clickclaims.com/".
- Enter F5/status. (See Figure 2 and Figure 3 below.)
Figure 2: Example URL address before
Figure 3: Example URL address after
4. Click the "Enter" key on your keyboard. This will redirect you to the "LoadBalancer Status" page.
- Note: If the above steps did not redirect you to the "LoadBalancer Status" page, ensure you first successfully logged in to ClickClaims and then confirm the URL address was modified correctly per steps 2 and 3 above.
5. "Node 1" and "Node 2" are listed on the "LoadBalancer Status" page which represent each server.
- Node 1 (xxx.xxx.xxx.20) = CP4291
- Node 2 (xxx.xxx.xxx.60) = cp3271
Figure 4: 'LoadBalancer' Status page
- Node 1 if step 1 above showed a server name of cp3271. This will manually switch you from the cp3271 server to the CP4291 server.
- Node 2 if step 1 above showed a server name of CP4291. This will manually switch you from the CP4291 server to the cp3271 server.
Figure 5: Changed web server example