Question

Apache2 / Let's Encrypt / Debian 11 / VitalPBX 4

Posted on September 22, 2023
Let's Encrypt Debian 11 DigitalOcean Droplets Apache
Asked by f8e7c18b8ff949bcb1002d76b9e565

I created a droplet with Debian 11 and installed VitalPBX 4. I’m using a subdomain and I want it to be secure, so I created an SSL certificate using Let’s Encrypt with Apache2. The SSL certificate worked when I used the browser. The problem is, I’m stuck with the default Apache page saying “Success! The your_domain virtual host is working!” and doesn’t redirect to VitalPBX login page. What am I doing wrong? Please help!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

KFSys

Site Moderator

• September 25, 2023

Heya,

When you see the default Apache page, it usually means that the DocumentRoot for the Apache VirtualHost is not correctly set or the configuration specific to VitalPBX is not properly implemented. Here are the steps to resolve this:

1. Identify the VitalPBX Web Root

Identify the correct web root directory for VitalPBX. This is the directory where the VitalPBX web files are located. Often, it might be in a directory like /var/www/vitalpbx, but it can vary based on how VitalPBX was installed.

2. Edit Apache VirtualHost Configuration

Edit the Apache VirtualHost configuration file for your subdomain to set the proper DocumentRoot.

The VirtualHost configuration for your subdomain might be located in a file under /etc/apache2/sites-available. Look for a file named after your subdomain or a file named 000-default.conf if a specific one doesn’t exist.

sudo nano /etc/apache2/sites-available/your_subdomain.conf

Replace your_subdomain.conf with the actual file name corresponding to your subdomain.

3. Set Correct DocumentRoot

Find the DocumentRoot directive in the VirtualHost configuration file and set it to the VitalPBX web root directory identified in step 1.

<VirtualHost *:80>
    ServerName your_subdomain.example.com
    DocumentRoot /path/to/vitalpbx
    # ... other configurations ...
</VirtualHost>

<VirtualHost *:443>
    ServerName your_subdomain.example.com
    DocumentRoot /path/to/vitalpbx
    # ... other configurations, including SSL configurations ...
</VirtualHost>

Replace your_subdomain.example.com with your actual subdomain, and /path/to/vitalpbx with the actual path to the VitalPBX web root directory.

4. Restart Apache

After editing the configuration file, save the changes and exit the text editor. Then, restart Apache to apply the changes.

5. Check the URL

Finally, open a web browser and navigate to your subdomain to check if it now loads the VitalPBX login page instead of the default Apache page.

alexdo

Site Moderator

• September 24, 2023

Heya @f8e7c18b8ff949bcb1002d76b9e565

It seems like the SSL Certificate was installed successfully but the virtual host for the domain name is still pointing to a different root directory and not loading your actual application/site’s content.

Make sure you have configured Apache correctly to use your SSL certificate and to serve your VitalPBX application. Check the following configuration files:

/etc/apache2/sites-available/your_domain.conf: This file should contain the VirtualHost configuration for your subdomain. It should have the appropriate DocumentRoot and SSL settings.
/etc/apache2/sites-available/default-ssl.conf: Ensure that this configuration file points to your SSL certificate files correctly.

Hope that this helps!