New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Depends on error. Look at them, see what they are, and act accordingly.
i search them on google but they seem very confusing to fix. Answers are not clear. Its not like wordpress fixes
Then leave them be. You are incapable of dealing with it.
yeah thats what i do . But the point of the question is: leaving them would cause issues or not?
I will say again: It depends.
Post an example error your concerned about.
Error can range from simple "woops single domain not working" to "everything is down"
Like these:
Was getting 'Primary script unknown\n''Primary script unknown\ 'Primary script unknown\n' errors a lot before now not getting it.
They're just warnings. You can ignore them.
What it says is that a folder, located in your home folder called domains/sharedip doesn't exist. You can create it with a file manager/FTP if you really want to, but you don't have to do that.
Also it appears that you don't have SSL setup for whatever domain is your server name. Only important if you want to encrypt your website
"Primary script unknown" is probably because you're not running custom CGI software
I think @folom is colocrossing tier 3 support and he comes here to solve tickets
If it works, don't fix it.
And, at last, the truth is out.
I'd at least silence them if you're not going to fix them. Those logs typically get made roughly in line with how much traffic you get, so if you get a lot of traffic, you'll get a lot of useless logs. In more extreme situations this can lead to running out of space and problems coming up
The mismatched certificate should be easy enough to correct/replace.
I would look at [core:crit] first.
Yes. Obviously.
@folom
If you ask for help always provide some basic info, things like apache version, panel type and version (if any is used), OS type and version, etc.
One of your problems seems to be with rights not being properly set. To fix that first find out the user apache is running as (
ps axo user,command | grep apache
). Then dochown -R XYZ /home/admin/domains/
where XYZ represents the name found in the first step (most probably something like "www").