Acces leads to 403 on several resources : it means "forbiden access".
So your configuration of Apache to directories does not seem to allow access to whole directory.

You should have logs in directory you defined during configuration (defaut is projeqtor/files/logs)

Now, we're not responsible for Softaculous package, and we don't recommand to use it.
We don't know what is packaged and how it's done.
It could have malwares included (I hope it doesn't) or any other bullshit.
Only reliable source is from our repository, on Sourceforge.
I'm afraid we can't give further support.

Hi. Ah... clearly you feel strongly about Softaculous. My experience in the past, with other packages, is that Softaculous is more likely to work than a manual install because they've solved most of the problems. But it's not impossible for them to get it wrong. I'm not aware of any of the packages that we've installed via Softaculous (under Cpanel) carrying malware - that WOULD be bad.

So I know, where are you seeing the 403 reports?

Thanks, John

I'm not aware of any of the packages that we've installed via Softaculous (under Cpanel) carrying malware

I don't thing it does. Softaculous is well known and they should not play with it. But I won't guaranty it does not 😉

So I know, where are you seeing the 403 reports?

In the browser console.

Hi,

I am using XAMPP 5.6.32 and Projeqtor 6.5.7. I downloaded this a few days ago and here is what i discovered, and i hope it helps you. Please note that I am a newbie to this, I am no expert but what you described is exactly what I had.

So, you come up to the login screen and it says database updating, only admin can login. You need to login as admin but you then need to wait about 15min (in my case, running this off a laptop). Don't close while that 'rotating thingy' is onscreen. You should notice that your drive activity light goes crazy once you login as admin. In my case, after 10-15min, it tells you that the database has been upgraded and you can log in.

I hope this helps,

Hi,

Thanks for sharing.
I can add that if you had to wait 10-15 minutes, your PC is very slow; of your PHP misconfigured (try and disable xDebug for instance).
On my laptop, full migration is 15-30 seconds, and on my servers, about 10 seconds.

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. 🙂

Hi,

Shared hosting platforms often offfer poor performance.
So for single user, it may be enought, but if you plan to use ProjeQtOr as a collaborative platform, dedicated hosting (or cortrectgly sized one) would offer better user experiment.

PHP version may be important.
PHP 7.0 brought much better performance thant PHP 5.6 and previous versions.
Pay attention that PHP 7.1 brough regressions to many applications (including famous framework SYMPHONY).
So all had to migrate to support PHP 7.1 (ProjeQtOr did and is compatible since V6.5)
Also PHP 7.2 brought regressions, but less important (ProjeQtOr is compatible since V7.0)

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.

Possibly there was an issue.

1) Check log file, as defined during installation (default location is projeqtor/files/logs)

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

3) Check browser console for errors.

Hi, and thanks for the suggestions.

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.
.

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

I think some errors are logged on Apache Error log file.
Please report these errors.

Hi, Babynus. I've solved the problem, by combining two things that weren't working separately. Leading from your comments about the error potential for the Softaculous installation script, I attempted to install ProjeQtOr directly. That didn't work because I couldn't get the database instance to work with the manual ProjeQtOr build. The installation menu appeared to work, but the DB wouldn't permit logon.

BUT. Since the Softaculous script automatically creates a unique DB, and sets up a lot of other useful functions (like regular backup, and ability to reset the master password for the app), I did the Softaculous install for ProjeQtOr, then moved all the manually installed ProjeQtOr files in place of the Softaculous-created directory, still using the parameters.php from the Softaculous install.

And that worked. At first logon, ProjeQtOr updated itself to 7.0.1 and logon was fine. I'd like to be more literate in a LAMP environment, and the correct answer would be for me to understand DB permissioning a bit better. But while the approach I took was very brute-force, it was effective and we're now experimenting with ProjeQtOr.

Merci beaucoup!