Known Issues

Summary of known issues for this release.

Known issues in this release include:

MiNiFi Java GetFile processor ignores 'Ignore Hidden File' property
EFM metrics for connection queues can be inaccurate for single-node deployments
EFM repository usage views do not show data or can be inaccurate
EFM cannot talk to NiFi Registry over HTTPS if using TLS certificates that have international characters in the DN
Browser back navigation does not work in parts of the EFM web app
Recent versions of browsers, including Chrome and Firefox, blocks HTTP, HTTPS, and FTP access to TCP port 10080 to prevent the ports from being abused in NAT Slipstreaming 2.0 attacks.

Workaround: In case of an error message saying could not connect to server in the browser, you need to change the port being used by EFM. You can set a different value for the efm.server.port property in the efm.properties file. You need to restart EFM for the change to be effective. The change also needs to be reflected on the agents to ensure proper communication.