Re: node.js application listening on port 8000 enabled with SSL certificate returns ERR_SSL_PROTOCOL_ERROR on browser.

[Frank Gingras <thumbs@xxxxxxxxxx>]

None of those entries point to your 404 error.

Make sure that you are reaching the proper vhost (with the scheme and hostname) by running apachectl -S.

There is just far too much noise in the backlog of this thread to make sense of it so far.

On Sun, Jun 25, 2023 at 11:46 AM Richard <lists-apache@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Date: Sunday, June 25, 2023 16:09:23 +0530
> From: Kaushal Shriyan <kaushalshriyan@xxxxxxxxx>
>
> I have modified the nodejsbackendssl.conf file located
> in /etc/httpd/conf.d/ to the below configuration.
>
> *#cat  /etc/httpd/conf.d/nodejsbackendssl.conf*
> <VirtualHost *:80>
>         ServerName nodejs.mydomain.com
>         ProxyPass / http://localhost:8000/
>         LogLevel debug
>         ErrorLog /var/log/httpd/nodejssslerror.log
>         CustomLog /var/log/httpd/nodejssslaccess.log combined
> </VirtualHost>
>
> Below are the logs in /var/log/httpd/nodejssslerror.log
>
> [Sun Jun 25 16:04:40.289171 2023] [proxy:debug] [pid 6223:tid 6223]
>> proxy_util.c(2155): AH00925: initializing worker
>> http://localhost:8000/ shared

If you are still getting errors (e.g., 404s) on the front-end please
provide the relevant lines from the front-end server's error_log. The
proxy's corresponding log entries may be of value, but without the
detail from the front-end it's hard to tell.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx