There is no relevant error there, only a warning because you are using a
self-signed server certificate.

Can you describe *fully* which error you are having that is causing you
problems?

If you refer to an error of your browser complaining about your
certificate, then this is normal when using self-signed certs unless you
add them manually to your client browser.

2017-05-04 14:39 GMT+02:00 Keerthi Narayan <mkeerth...@gmail.com>:

> below is the details of error log file
>
> [Thu May 04 07:35:01.892795 2017] [ssl:warn] [pid 15336:tid
> 140037655033728] AH01906: 172.19.18.238:443:0 server certificate is a CA
> certificate (BasicConstraints: CA == TRUE !?)
> [Thu May 04 07:35:01.892876 2017] [mpm_event:notice] [pid 15336:tid
> 140037655033728] AH00489: Apache/2.4.18 (Ubuntu) mod_jk/1.2.41
> OpenSSL/1.0.2g configured -- resuming normal operations
> [Thu May 04 07:35:01.892881 2017] [core:notice] [pid 15336:tid
> 140037655033728] AH00094: Command line: '/usr/sbin/apache2'
> [Thu May 04 12:54:40.038040 2017] [mpm_event:notice] [pid 15336:tid
> 140037655033728] AH00491: caught SIGTERM, shutting down
> [Thu May 04 12:54:40.780686 2017] [ssl:warn] [pid 18991:tid
> 140346453059456] AH01906: 172.19.18.238:443:0 server certificate is a CA
> certificate (BasicConstraints: CA == TRUE !?)
> [Thu May 04 12:54:40.787424 2017] [ssl:warn] [pid 18992:tid
> 140346453059456] AH01906: 172.19.18.238:443:0 server certificate is a CA
> certificate (BasicConstraints: CA == TRUE !?)
> [Thu May 04 12:54:40.788009 2017] [mpm_event:notice] [pid 18992:tid
> 140346453059456] AH00489: Apache/2.4.18 (Ubuntu) mod_jk/1.2.41
> OpenSSL/1.0.2g configured -- resuming normal operations
> [Thu May 04 12:54:40.788023 2017] [core:notice] [pid 18992:tid
> 140346453059456] AH00094: Command line: '/usr/sbin/apache2'
>
>
>
> On Thu, May 4, 2017 at 2:33 PM, Daniel <dferra...@gmail.com> wrote:
>
>> At first sight there is no syntax error. Can you try to describe what
>> error you get and paste related error.log entries?
>>
>> 2017-05-04 9:30 GMT+02:00 Keerthi Narayan <mkeerth...@gmail.com>:
>>
>>> Hi All,
>>>
>>> I am trying to implement HTTPS to my local server(apache2) and below is
>>> configuration file.   -----UBUNTU SERVER
>>>
>>> <IfModule mod_ssl.c>
>>>         <VirtualHost _default_:443>
>>>                 ServerAdmin user@localhost
>>>                 ServerName x.x.x.x
>>>                 ServerAlias www.x.x.x.x
>>>                 DocumentRoot /var/www/html
>>>                 ErrorLog ${APACHE_LOG_DIR}/error.log
>>>                 CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>                 SSLEngine on
>>>                 SSLCertificateFile    /etc/apache2/ssl/apache.crt
>>>                 SSLCertificateKeyFile /etc/apache2/ssl/apache.key
>>>   <FilesMatch "\.(cgi|shtml|phtml|php)$">
>>>                                 SSLOptions +StdEnvVars
>>>                 </FilesMatch>
>>>                 <Directory /usr/lib/cgi-bin>
>>>                                 SSLOptions +StdEnvVars
>>>                 </Directory>
>>>                 <Directory /var/www/html>
>>>                         Options Indexes FollowSymLinks MultiViews
>>>                         AllowOverride None
>>>                         Order allow,deny
>>>                         allow from all
>>>                 </Directory>
>>>                  BrowserMatch "MSIE [2-6]" \
>>>                                 nokeepalive ssl-unclean-shutdown \
>>>                                 downgrade-1.0 force-response-1.0
>>>                 BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
>>>         </VirtualHost>
>>> </IfModule>
>>>
>>> Please advice me what else i have to configure apart from above
>>> configuration or correction.  So that it will get secured.
>>>
>>> Thanks & Regards,
>>> Keerthi Narayan
>>>
>>>
>>
>>
>> --
>> *Daniel Ferradal*
>> IT Specialist
>>
>> email         dferradal at gmail.com
>> linkedin     es.linkedin.com/in/danielferradal
>>
>
>


-- 
*Daniel Ferradal*
IT Specialist

email         dferradal at gmail.com
linkedin     es.linkedin.com/in/danielferradal

Reply via email to