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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> Date: Thursday, June 22, 2023 00:13:34 +0530
> From: Kaushal Shriyan <kaushalshriyan@xxxxxxxxx>
> 
> 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-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx




[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux