OK. First let me know which cPanel version you're using and on which CentOS or CloudLinux release.
It's WHM 60 with CloudLinux 6.8 and CentOS 6.8.
And yes, return all domains with vHost, ssl files, root directory, and so on.
Same issue here (on all steps mentioned), WHM 60.0 (build 36) EasyApache 3, Apache 2.2 PHP5.5, centos 6.8 openvz (no cloudlinux).
The vps time zone is Europe/Athens and the timezone conversion from America/New_York matches the correspoding log entries.
PS sorry for interrupting.
I have the same problem like other people.
Here is the output of: #tail /etc/nginx/utilities/error_log
[20-Feb-2017 22:16:32 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [20-Feb-2017 22:16:32 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89
I have also sent you an email with my httpd.conf file.
I have ea4 installed but still get the error in the initial post of this
thread: invalid number of arguments in "ssl_certificate" directive in
/etc/nginx/conf.d/default_https.conf:43
On Feb 20, 2017 11:58 PM, "iRakic" <
[email protected]> wrote:
BTW I have forgotten to mention, I have an issue with EA3.
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
#407 (comment)>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AURI1i6Mfk7caK1ItUPUt9OKTka4gy4Bks5rehqigaJpZM4MF-D->
Sorry about the delay in answer. Today i have updated to the latest version and now works, but all sites with HTTPS enabled are mismatch, the server puts the certificate from the hostname instead the true certificate of the website.
All websites have certificated issued, someones by let's encrypt and others by his own way.
afaik EA3 is not supported by engintron. you should be using EA4
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Today, i upgraded to new version 1.8.0 and got that error too
Now i must disable Engintron
How to fix that?
It says it's compatible with EA3. As you can see it here:
Engintron is also compatible with both EasyApache 3 and EasyApache 4 as of version 1.7.0.
Maybe it has stopped being compatible from version 1.8.0?
I just tried the newest version again. I have the same issue like before.
# tail -n 10 /etc/nginx/utilities/error_log [22-Feb-2017 16:28:42 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_get_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89 [22-Feb-2017 16:28:42 UTC] PHP Warning: file_put_contents(): Filename cannot be empty in /etc/nginx/utilities/https_vhosts.php on line 89
I must mention that I'm using Let's encrypt for the most of the sites. I have also users that have paid certificates as well.
A fix for this:
Uninstall, install 1.7.2:
https://github.com/engintron/engintron/releases/tag/v1.7.2
Then:
rm -f /etc/nginx/conf.d/default_https.conf
Wait for the cron job to recreate the https.conf automatically, and you should be set.
This PHP script seems to be broken in 1.8.0:
/etc/nginx/utilities/https_vhosts.php
1.7.2 uses a different PHP script for its cron, which seems to be working.
fully broken for me with WHM 62, centOS 6.8, EA4
I've got the same problem as @CarlosLopezES , the generator (/etc/nginx/utilities/https_vhosts.php) doesn't work correctly, and in turn the default_https.conf doesn't have any keys set for it thus nginx fails to start/restart, the error_log has the same contents as what @petrogazz posted.
I'll just keep it disabled until a solution is found.
@Paralda I have uninstalled 1.8.0 and installed 1.7.2 (remember to edit lines 528, 530 and 531 from engintron.sh).
Can we launch manually these cronjob to recreate?
Thank you,
Script command:
/usr/local/cpanel/bin/apache_conf_distiller --update
not working easyapache 4
So what replace for that?
@fevangelou no, I've had the AutoSSL certs on all domains before I reinstalled engintron, but yeah like you mentioned in the other issue I did make it search the entire vhost block instead of a specific place because it wasn't matching at all, the latest update does work though so thats great.
edit: actually no, it doesn't work. none of the vhosts are ported over, do I need to edit anything in it? it finds the httpd.conf just fine when I do an echo on it, but none of the domains are in the generated conf file, just the default https block
@fevangelou I think there's been some misunderstanding if I'm reading this regex correctly, it's searching for an <IfModule ssl_module>
block, inside every <VirtualHost example.com:443>
block, but that isn't how my certs are stored at all, I'll just go ahead and paste a sanitized example of a live domain for you to better understand it, but I think this is definitely something with how EA4 or Apache 2.4 generates the httpd.conf, maybe even how AutoSSL interacts with it, I'm not sure, but all I know is that when I debug the https_vhosts file with print_r's and echos, it returns 0 results even though it can read/parse the file.
<VirtualHost 1.2.3.4:8443>
ServerName example.com
ServerAlias mail.example.com www.example.com
DocumentRoot /home/user/public_html
SSLEngine on
SSLCertificateFile /var/cpanel/ssl/installed/certs/example_com.crt
SSLCertificateKeyFile /var/cpanel/ssl/installed/keys/example_com.key
SSLCACertificateFile /var/cpanel/ssl/installed/cabundles/cPanel_Inc__example.cabundle
</VirtualHost>
any idea why the ssl_module block isn't in there on any of them? I haven't changed anything.
edit1: apparently its due to cpanels apache templates (/var/cpanel/templates/apache2_4), gonna see if I can update those.
edit2: I've deleted vhost.local
and ssl_vhost.local
files, and now its using the default ones which work correctly, I don't understand how this happened and I've never edited or touched those files.
@Shadowized I did not think that we need the codeit-nginx repo because v1.8.1 Compiling nginx Official repositories with OpenSSL 1.1.0e, @fevangelou let's confirm about this with us.
Show precompiled Nginx modules...
nginx version: nginx/1.10.3
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC)
built with OpenSSL 1.1.0e 16 Feb 2017
TLS SNI support enabled
@Nirjonadda the official nginx repo uses the openssl version of the system from what I recall, and that is only 1.0.1e currently, where as the codeit one has a statically linked 1.1.0e, you can verify that yourself when you invoke nginx -V
, you'll see something like --with-openssl=
pretty sure engintron isn't compiling nginx currently, it just enables the nginx repo and installs it.