index.php exists in the root, but when I try to access it, I get Page Not Found
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok, So I am assuming you have a "/webroot" and a "/webroot/wordpress", you can see www.example.com/wordpress/index.php but can not see www.example.com/index.php and wish to know why? Can you see other files in www.example.com/ say if you placed an example.php with just "phpinfo();" in it?
Ok, try seeing if the same files have the same problems in /wordpress if you do the actions in the same way. If they appear to work in /wordpress then their might just be a configuration problem in the apache configuration file.
After reading up a bit, I think this may have something to do with a command named CHOWN?
This changes ownership, or something. I understand that my /wordpress directory should undergo "chown apache:apache" (I'm assuming this means ownership to apache, even though I don't know what that really means).
Do you think my root directory needs some redefining of ownership? If so, how do I do this?
How do I get into a screen in which I can even begin to write commands?
I would suggest if ownerships are the same for the files and they are identical then it's possibly an apache configuration error that is occuring. Just one last test, make a file say ~.test.htm and cp that to both directories and see if it's accessible when it's handled that way.
As /wordpress is seen I would doubt any permission errors on earlier folders but you never know...
I tried a test html file and the behavior is definitely different in both directories (root vs. wordpress). The root directory returned a Page Not Found.
I'm pretty much at a wit's end. The support on Prouddomains wrote:
"The issue is due to the scripting of the website not being correct and is not an issue on our servers. Unfortunately we can not assist with an scripting issue. It is up to you to correct the errors in the scripting as well as move the files that would be required for WordPress to the appropriate folder for the site to function properly. For scripting help you will want to refer to your preferred search engine or forum. I apologize for any inconvenience."