Apache wont start after playing around

abintipl · Oct 11, 2024

Yes, I have checked and compared line by line with another server's 000-apps.vhost(another server working fine), both are the same
Thanks & regards!

remkoh · Oct 12, 2024

I'm at a loss.
Are you actively using apps.vhost on this server?
If not, remove the symbolic link in /etc/apache2/sites-enabled and restart Apache.
If there are no other errors in your config Apache should be running and serving your other websites again.
At least for the time being, until the solution is found.

till · Oct 12, 2024

The apps vhost is likely fine, its just the first one that uses SSL and that#s why it showed up. If he removes it (what he can do of course), he will likely get the exact same error with the next vhost that uses SSL.

The error:
Code:
Invalid command 'SSLEngine', perhaps misspelled or defined by a module not included in the server configuration
Means that SSL is not available in Apache. I'm aware that a2enmod says it's enabled, but apparently, it's not.

remkoh · Oct 12, 2024

till said: ↑

...
Means that SSL is not available in Apache. I'm aware that a2enmod says it's enabled, but apparently, it's not.
Click to expand...

My thoughts exactly. But clueless on how somebody could have accomplished that.
I would have expected some other error before apps.vhost is loaded and returning the current error.
Nothing else related in syslog??

abintipl · Oct 12, 2024

Hi,
Thank you for the reply
I again checked file /etc/apache2/sites-available/apps.vhost & compared with another working server apps.vhost, both are idential!

Even, I replaced the apps.vhost file with working server apps.vhost but no luck.

Thanks

till · Oct 12, 2024

You do not have an issue with the apps.vhost, see my post above.

abintipl · Oct 12, 2024

Sir,
I have removed apps.vhost from /etc/apache2/sites-enabled as well as from /etc/apache2/sites-available.
Then restarted apache with no errors
Now I can see Apache Default page while logging (with http://) to ISPconfig Panel or any of the website hosted on this server

Apache2 Ubuntu Default Page

Further, I ran ispconfig_update.sh --force any updated services & created new ssl but can not access
Then again removed apps.vhost from sites-available as well as sites-enabled restarted apache2
Then can see again Apache Default page
But not able to go further.
Thanks

till · Oct 12, 2024

abintipl said: ↑

Sir,
I have removed apps.vhost from /etc/apache2/sites-enabled as well as from /etc/apache2/sites-available.
Then restarted apache with no errors
Now I can see Apache Default page while logging (with http://) to ISPconfig Panel or any of the website hosted on this server

Apache2 Ubuntu Default Page
It works!

But not able to go further.
Thanks
Click to expand...

This shows what I told you: you do not have an issue with the apps.vhost and removing the apps vhost does not solve your issue. So the next step is to undo the apps vhost removal. Then, you should start to check why Apache is not loading its SSL module.

till · Oct 12, 2024

Here some trouble shooting steps from ChatGPT:

The error message you're encountering suggests that the `SSLEngine` directive is not recognized, which usually happens when the SSL module (`mod_ssl`) is not loaded, despite it being enabled using `a2enmod`. Here’s how you can troubleshoot and resolve the issue:

### 1. **Check if `mod_ssl` is correctly loaded:**

Even though you've enabled the SSL module using `a2enmod ssl`, it’s possible that Apache hasn't loaded the module properly. To verify:

- Open your Apache configuration file:
- For Debian-based systems, this is usually `/etc/apache2/apache2.conf`.

- Ensure that the following line exists in the configuration (this is what `a2enmod ssl` does):

```apache
LoadModule ssl_module modules/mod_ssl.so
```

If it's not present, you can manually add it and restart Apache.

### 2. **Check for `ssl.conf` or `mods-enabled/ssl.load`:**

After enabling the SSL module with `a2enmod`, it should create symlinks in `/etc/apache2/mods-enabled/` for the `ssl.load` and `ssl.conf` files.

- Check if these symlinks exist:

```bash
ls -l /etc/apache2/mods-enabled/ | grep ssl
```

- You should see two files: `ssl.load` and `ssl.conf`. If these are missing, manually create the symlinks to the files in `/etc/apache2/mods-available/`.

```bash
ln -s /etc/apache2/mods-available/ssl.load /etc/apache2/mods-enabled/
ln -s /etc/apache2/mods-available/ssl.conf /etc/apache2/mods-enabled/
```

### 3. **Check the Apache version:**

Ensure that your Apache installation actually supports SSL. Older versions of Apache might not have SSL support compiled in. You can check the Apache version with:

```bash
apache2 -v
```

SSL support is available in Apache 2.2 and later, but it’s worth ensuring you're using a version that supports it.

### 4. **Ensure OpenSSL is installed:**

Apache requires OpenSSL for SSL functionality. Make sure OpenSSL is installed on your system:

```bash
apt install openssl
```

You can also check the version with:

```bash
openssl version
```

### 5. **Restart Apache:**

Once you've checked and ensured all the above steps are correct, restart Apache to apply the changes:

```bash
systemctl restart apache2
```

### 6. **Check for Configuration Issues:**

Run the following command to check the Apache configuration for syntax errors, including any issues related to SSL:

```bash
apache2ctl configtest
```

This should report `Syntax OK` if the configuration is correct. If it shows any errors, fix them before proceeding.

### 7. **Check Apache Logs:**

If the issue persists, you can check the Apache error log for more information. The log file is typically located at `/var/log/apache2/error.log`.

```bash
tail -f /var/log/apache2/error.log
```

Look for any relevant error messages related to SSL or module loading.

---

By following these steps, you should be able to identify and resolve the issue with the `SSLEngine` directive and the SSL module in Apache on your Debian system.
Click to expand...

remkoh · Oct 13, 2024

I was under the impression more HTTPS sites existed on the server.
But apparenly not since now there's only talk about de default site working after removing apps.vhost.
I would just reinstall Apache and maybe Openssl packages over the existing ones then and after that run ispconfig_update.sh --force again.
That should fix any corrupted or missing files.

Log in or Sign up

Apache wont start after playing around

abintipl Member HowtoForge Supporter

remkoh Active Member HowtoForge Supporter

till Super Moderator Staff Member ISPConfig Developer

remkoh Active Member HowtoForge Supporter

abintipl Member HowtoForge Supporter

till Super Moderator Staff Member ISPConfig Developer

abintipl Member HowtoForge Supporter

till Super Moderator Staff Member ISPConfig Developer

till Super Moderator Staff Member ISPConfig Developer

remkoh Active Member HowtoForge Supporter

Share This Page

Log in or Sign up

Apache wont start after playing around

abintipl Member HowtoForge Supporter

remkoh Active Member HowtoForge Supporter

till Super Moderator Staff Member ISPConfig Developer

remkoh Active Member HowtoForge Supporter

abintipl Member HowtoForge Supporter

till Super Moderator Staff Member ISPConfig Developer

abintipl Member HowtoForge Supporter

till Super Moderator Staff Member ISPConfig Developer

till Super Moderator Staff Member ISPConfig Developer

remkoh Active Member HowtoForge Supporter

Share This Page

Useful Searches