Adobe Connect User Community
Menu

#1 2018-12-24 05:17:21

exarch

HTTP 404 after restart a server

We have Adobe Connect server that was virtualized about two years ago (VMWare). The configuration of the virtual machine has not changed. However, the server has rebooted several times during these two years. There were no problems.

Last week we realized that we did not have enough CPU power. We turned off the virtual machine, cloned it, added the necessary number of vCPUs to the new virtual machine, launched both.

Old VM works without problems. On a new one, when trying to access any Adobe Connect page, we get a 404 error. The error appears when trying to connect from the outside or from the VM itself at http: // localhost. At the same time, the local administrator console is available (localhost: 8510 / console). We also tried to restore the original VM configuration, but this did not solve the problem.

Tell me, please, what could be the problems? What logs or settings we need to check,

Thank you in advance.

Offline

#2 2019-01-02 14:24:30

Jorma_at_CoSo

Re: HTTP 404 after restart a server

You have a lot of changes all at once, so it may be hard to nail down exactly where the issue lies.

I'd probably start by verifying that your DNS records point to the new server(s) or that your load balancer points to the new servers, if applicable.

After that, look at the firewall rules and verify the required ports are open on the new server(s).

Will the login page come up if you go directly to the IP of the new server?

Offline

Board footer