No access to GUI after beta script install

Beta Program Issues
1

I just run the new install script on a Debian 12. It worked, and everythings eems to be installed, but:

  • if I access port 80, i just get the default “Apache2 Debian Default Page”
  • there is nothing on port 443
mongod     748  mongodb   14u  IPv4  16933      0t0  TCP localhost:27017 (LISTEN)
redis-ser  754    redis    6u  IPv4  16893      0t0  TCP localhost:6379 (LISTEN)
apache2    778     root    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
sshd       792     root    3u  IPv4  16625      0t0  TCP *:22 (LISTEN)
sshd       792     root    4u  IPv6  16627      0t0  TCP *:22 (LISTEN)
apache2    831 asterisk    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
apache2    832 asterisk    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
apache2    834 asterisk    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
apache2    835 asterisk    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
apache2    836 asterisk    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
mariadbd   976    mysql   17u  IPv4  17321      0t0  TCP localhost:3306 (LISTEN)
master    1358     root   13u  IPv4  17919      0t0  TCP *:25 (LISTEN)
master    1358     root   14u  IPv6  17920      0t0  TCP *:25 (LISTEN)
apache2   3266 asterisk    3u  IPv4  15732      0t0  TCP *:80 (LISTEN)
asterisk  4246 asterisk   13u  IPv4  26560      0t0  TCP localhost:8088 (LISTEN)
asterisk  4246 asterisk   14u  IPv6  26561      0t0  TCP *:8089 (LISTEN)
asterisk  4246 asterisk   15u  IPv4  26562      0t0  TCP localhost:5038 (LISTEN)
asterisk  4246 asterisk   27u  IPv4  27671      0t0  TCP *:1720 (LISTEN)
node\x20/ 4503 asterisk   20u  IPv4  27968      0t0  TCP localhost:4573 (LISTEN)
node\x20/ 4618 asterisk   23u  IPv4  28177      0t0  TCP localhost:6001 (LISTEN)
node\x20/ 4618 asterisk   32u  IPv4  28178      0t0  TCP localhost:6006 (LISTEN)
node\x20/ 4618 asterisk   48u  IPv6  28289      0t0  TCP *:6082 (LISTEN)
node\x20/ 4618 asterisk   53u  IPv4  28294      0t0  TCP localhost:6081 (LISTEN)
node\x20/ 4618 asterisk   55u  IPv4  28296      0t0  TCP localhost:6086 (LISTEN)
node\x20/ 4618 asterisk   57u  IPv6  28300      0t0  TCP *:6083 (LISTEN)

How is one supposed to get started?

2

I saw this come across:

Could be your issue.

3

Thanks I’ll try that :slight_smile:

4

@QM2021 I had the same issue. There may be some issues with the install script. I tried 3 times to install it on fresh VMs and only on the 3rd attempt did everything go smoothly.

When the script finished, did you get the FreePBX splash screen?

5

The blog post was updated with new install commands. The former method was seen to be timing out in some cases. Start over with by dloading the script first.

6

I did - on reboot. But I think I’ll try again following @lgaetz suggestion.

7

As of this morning, same fresh VM with Deb12:

2024-03-20 07:28:42 - Starting installation.
2024-03-20 07:28:42 -   Starting FreePBX 17 installation process for vmlenz-fpbx3 Linux vmlenz-fpbx3 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
2024-03-20 07:28:42 -   Please refer to the /var/log/pbx/freepbx17-install-2024.03.20-07.28.42.log to know the process...
2024-03-20 07:28:42 -   Executing script v1.1 ...
2024-03-20 07:28:42 - Making sure installation is sane

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2024-03-20 07:28:42 - Setting up default configuration
2024-03-20 07:28:42 - ###############################
2024-03-20 07:28:42 - Installing software-properties-common ....
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package software-properties-common
2024-03-20 07:28:42 - Exiting script

The reason seems to be a missing apt-get update - so it could be an idea to have it run by the beginning of the script.