Skip to content

IP Fabric v7.6

Upgrade Version Policy

We support the following upgrade paths:

  • The latest version in the previous major line → any version in the current major line (for example: 6.10.7 → 7.3.23).
  • Any version in the current major line → any newer version in the current major line (for example: 7.0.15 → 7.3.23).
  • An upgrade to 7.5.x can be only performed from version 7.3.23 or newer.

Clearing Browser Cache

After upgrading IP Fabric to a newer version, you should see the Your application has been updated and must be refreshed dialog in the main GUI.

It is usually sufficient to just click the Refresh button.

However, in case of issues with the main GUI or if you did not see the mentioned dialog, please force refresh your browser cache.

The key combination for doing this depends on your operating system. In your browser window with your IP Fabric appliance’s URL open, use one of the following key combinations:

  • Windows: Ctrl + F5
  • macOS: Command + Shift + R
  • Linux: Ctrl + F5

This will only affect the browser cache for the IP Fabric appliance.

Known Issues

There are currently no known issues in IP Fabric version 7.6.

v7.6.1 (October 27th, 2025, Private Release)

Potential Race Conditions and File Conflicts During Upgrade

A race condition in the appliance upgrade process could cause misleading error messages during upgrades. We also fixed cases where upgrades could fail due to configuration files that had been incorrectly created or modified in the past. Both issues are now resolved and should no longer occur.

Removal of ArangoDB

ArangoDB has been completely removed in this release, including all related dependencies and custom configuration options.

New Features

System upgrade via CLI

A new command-line tool /opt/ipf-system-upgrade/bin/cli now enables performing system upgrades in the same way as through the web interface.

Improvements

API logging

The ipf-api component now writes logs to /var/log/ipf/ipf-api/ instead of forwarding them to syslog.

Improved PostgreSQL Migration Process

We have addressed edge cases where PostgreSQL might not have been configured correctly during upgrades. Additional checks and safeguards now ensure consistent and reliable system configuration. The installation process has also been improved to better handle dependencies between the product and PostgreSQL.

Simplified TechSupport Exports

Logs from cloud-init are now excluded from TechSupport exports.

Additional Disk-space Checks During Upgrade

Added a pre-upgrade check for available disk space to prevent the appliance from running out of space during an upgrade.

Jumphost Logs Included in TechSupport Exports

The ipf-jumphost service, which has logged to /var/log/ipf/ipf-jumphost/ since release 7.0 to keep its logs separate from system logs, now includes these logs in TechSupport exports to assist with troubleshooting.

Upgraded Node.js to v22.19.0

All JavaScript-based services are now running on Node.js version v22.19.0.

Database and RabbitMQ Credentials Moved Out of Built Code

Previously, due to how the application configuration was managed through a JSON file, several credentials were embedded directly into the built JavaScript code. This is no longer the case — credentials are now automatically generated and supplied via environment variables. The default RabbitMQ guest account has been removed. Only internal, non-management accounts are now used for communication between the application and the message broker.

API Changes

Endpoint payload size limit

The payload size limit has been introduced with a default of 20 MB, except for the following endpoints with their respective limits:

  • /appliance-configuration/import -> 100 MB
  • /extensions/docker-image -> 2 GB
  • /extensions/docker-zip -> 10 GB
  • /licenses/upload -> 5 MB
  • /snapshots/upload -> 10 GB
  • /graphs/vsdx -> 25 MB
  • /os/upload-nimpee-cert -> 5 MB
  • PATCH /settings -> 100 MB

Other Changes

  • The system status page is now accessible only after login.
  • The license upload endpoint is now protected by authentication and accessible only to admin users.
  • When a user changes their password, all active sessions for that user are invalidated.
  • Session token is now invalidated upon logout.
  • The built-in Role-Based Access Control (RBAC) policy previously named others (ID: read) has been renamed for improved clarity.
    • Despite its ID, this policy also permits write operations for saved filters and graphs. The rename helps better reflect its actual permissions and avoid confusion between read-only and read/write capabilities.