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
wrote:
>
>
> Date: Sunday, June 25, 2023 16:09:23 +0530
> From: Kaushal Shriyan
>
> I have modified the nodejsbackendssl.conf file located
> in /etc/httpd/conf.d/ to the below configuration.
>
> *#cat /etc/httpd/conf.d/nodejsbackendssl.conf*
>
> ServerName nodejs.mydomain.com
> ProxyP
Hi Frank,
I have modified the nodejsbackendssl.conf file located
in /etc/httpd/conf.d/ to the below configuration.
*#cat /etc/httpd/conf.d/nodejsbackendssl.conf*
ServerName nodejs.mydomain.com
ProxyPass / http://localhost:8000/
LogLevel debug
ErrorLog /var/log/ht
Why did you define a vhost without a ServerName directive?
Also, those access log entries are quite useless, other than the requested
path. Increase the log level, and find the error log entries instead.
On Sun, Jun 25, 2023 at 2:54 AM Kaushal Shriyan
wrote:
>
>
> On Sun, Jun 25, 2023 at 10:40
