[SOLVED] Logon hangs after installation

I installed on a hosted system, and I don't know how many virtual machines would be run on the same physical machine, so no real way to know how busy the system is. However I'm perfectly happy to clear down and try another install.... and I can leave the widget spinning overnight.

I did wonder whether the PHP version makes any difference. I know I can change the PHP version, but that appears to be global and might affect other products on the platform. It would be bad juju to break our core applications while testing a potential solution. That's why &deity made VMs.

I deleted the previous instance of ProjeQtor, and reinstalled effectively from clean. The logon screen came up when I went to the projeqtor/view/main.php page, and I entered user and password. Over an hour later, the widget is still spinning.

The hosting does have a resource measurement tool, which only shows that there's no significant consumption right now and hasn't been for the last 90 minutes. The server isn't reporting anything strange, and nothing that would be a blip even from the installation (which was very quick). The last bump on the resource graphs was four hours ago, and I wasn't doing anything with this app at that time.

Meanwhile other apps running on our instance are very fast, so I think we're not resource constrained.

Babynus, I agree with you that dedicated hosting would offer better performance, but I don't believe we've got to performance yet. My conclusion is that installation of ProjeQtor is waiting on an event that might never happen. I just don't know what that is.

Hi, and thanks for the suggestions.

babynus wrote: Possibly there was an issue.
Yes, I have to agree with you there.

1) Check log file, as defined during installation (default location is projeqtor/files/logs)
Empty, apart from index.php

2) Possibly issue is inccorrect access rights to log file (cannot write in folder), so you should find an error loggued in Apache log file
The folder permissions are set to 777, which should allow anything to happen in the folder

3) Check browser console for errors
Which would be the 403 errors that you've seen. Again, all the folders are either 0755 or 0777 and the code is universally 0644.
.