1
General / Re: Update Log
« Last post by earnolmartin on February 28, 2025, 10:52:21 am »Minor update released to fix the backup code in Ubuntu 22 and newer. Get it from the first post.
News:
EHCP Force Edition can be downloaded from GitHub
https://github.com/earnolmartin/EHCP-Force-Edition
Recent Posts
2
General / Re: Update Log
« Last post by earnolmartin on December 19, 2024, 01:13:45 pm »Update released which adds Ubuntu 24.04 support. 
3
General / Re: Update Log
« Last post by earnolmartin on August 30, 2024, 10:09:34 pm »Update released mainly to point to our new url of https://ehcpforce.ezpz.cc
4
Bugs / Re: Letsencrypt cert bug
« Last post by earnolmartin on August 06, 2024, 12:37:07 pm »I don't see any issues. Did you configure your subdomains in the EHCP panel? They have to be configured there. Otherwise, it will not work.
5
Bugs / Re: Letsencrypt cert bug
« Last post by spicer on July 26, 2024, 10:48:59 am »Here the newest letsencrypt logs
6
Bugs / Re: Letsencrypt cert bug
« Last post by spicer on July 25, 2024, 03:17:46 am »Hmm, the log is attached in the first post 
7
Bugs / Re: Subdomain removing bug
« Last post by andy on July 24, 2024, 12:16:00 pm »Thanks, this should be fixed in GitHub. Please update your classapp.php file using the following method:
https://ehcpforce.tk/download.php#ehcpforceclassappupdate-test
Is it fixed now? It appears to be from my testing...
I also added the same checks for if there are no domains or passive domains.
Awesome, thank you! I'll give it a shot soon.
The presence of that empty folder doesn't hurt anything, so I'll just leave it there for now.
Yes I know, it's just if you're adding and removing a lot of subdomains it can get quite messy in there.
8
General / Re: Update Log
« Last post by earnolmartin on July 24, 2024, 11:06:08 am »Update released. See information in first post.
If bind9 service won't start, edit named.options.conf:
sudo nano /etc/bind/named.conf.options
Remove:
additional-from-cache no;
line and restart the service:
sudo service bind9 restart
If bind9 service won't start, edit named.options.conf:
sudo nano /etc/bind/named.conf.options
Remove:
additional-from-cache no;
line and restart the service:
sudo service bind9 restart
9
Bugs / Re: Subdomain removing bug
« Last post by earnolmartin on June 20, 2024, 05:20:24 pm »Hello,
When you have only one subdomain left and remove it on the EHCP Force web panel, the following things aren't correctly processed:
- If you remove it manually, the webserver (in my case apache2) does not start anymore. This is because:
-> The content for the last remaining subdomain, which was deleted, doesn't get removed from the ehcp apache2 config file in /var/www/new/ehcp/apachehcp_subdomains.conf. This is not a problem, if you have several subdomains and you remove one, then the block gets removed correctly from this file.
Thanks, this should be fixed in GitHub. Please update your classapp.php file using the following method:
https://ehcpforce.tk/download.php#ehcpforceclassappupdate-test
Is it fixed now? It appears to be from my testing...
I also added the same checks for if there are no domains or passive domains.
- The folder /var/www/vhosts/.../domain.com/httpdocs/subdomains doesn't get removed. Also the subdomain folder within this path is still there.
The presence of that empty folder doesn't hurt anything, so I'll just leave it there for now.
10
Bugs / Subdomain removing bug
« Last post by andy on June 17, 2024, 03:30:06 am »Hello,
When you have only one subdomain left and remove it on the EHCP Force web panel, the following things aren't correctly processed:
- The folder /var/www/vhosts/.../domain.com/httpdocs/subdomains doesn't get removed. Also the subdomain folder within this path is still there.
- If you remove it manually, the webserver (in my case apache2) does not start anymore. This is because:
-> The content for the last remaining subdomain, which was deleted, doesn't get removed from the ehcp apache2 config file in /var/www/new/ehcp/apachehcp_subdomains.conf. This is not a problem, if you have several subdomains and you remove one, then the block gets removed correctly from this file.
When you have only one subdomain left and remove it on the EHCP Force web panel, the following things aren't correctly processed:
- The folder /var/www/vhosts/.../domain.com/httpdocs/subdomains doesn't get removed. Also the subdomain folder within this path is still there.
- If you remove it manually, the webserver (in my case apache2) does not start anymore. This is because:
-> The content for the last remaining subdomain, which was deleted, doesn't get removed from the ehcp apache2 config file in /var/www/new/ehcp/apachehcp_subdomains.conf. This is not a problem, if you have several subdomains and you remove one, then the block gets removed correctly from this file.