Visitar URL original
How to ugrade phpIPAM from an older version · Issue #4654 · phpipam/phpipam · GitHub
Skip to content

How to ugrade phpIPAM from an older version #4654

Open

Description

@matthewhinchliffe1975

We are currently running Installed version: 1.5.3.

I am looking to upgrade the most recent version available, I attempted to upgrade to version 1.8.2 however this failed when trying to run the upgrade from the browser.

Being that we are on version 1.5.3, do I need to upgrade in stages ? If so, could someone give me an upgrade path.

Thanks

Activity

  1. matthewhinchliffe1975 commented on Sep 9, 2026

    @matthewhinchliffe1975
    Author

    I meant to add the following

    Database Schema Version : 1.53 dbversion 39
    PHP Version: 7.2.30-1+ubuntu18.04+deb.sury.org+1
    MySQL Version: 10.3.22-MariaDB-1:10.3.22+maria~bionic-log
    MySQL CTE queries: Yes

  2. GaryAllan commented on Sep 9, 2026

    @GaryAllan
    Collaborator

    Hi,
    Upgrading to latest release should work.

    Please post upgrade error messages.

  3. matthewhinchliffe1975 commented on Sep 9, 2026

    @matthewhinchliffe1975
    Author

    Hi,

    Thanks for the reply, as I'm not sure what Git Branch we are on, I tried manually downloading the phpipam-v1.8.2.tgz
    When I extracted and ran the upgrade I got the following error message

    Image

    And in the browser I see this

    Image

    The documentation we have is pretty old, so I'm trying to recreate it.

    I took a snapshot of the VM prior to the work, so I have rolled back to that so am able to start afresh.

    Thanks

  4. GaryAllan commented on Sep 9, 2026

    @GaryAllan
    Collaborator

    Hello

    Your database schema and dbversion values are out-of-sync.

    Take a backup of files and database / VM snapshot etc....[make sure you can rollback]

    Run php functions/upgrade_queries.php 1.5.27 and manually apply the UPDATE SQL to the database in chunks ending in a database dbversion/version bump. If the column already exists it should be safe to ignore the error and move on.

    After a few sections with no errors you can re-try the automatic upgrade process.

    /* VERSION 1.5.28 */
    ALTER TABLE `subnets` ADD `isPool` BOOL NOT NULL DEFAULT '0';
    -- Database version bump
    UPDATE `settings` set `dbversion` = '28';
    
    /* VERSION 1.5.29 */
    ALTER TABLE `sections` ADD `showSubnet` BOOL NOT NULL DEFAULT '1';
    -- Database version bump
    UPDATE `settings` set `dbversion` = '29';
    
    /* VERSION 1.5.30 */
    -- Add Italian translation
    INSERT INTO `lang` (`l_name`, `l_code`) VALUES ('Italian', 'it_IT.UTF-8');
    -- Database version bump
    UPDATE `settings` set `dbversion` = '30';
    

    ...

  5. matthewhinchliffe1975 commented on Sep 29, 2026

    @matthewhinchliffe1975
    Author

    Hi

    Thanks for your reply, I am really struggling with this upgrade.

    I did run the database upgrade in stages and managed to get it to the latest version and upgraded via the browser. However, when I attempted to use GIT PULL to get the latest version I got the following error

    Image

    I have had to roll back to the snapshot I took, so I am back to square one.

    If possible please could someone give me some step by step instructions as I feel I am missing something.

    Thanks again for your help

    Matthew

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions