Yes, we have seen this previously, but never really had a solid step by step resolution. Some people talk about changing httpd configuration, but playing with that made no difference.
Nothing helpful in `journalctl -f’
This was a deployment we couldn’t upgrade from 13 - 14, so we deactivated, restored to 16 and then tried to activate the previous deployment.
Looked good, and via the GUI came back and said
Deployment XxXxXxXxX is currently assigned to this machine and is available for activation.
I then decided after restarting the machine, playing with httpd configuration (manually) to activate from fwconsole.
Below looked great, I thought I was set, but the GUI only goes to the Activation Pop up…
Any ideas or direction appreciated!
( I did change machine ID, updates and the other box below just in case )
fwconsole sysadmin activate XxXxXxXxX Attempting to activate against deployment 'XxXxXxXxX' Running /var/www/html/admin/modules/sysadmin/bin/activate_existing XxXxXxXxX Asking for deployment XxXxXxXxX...Success! Array ( [Hardware-Locked] => Yes [Produced-By] => Schmooze Communications [Product-Name] => PBXact [Registered-To] => XxXxXxXxX [branding] => FreePBXDistro [deploy_type] => OSS [deployment_id] => XxXxXxXxX [deploymentid] => XxXxXxXxX [distributor] => No [epm4ucp_exp] => 2043-02-07 [epm_exp] => 2043-02-07 [extroute_exp] => 2044-03-14 [global_lic_exp] => 2042-12-22 [license_version] => 2 [machineid] => c05fd30710bac728a831ab365a1411447213e92bb16c111b5b60971586e [updates] => eyJleHRyb3V0ZV9leHAiOiIxNTg0MjE1NjExIiwX2V4cCI6IjE1NDk1NzA2NTMifQ== [Expires] => 25-Dec-2030 [S3THzBzCK56d413px9vDakLsV1] => = [deployment_name] => XxXxXxXxX ) Setting permissions... Restarting httpd... Done