A week ago I enabled Let's Encrypt and ran the following commands without problems:
Now I wanted to change the certificate paths in directadmin.conf to a letsencrypt certificate, and after doing so and running again the rewrite_confs command, apache won't restart.
The problem is that in the httpd.conf template, it says 'Listen |PORT_80|', which also turned up in the real config file (/etc/httpd/conf/httpd.conf), so it was not rewritten to 80 or something like that.
But I'm running a reverse proxy with nginx listening on port 80. Shouldn't it be |PORT_8080| in the httpd.conf template? Can I just edit the template, or should i run some command to indicate that i'm using a reverse proxy? Why is this happening now, has it something to do with new certificate paths in directadmin.conf?
Btw, i changed back the certificate path and manually changed /etc/httpd/conf/httpd.conf to Listen 8080 instead of Listen |PORT_80|, and restarted httpd which went fine.
Thanks!
Code:
cd /usr/local/directadmin/custombuild
./build update
./build rewrite_confs
Now I wanted to change the certificate paths in directadmin.conf to a letsencrypt certificate, and after doing so and running again the rewrite_confs command, apache won't restart.
The problem is that in the httpd.conf template, it says 'Listen |PORT_80|', which also turned up in the real config file (/etc/httpd/conf/httpd.conf), so it was not rewritten to 80 or something like that.
But I'm running a reverse proxy with nginx listening on port 80. Shouldn't it be |PORT_8080| in the httpd.conf template? Can I just edit the template, or should i run some command to indicate that i'm using a reverse proxy? Why is this happening now, has it something to do with new certificate paths in directadmin.conf?
Btw, i changed back the certificate path and manually changed /etc/httpd/conf/httpd.conf to Listen 8080 instead of Listen |PORT_80|, and restarted httpd which went fine.
Thanks!