Creating test environment from production; ispconfig ip change.

Discussion in 'General' started by michel!!, Oct 1, 2021.

  1. michel!!

    michel!! New Member

    Hi all,

    I am trying to create a testing environment, by copying our production vm's from vsphere to a seperate part of the network.
    I changed the ip addresses and the /etc/hosts file.
    But nothing is working so far.
    I am using the manual as a reference,but the sql setup is using a script so I have no idea what to change, besides adding the new root accounts with the changed ip's.
    Are there any other configs to edit, to get this clone working?
    The environment contains 1 managment , one web, and one sql server
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    The IP-address is in several places. Including the database at least in host account names if this is a multiserver setup. Also change the IP-address in ISPConfig GUI, server ip -addresses.
    grep -r /etc/
    with your old IP-number to find the setup files.
  3. michel!!

    michel!! New Member

    Thanks for your reply.
    I ran the command on all servers with all ip addresses, but it only revealed one file: /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg.
    Shouldn't there be more?
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    No, and this file is not from ISPConfig. In general, you can change the IP of an ISPConfig server without having to change anything within ISPConfig. So that your ISPConfig is not working must have other reasons.

Share This Page