Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Richard 



> Date: Wednesday, June 21, 2023 20:14:40 +
> From: Richard
> 
> 
>> Date: Thursday, June 22, 2023 00:13:34 +0530
>> From: Kaushal Shriyan 
>> 
>> When i hit https://nodejs.mydomain.com/demo/index.html I see the
>> below in both httpd error and access logs
>> 
>># pwd
>> /var/log/httpd
>># cat error_log
>> [Thu Jun 22 00:06:34.161122 2023] [suexec:notice] [pid 16995:tid
>> 16995] AH01232: suEXEC mechanism enabled (wrapper:
>> /usr/sbin/suexec) [Thu Jun 22 00:06:34.196360 2023] [http2:warn]
>> [pid 16995:tid 16995] AH10034: The mpm module (prefork.c) is not
>> supported by mod_http2. The mpm determines how things are
>> processed in your server. HTTP/2 has more demands in this regard
>> and the currently selected mpm will just not do. This is an
>> advisory warning. Your server will continue to work, but the
>> HTTP/2 protocol will be inactive.
>> [Thu Jun 22 00:06:34.197101 2023] [lbmethod_heartbeat:notice] [pid
>> 16995:tid 16995] AH02282: No slotmem from mod_heartmonitor
>> [Thu Jun 22 00:06:34.243545 2023] [mpm_prefork:notice] [pid
>> 16995:tid 16995] AH00163: Apache/2.4.57 (IUS) OpenSSL/1.0.2k-fips
>> PHP/8.1.20 configured -- resuming normal operations
>> [Thu Jun 22 00:06:34.243596 2023] [core:notice] [pid 16995:tid
>> 16995] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
>> 
>> 
>># cat access_log
>> 172.16.16.45 - drupaladmin [22/Jun/2023:00:06:45 +0530] "GET
>> /demo/index.html HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh;
>> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/114.0.0.0 Safari/537.36"
>> 172.16.16.45 - drupaladmin [22/Jun/2023:00:06:45 +0530] "GET
>> /demo/index.html HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh;
>> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko)
>> Chrome/114.0.0.0 Safari/537.36"
> 
> Leaving aside other potential issues, the timestamps on your
> error_log entries are from:
> 
> Jun 22 00:06:34
> 
> while the ones with the 404 in your access_log are from:
> 
> 22/Jun/2023:00:06:45
> 
> ~10 minutes later. I.e., they do not appear to be for the same
> event. 
> 
> The error_log entries look like server startup error messages,
> rather than ones related to a browser request. Also, given the
> timestamp formats, I'm suspecting that they aren't even from the
> same apache server/machine instance.
> 
> Look at the entries in the error_log that are specific to the
> access_log 404 errors. That will give you more detail from that side
> of things. 
> 

correction ... 

 > ~10 minutes later. I.e., they do not appear to be for the
 > same event. 

should be:

 > ~10 seconds later ...

regardless, the error_log entries aren't for the access_log 404
requests/events.






-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Richard 



> Date: Thursday, June 22, 2023 00:13:34 +0530
> From: Kaushal Shriyan 
> 
> When i hit https://nodejs.mydomain.com/demo/index.html I see the
> below in both httpd error and access logs
> 
># pwd
> /var/log/httpd
># cat error_log
> [Thu Jun 22 00:06:34.161122 2023] [suexec:notice] [pid 16995:tid
> 16995] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
> [Thu Jun 22 00:06:34.196360 2023] [http2:warn] [pid 16995:tid 16995]
> AH10034: The mpm module (prefork.c) is not supported by mod_http2.
> The mpm determines how things are processed in your server. HTTP/2
> has more demands in this regard and the currently selected mpm will
> just not do. This is an advisory warning. Your server will continue
> to work, but the HTTP/2 protocol will be inactive.
> [Thu Jun 22 00:06:34.197101 2023] [lbmethod_heartbeat:notice] [pid
> 16995:tid 16995] AH02282: No slotmem from mod_heartmonitor
> [Thu Jun 22 00:06:34.243545 2023] [mpm_prefork:notice] [pid
> 16995:tid 16995] AH00163: Apache/2.4.57 (IUS) OpenSSL/1.0.2k-fips
> PHP/8.1.20 configured -- resuming normal operations
> [Thu Jun 22 00:06:34.243596 2023] [core:notice] [pid 16995:tid
> 16995] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
>
>
># cat access_log
> 172.16.16.45 - drupaladmin [22/Jun/2023:00:06:45 +0530] "GET
> /demo/index.html HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh;
> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/114.0.0.0 Safari/537.36"
> 172.16.16.45 - drupaladmin [22/Jun/2023:00:06:45 +0530] "GET
> /demo/index.html HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh;
> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/114.0.0.0 Safari/537.36"

Leaving aside other potential issues, the timestamps on your
error_log entries are from:

Jun 22 00:06:34

while the ones with the 404 in your access_log are from:

22/Jun/2023:00:06:45

~10 minutes later. I.e., they do not appear to be for the same event. 

The error_log entries look like server startup error messages, rather
than ones related to a browser request. Also, given the timestamp
formats, I'm suspecting that they aren't even from the same apache
server/machine instance.

Look at the entries in the error_log that are specific to the
access_log 404 errors. That will give you more detail from that side
of things. 





-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Kaushal Shriyan 
Hi Daniel,

Please refer to the below details

$ npm start

> api-console@6.6.32 start
> node demo/index.js

Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly:
https://github.com/browserslist/update-db#readme
es-dev-server started on http://localhost:8000
  Serving files from '/var/www/html/api-console'.
  Opening browser on '/demo/'
  Using history API fallback, redirecting route requests to
'/demo/index.html'
  Using auto compatibility mode, transforming code on older browsers based
on user agent.

*httpd.conf file configuration*
#cat /etc/httpd/conf.d/nodejsnodejsssl.conf

SSLEngine On
ServerName nodejs.mydomain.com
SSLCertificateFile /etc/letsencrypt/live/nodejs.mydomain.com/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/
nodejs.mydomain.com/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/
nodejs.mydomain.com/chain.pem

ProxyPass http://localhost:8000/



When i hit https://nodejs.mydomain.com/demo/index.html I see the below in
both httpd error and access logs

#pwd
/var/log/httpd
# cat error_log
[Thu Jun 22 00:06:34.161122 2023] [suexec:notice] [pid 16995:tid 16995]
AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Jun 22 00:06:34.196360 2023] [http2:warn] [pid 16995:tid 16995]
AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm
determines how things are processed in your server. HTTP/2 has more demands
in this regard and the currently selected mpm will just not do. This is an
advisory warning. Your server will continue to work, but the HTTP/2
protocol will be inactive.
[Thu Jun 22 00:06:34.197101 2023] [lbmethod_heartbeat:notice] [pid
16995:tid 16995] AH02282: No slotmem from mod_heartmonitor
[Thu Jun 22 00:06:34.243545 2023] [mpm_prefork:notice] [pid 16995:tid
16995] AH00163: Apache/2.4.57 (IUS) OpenSSL/1.0.2k-fips PHP/8.1.20
configured -- resuming normal operations
[Thu Jun 22 00:06:34.243596 2023] [core:notice] [pid 16995:tid 16995]
AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
#cat access_log
172.16.16.45 - drupaladmin [22/Jun/2023:00:06:45 +0530] "GET
/demo/index.html HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh; Intel Mac
OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0
Safari/537.36"
172.16.16.45 - drupaladmin [22/Jun/2023:00:06:45 +0530] "GET
/demo/index.html HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh; Intel Mac
OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0
Safari/537.36"

Please suggest further. Thanks in advance.



Best Regards,

Kaushal

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Daniel Gruno 

On 2023-06-21 18:57, Kaushal Shriyan wrote:

Hi,

I am running node.js application on port 8000 and Apache HTTP server on 
CentOS Linux release 7.9.2009 (Core)


# node --version
*v16.20.0*
# httpd -v
Server version: *Apache/2.4.57 (IUS)*
Server built:   Apr  7 2023 14:49:47
#

_httpd.conf file configuration_
#cat /etc/httpd/conf.d/nodejsnodejsssl.conf

     SSLEngine On
     SSLProxyEngine On
     ServerName nodejs.mydomain.com 
     SSLCertificateFile 
/etc/letsencrypt/live/nodejs.mydomain.com/cert.pem 

     SSLCertificateKeyFile 
/etc/letsencrypt/live/nodejs.mydomain.com/privkey.pem 

     SSLCertificateChainFile 
/etc/letsencrypt/live/nodejs.mydomain.com/chain.pem 


     
         ProxyPass http://localhost:8000/ 
     


When I am trying to access the URL 
https://nodejs.mydomain.com:8000/demo/index.html 
, I am encountering 
the below error on the browser.


This site can’t provide a secure connection
nodejs.mydomain.com  sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Please comment if the above httpd conf file is incorrect or If i am 
missing anything. Thanks in advance.


Best Regards,

Kaushal



There are inconsistencies in your configuration.
On one hand, you have "SSLProxyEngine On" which would imply that the 
backend node.js application is running over TLS.
On the other hand, you are proxying to HTTP://, not HTTPS://, which is 
what you would use for plain-text (not TLS) connections.


The options are mutually exclusive. Either you have TLS on node.js, and 
should proxy to https://localhost:8000 or you do not, and you shouldn't 
have "SSLProxyEngine On" defined.




-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Richard 



> Date: Wednesday, June 21, 2023 23:09:45 +0530
> From: Kaushal Shriyan 
>
> When I am trying to access the URL
> https://nodejs.mydomain.com/demo/index.html, I am seeing the below
> information in Apache HTTP server access logs.
> 
> 172.16.16.45 - drupaladmin [21/Jun/2023:23:04:07 +0530] "GET
> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0

You need to look in the error log for the details the 404/not_found
error that is being returned.



-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Darryl Baker 
I will be in meeting for the rest of the afternoon. Here is an anonymized 
version of my working configuration. Hope it helps.

The main URL is https://directory.uexample.com/search

nodejs is expacting /search


ServerName  directory.example.com
ServerAlias hostnameaa.mid.example.com
ServerAlias hostnameab.mid.example.com

SSLEngine   on

SSLCertificateFile  /etc/httpd/certs/cert.pem
SSLCertificateKeyFile   /etc/httpd/certs/cert.pem
SSLOptions  +StdEnvVars

RewriteEngine On
LogLevel alert rewrite:trace6

CustomLog logs/nodejs_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

ErrorLog/var/log/httpd/nodejs_error.log
CustomLog   /var/log/httpd/nodejs_access.log combined

DocumentRoot /var/www/iam-directory/dist

# RewriteRule ^/health-check-test.txt$ /public/health-check-test.txt
RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}

# When a request comes in, test to see if there's a matching static 
file in the "public" dir
RewriteCond %{DOCUMENT_ROOT}/public/%{REQUEST_URI} !-f

# If request does not include a static file, proxy it to the backend
RewriteRule ^(.*)$ http://localhost:8000$1 [P]

# Otherwise, add "public" to it (e.g., serve the file)
RewriteRule ^(.*)$ /public$1 [L]




Darryl Baker, GSEC, GCLD  (he/him/his)
Sr. System Administrator
Distributed Application Platform Services
Northwestern University
4th Floor
2020 Ridge Avenue
Evanston, IL  60208-0801
darryl.ba...@northwestern.edu
(847) 467-6674

From: Kaushal Shriyan 
Reply-To: Apache httpd Users 
Date: Wednesday, June 21, 2023 at 12:40 PM
To: Apache httpd Users 
Subject: Re: [users@httpd] node.js application listening on port 8000 enabled 
with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

On Wed, Jun 21, 2023 at 10:35 PM Darryl Baker 
mailto:darryl.ba...@northwestern.edu>> wrote:
Have you tried browsing to 
https://nodejs.mydomain.com/demo/index.html
 The proxy configuration in Apache will direct the connection to nodejs over 
port 8000.

Hi Darryl,

When I am trying to access the URL 
https://nodejs.mydomain.com/demo/index.html,
 I am seeing the below information in Apache HTTP server access logs.

172.16.16.45 - drupaladmin [21/Jun/2023:23:04:07 +0530] "GET /demo/index.html 
HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) 
AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/114.0.0.0
 Safari/537.36"
172.16.16.45 - drupaladmin [21/Jun/2023:23:04:18 +0530] "GET /demo/index.html 
HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) 
AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/114.0.0.0
 Safari/537.36"
172.16.16.45 - drupaladmin [21/Jun/2023:23:04:39 +0530] "GET /demo/index.html 
HTTP/1.1" 404 25644 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) 
AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/114.0.0.0
 Safari/537.36"

Please suggest further. Thanks in advance.

Best Regards,

Kaushal

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Eric Covener 
On Wed, Jun 21, 2023 at 1:45 PM Kaushal Shriyan
 wrote:
>
> Hi,
>
> When I hit http://nodejs.mydomain.com:8000/demo/index.html (without ssl) it 
> works with port number using the below httpd config file. Is there a way to 
> enable SSL connections?
>
> httpd.conf file configuration
> #cat /etc/httpd/conf.d/nodejsnodejsssl.conf
> 
> 
> ProxyPass http://localhost:8000/
> 
> 

You're not accessing Apache if you specify port 8000.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Kaushal Shriyan 
Hi,

When I hit http://nodejs.mydomain.com:8000/demo/index.html (without ssl) it
works with port number using the below httpd config file. Is there a way to
enable SSL connections?

*httpd.conf file configuration*
#cat /etc/httpd/conf.d/nodejsnodejsssl.conf


ProxyPass http://localhost:8000/



Please suggest further. Thanks in advance.


Best Regards,

Kaushal

On Wed, Jun 21, 2023 at 11:09 PM Kaushal Shriyan 
wrote:

> On Wed, Jun 21, 2023 at 10:35 PM Darryl Baker <
> darryl.ba...@northwestern.edu> wrote:
>
>> Have you tried browsing to https://nodejs.mydomain.com/demo/index.html
>> The proxy configuration in Apache will direct the connection to nodejs over
>> port 8000.
>>
>
> Hi Darryl,
>
> When I am trying to access the URL
> https://nodejs.mydomain.com/demo/index.html, I am seeing the below
> information in Apache HTTP server access logs.
>
> 172.16.16.45 - drupaladmin [21/Jun/2023:23:04:07 +0530] "GET
>> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0 (Macintosh;
>> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
>> 114.0.0.0 Safari/537.36"
>> 172.16.16.45 - drupaladmin [21/Jun/2023:23:04:18 +0530] "GET
>> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0 (Macintosh;
>> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
>> 114.0.0.0 Safari/537.36"
>> 172.16.16.45 - drupaladmin [21/Jun/2023:23:04:39 +0530] "GET
>> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0 (Macintosh;
>> Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
>> 114.0.0.0 Safari/537.36"
>
>
> Please suggest further. Thanks in advance.
>
>
>
> Best Regards,
>
>
>
> Kaushal
>
>>

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Kaushal Shriyan 
On Wed, Jun 21, 2023 at 10:35 PM Darryl Baker 
wrote:

> Have you tried browsing to https://nodejs.mydomain.com/demo/index.html
> The proxy configuration in Apache will direct the connection to nodejs over
> port 8000.
>

Hi Darryl,

When I am trying to access the URL
https://nodejs.mydomain.com/demo/index.html, I am seeing the below
information in Apache HTTP server access logs.

172.16.16.45 - drupaladmin [21/Jun/2023:23:04:07 +0530] "GET
> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0 (Macintosh; Intel
> Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0
> Safari/537.36"
> 172.16.16.45 - drupaladmin [21/Jun/2023:23:04:18 +0530] "GET
> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0 (Macintosh; Intel
> Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0
> Safari/537.36"
> 172.16.16.45 - drupaladmin [21/Jun/2023:23:04:39 +0530] "GET
> /demo/index.html HTTP/1.1" *404* 25644 "-" "Mozilla/5.0 (Macintosh; Intel
> Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0
> Safari/537.36"


Please suggest further. Thanks in advance.



Best Regards,



Kaushal

>

Re: [users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Darryl Baker 
Have you tried browsing to https://nodejs.mydomain.com/demo/index.html The 
proxy configuration in Apache will direct the connection to nodejs over port 
8000.

Darryl Baker, GSEC, GCLD  (he/him/his)
Sr. System Administrator
Distributed Application Platform Services
Northwestern University
4th Floor
2020 Ridge Avenue
Evanston, IL  60208-0801
darryl.ba...@northwestern.edu
(847) 467-6674

From: Kaushal Shriyan 
Reply-To: Apache httpd Users 
Date: Wednesday, June 21, 2023 at 11:58 AM
To: Apache httpd Users 
Subject: [users@httpd] node.js application listening on port 8000 enabled with 
SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

Hi,

I am running node.js application on port 8000 and Apache HTTP server on CentOS 
Linux release 7.9.2009 (Core)

# node --version
v16.20.0
# httpd -v
Server version: Apache/2.4.57 (IUS)
Server built:   Apr  7 2023 14:49:47
#

httpd.conf file configuration
#cat /etc/httpd/conf.d/nodejsnodejsssl.conf

SSLEngine On
SSLProxyEngine On
ServerName 
nodejs.mydomain.com
SSLCertificateFile 
/etc/letsencrypt/live/nodejs.mydomain.com/cert.pem
SSLCertificateKeyFile 
/etc/letsencrypt/live/nodejs.mydomain.com/privkey.pem
SSLCertificateChainFile 
/etc/letsencrypt/live/nodejs.mydomain.com/chain.pem

ProxyPass 
http://localhost:8000/



When I am trying to access the URL 
https://nodejs.mydomain.com:8000/demo/index.html,
 I am encountering the below error on the browser.

This site can’t provide a secure connection
nodejs.mydomain.com
 sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Please comment if the above httpd conf file is incorrect or If i am missing 
anything. Thanks in advance.

Best Regards,

Kaushal

[users@httpd] node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

2023-06-21 Thread Kaushal Shriyan 
Hi,

I am running node.js application on port 8000 and Apache HTTP server on
CentOS Linux release 7.9.2009 (Core)

# node --version
*v16.20.0*
# httpd -v
Server version: *Apache/2.4.57 (IUS)*
Server built:   Apr  7 2023 14:49:47
#

*httpd.conf file configuration*
#cat /etc/httpd/conf.d/nodejsnodejsssl.conf

SSLEngine On
SSLProxyEngine On
ServerName nodejs.mydomain.com
SSLCertificateFile /etc/letsencrypt/live/nodejs.mydomain.com/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/
nodejs.mydomain.com/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/
nodejs.mydomain.com/chain.pem

ProxyPass http://localhost:8000/



When I am trying to access the URL
https://nodejs.mydomain.com:8000/demo/index.html, I am encountering the
below error on the browser.

This site can’t provide a secure connection
nodejs.mydomain.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Please comment if the above httpd conf file is incorrect or If i am missing
anything. Thanks in advance.

Best Regards,

Kaushal