Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yes I see what I've done or haven't done. So much to ingest at this stage.
I'll go check it all and unravel what I've raveled :-) and look at that link then check back after I've done it in a day or two.
I appreciate your help and time. Thank you
sudo apachectl configtest
[Mon Nov 28 19:18:21.367063 2022] [core:error] [pid 16882:tid 139759424044096] (EAI 2)Name or service not known: AH00547: Could not resolve host name *80 -- ignoring!
AH00558: apache2: 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
Syntax OK
Let me go check all the ServerName entries in the conf files.
Okay I've got it down to this.. but still trying..
Quote:
/etc/apache2/sites-available$ sudo apachectl configtest
AH00558: apache2: 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
Syntax OK
The only ServerName that is there, is a domain .com name we own which is pointed to our IP via A Zone at the registry.
I'm not sure what the message refers to.
Last edited by ozstar; 11-28-2022 at 02:49 AM.
Reason: Adding
Okay I see my 80 and 443 are open and I am getting through to the server to the 'net with http
But getting a Forbidden 403 page.
What could cause this ?
I am also looking at changing but to 443 https andcDMZ to help with security plus put it all in a VM.
Yes years ago in LAMP much the same as this, but the old memory is a bit shaky on some things until its boosted again, which is what is happening as we speak :-)
I'll check those conf files again.
Many thanks
One thing that did catch my attention is you using 127.0.1.1. Assuming this is for localhost, that's almost always 127.0.0.1 .
If it works for you, fine, but be aware that almost every article you see for 'localhost' will use 127.0.0.1. You may end up with an inconsistency.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.