NineChime forum

If you try to access the pictures folder directly, the server blocks access with a 403 Forbidden error.  This is uncommon, but not unusual.  However, I tried to directly access the picture I drew, and it displayed an error.  Click on this link to see if it works: (removed).  I intentionally chose a really old picture, so it would not likely be in your web browser's cache.  For me, neither of the previous two links works the way they should.

Now, what could be happening here is that the server will only display images if the HTTP referrer matches your web address.  That is, images can only be displayed in the oekaki, but not accessed directly through a link without visiting and looking at the actual oekaki itself.  Trying to look at avatars directly by typing in the avatar's name in the web browser address bar does the same thing.

This is a problem, because Java (the part of the web browser that runs the paint program) does not pass an HTTP referrer.  Therefore, the server refuses to let the oekaki applets load any pictures so they can be retouched, and the server will do this for both oekakis as well as uploaded pictures.  This is definitely related to your web server's security policy.  The question is how to disable it.

The first and easiest thing to try is to give the "pictures" folder less restrictive security permissions.  I assume you're familiar with FTP and uploading the PHP files to the server.  If so, then you can try changing the CHMOD number of the pictures folder.  Most servers have a default CHMOD number of 755 for folders.  Try using 775, and if that doesn't work, try 777.  Allowing looser permissions is fine for a folder that only contains pictures, so we don't have to worry about security issues.  However, some servers don't like 777 and might totally block access to the folder.  If that happens, you can go back to 775 or 755.

If that doesn't work, we can try using a custom ".htaccess" file to tell the server to allow full access to the pictures folder.  That might not be possible, though, so try setting the CHMOD number to 775, first, and let me know what happens.

Also, keep an eye on your space usage.  The board is using about 250 Megabytes of space on the server, spanning 136 pages worth of pictures over just 4 months.  That's a lot of pictures.  Check the control panel of your web server to see how much disk space you're allowed to use.  If your limit is, say, 500 Megabytes, you may have to reduce the total number of pictures that may be stored at a time, to make sure you don't go over the limit in a few more months.  It would just be a good idea to check.  Nothing needs to be done right now.

Last edited by Waccoon (07-03-2009 08:52:03)

Ah, yes, hotlink prevention would do it.  From what I can tell, it's working fine, now.  Feel free to delete that "picture" I drew.

Turning off indexes would be fine if you wish to do that.  It won't affect the oekaki.

Also, leaving the folder permissions at 755 would be fine.  If the diagnostics screen on the oekaki doesn't say "Locked" for any of the folders, then everything is working.

1GB of space should be enough for ~6,000 pictures.  The diagnostics screen shows how much space is being used.