Permissions (403). Webpage permissions can be directly set for a file on the U-System or indirectly set through most SSH-type software. There are many, many ways to fix permission problems.

• This Permissions webpage describes the steps for setting the access rights for your public_html files and directories for Menu and Shell interfaces, and for SSH File Transfer users (PCs).
• If you use the Shell interface, log in to your account and just enter the command wwwaccess, which will set permissions correctly for files and directories. Look here to see the commands wwwaccess executes.
• If you use software like Fetch or Fugu, they have easy-to-use (though not always easy-to-find) menu options, like Get Info, that let you set permissions.
• If you hand-set individual permissions (rather than let wwwaccess do all the "legwork"), you need to know that

  files (and graphics) need to allow everyone (Owner, Group, Others) Read access

  in Unix: chmod a+r public_html/*

  directories need to allow everyone to have Execute access

  in Unix: chmod a+x public_html

Not found (404). Your webpage files need to be in your public_html directory (folder). You may have uploaded them into your account but not necessarily into that directory. You can either move them or re-upload into the proper directory. Maybe you forgot to make a public_html directory?

Look at this sample. Start simple (or back off and remove things until your page is simple). If you get stuck, try the CCIT Knowledgebase or go to the Consulting Lab (CCIT, Room 224).

In the filenames for your subdirectories, webpages and graphics avoid using special characters, including spaces. Your PC/Mac can handle spaces, etc., but some of the other components which process your webpages later may not so you may end up with what appear to be missing files.

Make sure any files or graphics in a separate subdirectory are referred to correctly in your HTML. The graphic pic1.jpg in the directory MyPictures would look like MyPictures/pic1.jpg in your HTML.

Homepage Flowchart