VISULOX 5 Documentation
5.0.2 5.0.1
5.0.2 5.0.1

Known Issues

  • Access Management

    • Reset OTP keys via Visulox Cockpit is not available for Unix users.

  • File Transit

    • Files with non-ASCII characters sometimes are presented wrong.

    • File names with special chars like "\ / : * ? " <> |" that are transferred to Windows servers will be substituted.

    • Visulox FTPD does not support IPv6.

    • If two persons are using the same user name to connect to a Unix application server, this can lead to an undefined behaviour regarding the Transit Zone.

    • For File Transfer within Command Connect, MaxSessions in sshd_config on the destination server has to be set at least to 2.
      With a MaxSession setting of 1, only the FT Client can be used without Command Connect.

  • Cooperation / Assistance

    • Assisting in seamless window mode can cause side effects.

    • If the source and destination displays in a cooperation have different keyboard layouts, this can cause side effects.

    • Dual Control is currently only possible in observation mode for members.

  • Objects

    • Character and doc applications are displayed in Visulox Cockpit / Online and Filter Objects, but these applications can not be selected in policies and can not be recorded, locked, etc.

  • Miscellaneous

    • Time zone interval for Bangalore / India is not a full hour.

    • Nested groups are not supported.

    • In a checked out ZIP archive special chars sometimes are not displayed properly on the info page.

    • Effective Policies in Cockpit / Online for Access and Application Policies are only displayed completely, if the Access Point has been provided.

    • Platform with SELINUX and Unix vlxtransit based on NFS Home Shares works only with NFS4.2.

    • AD LDAP paging with a pagesize of 100 can cause issues (an LDAP paging configuration parameter has been implemented)

    • IPv6 DNS compatibility issue in gateway setup.

    • Portal RPM upgrade overwrites custom nginx port config, breaks HTTPS access on port 443

    • XPRA screen fails to open when Connector advertises an invalid DNS hostname