Worked for me as well. My symbolic link didn't work, so i just had to add the full path:
sh /usr/local/cwpsrv/htdocs/resources/scripts/generate_hostname_ssl
This solution didnt work for a long time, now I have again the same problem... :/
OK, I traced the issue and it was caused by Let's Encrypt. It changed the mechanism of testing the certificates. After i ran the
generate_hostname_ssl script, the CWP Admin Panel was working, but all my webpages, that were running Let's Encrypt SSL module had problem with their certificates - i couldn't access them. The
httpd daemon was down telling me, it has problem with SSL (the same as the
swpsrv before). I had to manually reinstall certificates for all websites, but after a while, the problem with hostname certificate showed up again - I couldn't access CWP Admin Module again. It seemd like infinite loop. I could only choose, if I want to access CWP Admin Panel or webpages.
What really solved my problem was to tell CWP not to use the hostname (.crt, .key) certificate, so the process
swpsrv could start normally.
I edited all files in this folder:
/usr/local/cwpsrv/confand i had to comment out everything with ssl, so, in my case:
ssl on;
ssl_session_timeout 90m;
ssl_certificate /etc/pki/tls/certs/hostname.crt;
ssl_certificate_key /etc/pki/tls/private/hostname.key;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
to
# ssl on;
# ssl_session_timeout 90m;
# ssl_certificate /etc/pki/tls/certs/hostname.crt;
# ssl_certificate_key /etc/pki/tls/private/hostname.key;
# ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
# ssl_ciphers HIGH:!aNULL:!MD5;
# ssl_prefer_server_ciphers on;
Now, my CWP works like a charm and I can also use the Let's Encrypt Certificates for webpages as usual. I am not able to use CWP Admin Panel with SSL, but I dont care 'cause I use VPN for accessing the CWP Admin Panel.
The problem ocures, when I create a new user, then the configuration file with enabled SSL is created, so the CWP Admin panel is down again. To make it work, i have to edit the new user configuration file and comment out the SSL so it can work again. Thank God, i don't create new users that often.
I am not sure about how proper this solution is, but it works for me great.