Apache2 wont start for ns1

[leon]

ns1.baillat.uk (192.168.0.150)
Debian Linux 12
Thursday, 25 September 2025 20:26
Linux 6.1.0-40-amd64 on x86_64
1 day, 3 hours, 39 minutes
382

Sorry if my info is skewed.

I have been having trouble with importing servers from Backblaze, since doing tar.gzip archives.

Then found out just to do the default archive.

I had errors since trying to upgrade my system to Debian 13, and then my server was useless.

I have now got a stable Linux installed and just got the pro version of Virtualmin installed.

Got my servers installed and now running a problem with apache2 as it just does not want to start nor can start the service.

Please help.

[ID10T]

Run this in the terminal and tell us what it reports.
systemctl start apache2

[leon]

× apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2025-09-25 22:58:38 BST; 27s ago
Docs: Apache HTTP Server Version 2.4 Documentation - Apache HTTP Server Version 2.4
Process: 661252 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
CPU: 22ms

Sep 25 22:58:38 ns1.baillat.uk systemd[1]: Starting apache2.service - The Apache HTTP Server…
Sep 25 22:58:38 ns1.baillat.uk apachectl[661255]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
Sep 25 22:58:38 ns1.baillat.uk apachectl[661255]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
Sep 25 22:58:38 ns1.baillat.uk apachectl[661255]: no listening sockets available, shutting down
Sep 25 22:58:38 ns1.baillat.uk apachectl[661255]: AH00015: Unable to open logs
Sep 25 22:58:38 ns1.baillat.uk apachectl[661252]: Action ‘start’ failed.
Sep 25 22:58:38 ns1.baillat.uk apachectl[661252]: The Apache error log may have more information.
Sep 25 22:58:38 ns1.baillat.uk systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Sep 25 22:58:38 ns1.baillat.uk systemd[1]: apache2.service: Failed with result ‘exit-code’.

[ID10T]

Do you have another web server or possibly a docker container running?
netstat -ap |grep 443

[leon]

no just the main server.

[Steini]

Run sudo lsof -nP -iTCP:443 -sTCP:LISTEN and check if another process/server is listening on port 443.

If you see another server, stop it.

Or Apache itself is trying to bind 443 twice…

[Ilia]

@leon

Sep 25 22:58:38 ns1.baillat.uk apachectl[661255]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443

Ah, alright. Sadly this is a known issue.

Do the following:

1. Type the following in the Virtualmin search bar and press enter:

   !edit /etc/apache2/ports.conf
   

2. Make sure that the file contents is as follows:

   # If you just change the port or add more ports here, you will likely also
   # have to change the VirtualHost statement in
   # /etc/apache2/sites-enabled/000-default.conf
   
   Listen 80
   
   <IfModule ssl_module>
   	Listen 443
   </IfModule>
   
   <IfModule mod_gnutls.c>
   	Listen 443
   </IfModule>
   
   

   • Save the file and close the panel

3. Then try restarting Apache from Terminal module again.

[leon]

tried that @Steini no other 443

[leon]

@Ilia

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf

Listen 80

<IfModule ssl_module>
	Listen 443
</IfModule>

<IfModule mod_gnutls.c>
	Listen 443
</IfModule>

that fixed the issue thanks for your help/

[Ilia]

@leon

that fixed the issue thanks for your help/

Great!

Can you please tell me more about your cloud provider and how you installed Virtualmin? Is this a clean install?