Testing copying a master server (part of multiserver setup) to new hardware, and after finishing the copy, the apache web sites on this new master server give a 503 error in a browser. Steps: Setup new master server on debian using perfect server automated ISPConfig 3 process: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ Specific command run was: wget -O - https://get.ispconfig.org | sh -s -- --no-mail --no-roundcube --no-mailman --monit --unattended-upgrades Logged into existing master server (source) Downloaded ISPConfig Migration Toolkit, extracted ISPCopy Run ISPCopy: ./isp_copy After completion, can successfully access new master ISPConfig web control panel in browser Logged into target server, and run: ispconfig_update.sh --force, and selected to reconfigure services (as suggested in migration toolkit notes) Edited windows host file to point a website at new master IP address Loaded website in browser, get 503 error Error log: [Thu Nov 14 21:12:46.582840 2024] [proxy:error] [pid 247195:tid 247221] (111)Connection refused: AH02454: FCGI: attempt to connect to Unix domain socket /var/lib/php5-fpm/web2581.sock (localhost:8000) failed [Thu Nov 14 21:12:46.582865 2024] [proxy_fcgi:error] [pid 247195:tid 247221] [remote x.x.x.x:53604] AH01079: failed to make connection to backend: localhost Using ISPConfig control panel on new master server, de-activate website (uncheck active box), save Activate website, save Wait a minute, website now works in a browser (with windows host file still pointing at new master IP) Does this mean that every website that is copied with ISPCopy needs to be de-activated and then activated again, in order to fix this? Or have I missed a step? Once this is sorted, I would like to run ISPCopy on a slave server, that hosts 100+ websites, to copy to new hardware, as well as a slave mail server. Thanks
