11/9/2022 0 Comments 404 not found error was encountered while trying to use an errordocument to handle the request.![]() ![]() From what I was told, the whole purpose of that /etc/apache2/conf.d/includes/nf is so people can just put a 404.shtml file (or whatever) in their /home//public_html directory and have Apache pull it when there's an error. I still feel like there's a problem cPanelMichael. ![]() Is there way to not have that built, ever?Ĭlick to expand.Thank you! I asked for clarification about editing them and removing the cPanel logo, just to be sure, and they said yes before you answered, but I really appreciate you looking into it for me. To remove the Additionally message, I have to comment out all of the lines in the /etc/apache2/conf.d/includes/nf file. It just seems wrong that cPanel purposefully tells Apache to look for files that might or might not be there. This way, by default, the error pages that are in /var/but had it as a real page, I couldn't use that name. htaccess file, instead of assuming they're going to be there in the /home//public_html directory. I'd think the right way of doing it would be to let users right their own ErrorDocument in an. shtml file does not exist in the /home//public_html directory. What do you think?Īdditionally, a error was encountered while trying to use an ErrorDocument to handle the request.because the. I just thought maybe because the ticket ended up over here, it'd be best to ask over here. Am I supposed to setup an alias in pre_virtualhost_nf or something? I'm a bit confused.Īny thoughts? If not, I'll ask for clarification on the ticket on. # grep 404 /usr/local/apache/conf/includes/nfĬPanel CertifiedI'm confused as to what the answer actually means. # cat /usr/local/apache/conf/includes/pre_virtualhost_nf I was able to implement an Alias directive to allow this to assume the "default" error status with a custom created 404.html in the same location as below: the error seen) would be specific to the cPanel error documents handled, as we can see they reference here : The 404 that is being served is coming in from Apache directly going back quite a few versions, I determined that this appears to be the functionality there as well, going back even further into EA3, it appears that this happens there as well. Is there some environmental variable I need to set to tell Apache to look in two places? Or some Apache directive that tells Apache to look for them specifically in a different directory, outside the /home/sporkschivago/public_html directory? So it seems the /etc/apache2/conf.d/includes/nf file is properly setting ErrorDocuments, Apache just can't seem to find them unless they're in the /home/sporkschivago/public_html directory. I don't think Apache generally looks for a. It's as if they're only searching for them in the /home/sporkschivago/public_html directory and nowheres else. I've grepped the entire /home/sporkschivago/public_html directory and there is no ErrorDocument at all.Įven on the old server, the default error documents would never display when I had a website setup, unless I copied the various shtml files to the /home/sporkschivago/public_html directory. The website is hosted out of the /home/sporkschivago/public_html directory. If so, is there anyway to have Apache server the normal website files through /home//public_html but have it still use the ErrorDocuments in the /var/but it seems ErrorDocument is expecting a relative path, not an absolute. In Apache's nf file, I see a DocumentRoot pointing to /var/Is this the expected behavior? I thought there'd be a default directory Apache would be looking for, for these files, besides just the virtual host's DocumentRoot directory. In the nf file, the 404, for example, is listed as /404.shtml. htaccess file, however, it is set in /etc/apache2/conf.d/includes/nf and /etc/apache2/conf/nf includes that file. Click to expand.The ErrorDocument entry does not exist in the. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |