-----Original Message-----
From: Richard <lists-apache@xxxxxxxxxxxxxxxxxxxxx>
To: users@xxxxxxxxxxxxxxxx
Sent: Wed, 28 Apr 2021 3:56
Subject: Re: Re: LAN to WAN access
> Date: Wednesday, April 28, 2021 00:59:37 +0000 > From: back Button <back.button@xxxxxxx.INVALID> > >> From: Richard >> Sent: Wed, 28 Apr 2021 1:43 >> >> >>> Date: Wednesday, April 28, 2021 00:25:29 +0000 >>> From: back Button <back.button@xxxxxxx.INVALID> >>> >>> After the fresh installation of 2.4.46 and It works! >>> When I ran apache for the first time I was getting >>> AH00558: httpd: Could not reliably determine the server's fully >>> qualified domain name, using 127.0.1.1. Set the 'ServerName' >>> directive globally to suppress this message Then I updated the >>> httpd.conf with >>> ServerName http://backbtn.ddns.net >>> Now the AH0058 message has gone, so I guess that has been >>> accepted. still when I put http://backbtn.ddns.net >>> I am getting >>> >>> 400 Bad Request >>> Invalid Header. >>> >> >> The "ServerName" is the FQDN (i.e., "backbtn.ddns.net") and does >> not include the protocol ("http://"). If the protocol is included >> in your message because of something your mail client is doing you >> need a mail client that doesn't "auto-html" things like that. >> >> You need to look in your apache server logs (specifically error) to >> get a better sense of what that error message may be being caused >> by. The user messages you are showing are of only marginal value. >> > > I removed the protocol http:// > > error logsﾠcat error_log > > [Wed Apr 28 01:03:47.100777 2021] [mpm_event:notice] [pid > 163591:tid 140110325255232] AH00489: Apache/2.4.46 (Unix) > configured -- resuming normal operations > ... > [Wed Apr 28 01:52:46.712904 2021] [core:notice] [pid > 164844:tid 139688522169408] AH00094: Command line: > '/usr/local/apache2/bin/httpd' > > cat access_log > 127.0.0.1 - - [28/Apr/2021:01:07:15 +0100] "GET / HTTP/1.1" 200 45 > ... > 127.0.0.1 - - [28/Apr/2021:01:19:16 +0100] "GET / HTTP/1.1" 304 - >
Those logs don't appear to be related/relevant to the "400" error you indicated you were getting. If/when you get an error, "tail" the log(s), replicate the error and then grab the relevant log bits.
