Summary of Network Interception Issues

When you use FineBI, network interception issues may sometimes cause errors or problems. This article provides methods for troubleshooting and resolving these issues.

Problems

1. Loss of Network Connection

l Network Disconnected on Local or Server: Unable to save platform configurations, dashboard creation, and dataset modification. Or prompt: The local or server network has been disconnected. Please try again after connecting to the network. 

l When deleting a dashboard or self-service dataset, it prompts that The local or server network has been disconnected. Please try again after connecting to the network. 

2. Blank Page

After clicking Add SQL dataset, the page becomes blank.

Cause

• Problems caused by forwarding or domain name configuration

• Network interception of request headers containing special characters

• Server shutdown

• Problems with web.xml configuration.

Checking Domain Name IP

Check whether the current access address is configured for domain name access. If so, log in to the system directly using the server's IP for operation and verification. If there is no abnormality in the operation, it indicates a domain name issue and you should contact the network operation and maintenance personnel for help.

Checking Nginx Configuration

Check whether the environment is configured with an Nginx server. If it is, log in using the server's IP to verify. If there is no abnormality in the operation, it indicates an Nginx configuration issue.

Checking Current Network Requests

1. Open the console by pressing F12 key and check the current network requests. Click network to check if there are any 502 or 403/404 errors.

2. Check if there are a large number of requests with network timeout errors on the console page.

3. If there are such errors, it means that the requests are abnormally intercepted. Contact network maintenance personnel to confirm whether there is interception for requests containing special characters.

Checking FineBI Server Running Status

Check the FineBI server process and refresh the page to see if the system can still be accessed normally. If not, ensure that the FineBI process is running normally.

Checking web.xml Configuration

Check whether there is a web.xml file in %FineBI%/webroot/WEB-INF. If there is, confirm whether there is interception or forwarding of requests in the file.