Forums

file permissions (24 posts)

  1. tridad
    Member
    Posted 5 years ago #

    I have loaded a new blog, http://www.triathletedad.com
    However, I'm getting the following errors:
    When I try to go to the dashboard: You don't have permission to access wordpress/wp-admin/index.php on this server. index.php is set to 666 ( as per http://codex.wordpress.org/changing_file_permissions)
    If I go to the main page -- it is blank.
    If I go to themes, I get this error: You don't have permission to access /wordpress/wp-admin/themes.php on this server. The file is set at 666.
    What step am I missing?
    Thanks,
    Susie
    I have two blogs running -- the first one is running fine.

  2. ronchicago
    Member
    Posted 5 years ago #

    are the permissions and both your blogs the same?

  3. tridad
    Member
    Posted 5 years ago #

    I'm working to change them -- the other blog is http://www.susiej.com the index permission is 755

  4. doodlebee
    Member
    Posted 5 years ago #

    folders are supposed to be set at 755, files at 644.

  5. tridad
    Member
    Posted 5 years ago #

    Does it matter if both web sites have the same settings?

  6. tridad
    Member
    Posted 5 years ago #

    I got everything back up -- thank you for that -- except I am unable to work on the theme. I get that the file is not editable.
    The theme folder is set to 755.

  7. ronchicago
    Member
    Posted 5 years ago #

    don't know the answer to your question, doodlebee might. my line of thinking at this point is it would be strange if both were set exactly the same and one was not working. i would match the one that is working and see what's up.

  8. tridad
    Member
    Posted 5 years ago #

    I matched up the themes folder for both sites to 755-- the http://www.susiej.com, that is working, and the http://www.triathletedad.com is set to 755, and susiej works, but triathletedad does not.

  9. tridad
    Member
    Posted 5 years ago #

    Searching through the support forums -- I took the advice given to many, and changed the themes folder and the blixkreig folder -- both to 666. Still, the permissions were blocking me from editing the theme through the dashboard.

  10. doodlebee
    Member
    Posted 5 years ago #

    Theme files have to have the permissions changed to edit them. Mine need to be set to 746, but sometimes you have to set them to 777. They'll *work* at 755, but you can't edit without changing the permissions.

    If you do that, then you need to remember to change the permissions back when you're finished editing so your site won't get hacked.

    Alternatively, you can just open the files in notepad, make your changes and upload them.

  11. tridad
    Member
    Posted 5 years ago #

    Thanks for your help, doodlebee. (Geesh, that's fun to say.)
    I changed the theme folder:
    746 created an error, and wiped out all themes
    777 did not make them editable
    755 still did not make them editable.

    Any other numbers I could try?
    Thanks

  12. ronchicago
    Member
    Posted 5 years ago #

    i agree - i love doodble bee!

    what is the downside to reinstall again? sorry about this but it worked on permissions once before for me. how are you editing your permissions? ftp client? cPanel? i got rid of plesk because it was a permissions/naming nightmare for me.

  13. tridad
    Member
    Posted 5 years ago #

    I am using FTP. I am willing to reinstall -- however, after I had the same problem, I had install4free do it this morning, and they got the same error.
    Do you think it's worth re-installing?

  14. tridad
    Member
    Posted 5 years ago #

    I'm sorry = filezilla

  15. ronchicago
    Member
    Posted 5 years ago #

    You would think install4free would work. The solution is in the details -maybe. Before you try reinsalling again, think about this. I stopped changing permissions through my ftp client and do it on the server with software provided by my host to narrow down accountability and have support = cpanel. When I got my host involved they finally had me migrate off of plesk to cpanel. I still have problems as you can see if you visit the forum ;-) but the permissions thing seems to be solved.

    I feel for your pain. One works. One doesn't!

  16. tridad
    Member
    Posted 5 years ago #

    OK -- I'll check into that. Now that I've learned to edit through filezilla -- it's really not that bad.

    But I'm wondering -- will I have more problems down the road that I'm not aware of yet?

  17. ronchicago
    Member
    Posted 5 years ago #

    Fix this first before you start a-wondering ;-) i just fixed a three-day old problem - see "can't connect database" in installation forum - YES! I won't do an iron man but get a sandwich and maybe when i return to take a peek you will be all set!

  18. tridad
    Member
    Posted 5 years ago #

    I contacted my host, http://www.webstrikesolutions.com and this was their response:
    "Your chmod permissions were not recursive, so the individual themes and files did not havce correct 777 permissions. I have made all files and directories under themes chmod 777 now."
    I'm not sure why my changes to 777 did not work and theirs did work -- but everything is fine now.

  19. tridad
    Member
    Posted 5 years ago #

    Just a follow-up on the reason my settings weren't working, and the web host's were:
    You had set the permissions correctly on the initial folder, however I don't believe that setting the permissions on a folder in Filezilla will allow you to set the permissions for the files and folders BENEATH it (i.e. they will not inherit the permissions you set).

    You could try using a different FTP program, such as SmartFTP, which may allow you to set permissions recursively.

    Hope the sandwich was good.

  20. ronchicago
    Member
    Posted 5 years ago #

    ok!

    btw - cpanel gives the option of setting just the folder and/or folders within. i looked up smartFTP but could not tell if it works on mac platform. i am using captain FTP - nice mac exclusive client though i did not look to see if it is recursive...

    i don't know why the host gets things done sometimes that i can't. that's why one keeps good a relationship with host.

    had something a bit healthier than sandwich - i was informed ribs/calamari/risotto leftovers tonight. don't fret, i burn it off...

  21. doodlebee
    Member
    Posted 5 years ago #

    Oh my God - are you serious? You host has set *all* of your folder permissions in your wordpress installation to 777?

    Holy crap. Time to get a new host. If your site isn't hacked (and the host's server isn't compromised) within a month, I'll be shocked.

    That is a MAJOR security risk. You should *never* leave yourself wide open like that - and if your host did that for you, then they have absolutely no idea what they're doing. (and when someone compromises the server because of these decisions, I'll bet you $20 they'll come back and say it's WordPress' fault.)

    I'm getting queasy just thinking that there is a host out there that will purposely do this. Agh. How *horrible*.

    Get a new host.

  22. webDressing
    Member
    Posted 5 years ago #

    Yep! Nothing is more important to your site than its security. Anything that tries to compromise it you need to get rid of, including the host...

  23. ronchicago
    Member
    Posted 5 years ago #

    isn't true that it is necessary to go 777, like for the uploads folder for the initial upload? but once wp makes the initial connection you can (sounds like must!) go back to default settings? is default the best practice settings?

    speaking of hacking - where/how does one get in? are we saying that because wp sits in public_html everything is viewable = the need for the correct permissions?

    i have been reading that important files should not even be inside the html_public folder, like a mysql_connect.php file.

  24. doodlebee
    Member
    Posted 5 years ago #

    Yes, the uploads folder initially has to go to 777. Then you upload one image, and change the permissions back to the default (usually 755). WordPress will still have access to the uploads folder - it only needs permission once and then it always ahas it.

    True, important stuff can be housed outside of public_html. But some hosts won't allow you to do that. And then you have to do more finagling to get things to work. But the way WordPress is set up, it's still safe to do it how it is now, as long as your permissions are sett appropriately.

    Setting 777 give *anyone* access to your site. All they have to do is find the password to get in (some of them don't even need that). Once they're in, if everything is set at 777, they can do major damage, get info on the server and then compromise the entire server - take down many sites in one swoop rather than doing it one at a time.

    How they get in? I don't know - I'm not a hacker. I *do* know that, to protect yourself, 777 is NOT a good thing to keep your filesystem at. If this host is telling *this* guy to do that, imagine what all the other people in his server are doing? Everyone could be open. That server is way too insecure for anything - he needs a new host who knows what they're doing.

Topic Closed

This topic has been closed to new replies.

About this Topic