Decompressing of Navigate-CMS takes forever [Arch & Ubuntu]

[sxiii]

Hi developers :)

I've tried to install the N-CMS and it stucked in unpacking files even after I've given the directory with 777 to it:

I don't have a clue why this is the case.

[s@s-pc work]$ uname -a
Linux s-pc 5.3.11-1-MANJARO #1 SMP PREEMPT Wed Nov 13 12:21:14 UTC 2019 x86_64 GNU/Linux
[s@s-pc work]$ lsb_release -a
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	18.1.3
Codename:	Juhraya
[s@s-pc work]$ php -v
PHP 7.3.11 (cli) (built: Oct 23 2019 16:31:28) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.11, Copyright (c) 1998-2018 Zend Technologies
[s@s-pc work]$ apachectl -v
Server version: Apache/2.4.41 (Unix)
Server built:   Aug 13 2019 22:44:41

[sxiii]

Absolutely same problem on Ubuntu:

s3@s3-phenom:~$ uname -a
Linux s3-phenom 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
s3@s3-phenom:~$ lsb_release -a
Distributor ID:	Ubuntu
Description:	Ubuntu 19.10
Release:	19.10
Codename:	eoan
s3@s3-phenom:~$ php -v
PHP 7.3.11-0ubuntu0.19.10.1 (cli) (built: Oct 24 2019 11:38:49) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.11, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.11-0ubuntu0.19.10.1, Copyright (c) 1999-2018, by Zend Technologies
s3@s3-phenom:~$ apachectl -v
Server version: Apache/2.4.41 (Ubuntu)
Server built:   2019-08-14T14:36:32

[NavigateCMS]

Hi Dennis,

sorry for the delay in our response.
We have tested the Navigate CMS setup on a fresh Ubuntu installation and you are right that by default our installer gets stuck in the decompression state. The issue we could find is that the home folder (/var/www/html) must have enough permissions to create a folder. But you say that you already tried that, so you should check the Apache/PHP error logs to know what is the exact error or warning message that causes the installation to fail.

In our roadmap we already have a task creating a log during the setup process, so we and the admin user can see in which step the process failed, but meanwhile you will have to check the system logs.
Alternatively you can hit F12 in your browser (Firefox or Chrome) and check the last response of the setup.php ajax call in the Network tab. Maybe the error is also shown there.

If you find what it is please tell us. Thank you.