1. After debugging, there is no response when aggregating the interface. How to solve it?

Answer: When debugging, if you find that there is no response, please pay attention to the request header of the response, and click on the request response body tab to check the return context during the test to check the error information in the returned response body. Or turn on the debug mode and check the error information in the log.

  1. How to access after configuring routing?

Answer: The request address of FizzGate is currently: http://{ip}:{port}/proxy/{my_service}/{api_path}. Where {my_service} is the service group you configured, and {api_path} is your routing address.

  1. How to distinguish forwarded addresses?

Answer: At this stage, FizzGate supports two forwarding modes, request path forwarding | forwarding to the specified back-end service. If it is request path forwarding, that is, forwarding through service name + path, generally forwarding to the service orchestration interface, or in the registration center (Eureka ) registered services. There are two forwarding situations for forwarding to the specified backend service. If http://{ip|dns}:{port}/path_to_api is configured, it is http protocol forwarding, and if http://{my-service}/ is used {api_path2}, which is the registration center forwarding, is generally used to expose the inconsistency between the API address and the internal address.

  1. When executing the management background SQL script, an error occurs: ERROR 1071 (52000): Specified key was too long; max key length is 767 bytes. How to solve it?

Answer: The reason is due to the index length limit of the InnoDB table in the MySQL database. Just set the MySQL database parameter innodb_large_prefix=ON and re-execute the script.

  1. An error occurs when the management backend server starts: FlowableException: couldn't create db schema: alter table ACT_RU_VARIABLE. How to solve it?

Answer: The reason is that Flowable uses all-capital table names to operate the MySQL database. When the MySQL database is case-sensitive, it cannot read the table created by the script. Just set the MySQL database parameter lower_case_table_names=1 and restart the service.

  1. How to solve the problem when calling the gateway interface and responding with {"msgCode":403,"message":"xxxxxx-x no api config"}?

Answer: The reason is that the gateway cannot find the corresponding routing rules. Use the backend routing management function to set routing rules for the accessed services, save them and access the interface again.

  1. The JS call I wrote keeps reporting errors, how to solve it?

Answer: Check whether the JS directory in the source code has been placed under the same level directory of the fizz-gateway-node.jar package.

  1. The backend configuration is normal, but a 404 appears in the request response?

Answer: A request response {"msg":"Unknown system exception [HttpStatus]:400","code":400,"data":"",success:false} appears. Your request is sent to the fizz-manager service, which is a service for the backend management interface. The professional version of FizzGate needs to be used in conjunction with the community version fizz-gateway. Please confirm whether the request is sent to the fizz-gateway service normally.

  1. Click the gateway log menu and find that the gateway log record is empty?

Answer: Question is the same as 8.

  1. A specific route is configured, but it does not take effect?

Answer: Confirm that the application.yml file of fizz-gateway has the configuration of need-auth: true.

  1. Configure a specific route, check the log and find that the requested address is missing [SERVER_NAME], causing the request to appear "response 404 NOT FOUND?"

Answer: The request log is normally: 2021-02-19 18:29:46.953 [fizz-el-nio-3] INFO we.filter.FizzGateLogFilter - 5dcc5b98-20 41de6627-47 GET http://127.0.0.1:8600/ admin/cache/gatewayGroups response 200 OK in 2 2021-02-19 18:29:46.955 [wc-proxy-el-nio-1] INFO reactor.Mono.PeekTerminal.7 - | onNext(org.springframework.web.reactive.function.client.DefaultClientResponse@40bc5051) 2021-02-19 18:29:46.956 [wc-proxy-el-nio-1] DEBUG we.filter.RouteFilter - ef9b8d3a-46 response 200 OK 2021-02-19 18:29:46.958 [wc-proxy-el-nio-1] INFO reactor.Mono.PeekTerminal.7 - | onComplete() 2021-02-19 18:29:46.960 [fizz-el-nio-2] INFO we.filter.FizzGateLogFilter - ef9b8d3a-46 ef9b8d3a-46 GET http://127.0.0.1:8600/proxy/service1/hello1 response 200 OK in 19 If you find that http://127.0.0.1:8600/admin/cache/gatewayGroups is 404, you need to bring [SERVER_NAME], such as http://127.0.0.1:8600/[SERVER_NAME]/admin/cache/gatewayGroups. Then the configured forwarding path needs to be filled in as: /[SERVER_NAME]/admin/cache/gatewayGroups. Routing result: /service1/hello1 forwarded to: /[SERVER_NAME]/[SERVER_NAME]/admin/cache/gatewayGroups. It is recommended to configure the context-path of the backend service.

  1. Sending a request reported at we.plugin.FixedPluginFilters(FixedPluginFilter.java：73) ~[classes/:?] error.

Answer: Please confirm that the startup function is the FizzGatewayApplication main() function. If it is eclipse, it is recommended to right-click the main function in the code.

  1. Unable to switch menus in the background management interface

Answer: Please check if there is a resource error on the front end, net::ERR_INCOMPLETE_CHUNKED_ENCODING, which indicates that nginx’s temporary files are restricted and the files are not fully loaded. You can set the following settings in the Nginx configuration: server { proxy_max_temp_file_size 0;}

  1. After deployment, a SQL error is reported when logging in to the background: this is incompatible with sql_mode=only_full_group_by

Answer: Please refer to https://www.cnblogs.com/wxw7blog/p/10021563.html to remove the sql_mode restriction.

← Roadmap →