Troubleshooting Tip: FortiClient EMS v7.4.3 GUI being inaccessible after migrating from EMS v7.2.x

[btan]

Description	This article describes how to troubleshoot FortiClient EMS v7.4.3 GUI being inaccessible after migrating from FortiClient EMS v7.2.x.
Scope	FortiClient EMS v7.4.3.
Solution	After completing the steps in Migration Documentation, the migration tool shows 'EMS Migration Successfully completed'. When trying to access the EMS v7.4.3 GUI via the browser, it shows 'This site can't be reached'. The steps to troubleshoot this are: In the Linux server, run the command:  systemctl --all --type=service | grep -E 'fcems|apache|redis|postgres' apache2.service is active and running. ecsocksrv.service is looping in auto-restart state. The rest of the services are active and running (except for postgresql.service will be in 'exited' state, which is normal). Run the command:  emscli config get console allowed.hosts emscli config get console remote.access The result shows: emscli config get console allowed.hosts allowed.hosts => * emscli config get console remote.access remote.access => disabled This indicates that the Remote HTTPS access is disabled after EMS migration, which is the root cause of the issue. To resolve this, run command: sudo -i /opt/forticlientems/bin/emscli config set console --enable.remote.access Afterwards, verify by command:  /opt/forticlientems/bin/emscli config get console remote.access -> It should show remote.access => enabled. Now, access EMS GUI in the browser, it should be accessible.