Furry stuff, oekaki stuff, and other stuff.
You are not logged in.
Waccoon wrote:
Systems administrators are able to write different security rules for any kind of file.
I find this rather confusing. What the reclaim script does is read data from the locked file, make a new file, write the data to the new file, and delete the old one. PHP is supposed to have write access to all files it creates on its own. For some reason, this is not the case with the ban list.
If reclaim doesn't work, and CHMOD 664 and 660 don't work, I may have to check this out myself (if you don't mind giving me your FTP login). I'm afraid with some servers, you just have to try out lots of things until you find what works. Server FAQs generally don't outline all the security settings the host is using.
Alright. I'll note you for the details. Something could be wrong with the ips.txt and hosts.txt file as well.
Systems administrators are able to write different security rules for any kind of file.
I find this rather confusing. What the reclaim script does is read data from the locked file, make a new file, write the data to the new file, and delete the old one. PHP is supposed to have write access to all files it creates on its own. For some reason, this is not the case with the ban list.
If reclaim doesn't work, and CHMOD 664 and 660 don't work, I may have to check this out myself (if you don't mind giving me your FTP login). I'm afraid with some servers, you just have to try out lots of things until you find what works. Server FAQs generally don't outline all the security settings the host is using.
Waccoon wrote:
Try using 660 as a CHMOD number for hosts.txt and ips.txt. "Not a valid stream resource" isn't the kind of error you'd get from a locked file, so the server might be using some kind of security filter for files with execute permissions. It's also possible that TXT files are handled differently than PHP files, which is why you can now use the control panel but the ban list isn't working.
If that doesn't work, either I could log into your account and see if I can fudge it, or you might have to ask your system administrator what permissions are required to make files writable to PHP. Servers can be pretty inconsistent when it comes to security.
I tried to CHMOD the hosts.txt and ips.txt files to 660 but it didn't work at all. Instead, the hosts.txt and ips.txt get locked at all.
How would you know that TXT file are handled differently than PHP files in which it results in the ban list functions to not work properly?
Try using 660 as a CHMOD number for hosts.txt and ips.txt. "Not a valid stream resource" isn't the kind of error you'd get from a locked file, so the server might be using some kind of security filter for files with execute permissions. It's also possible that TXT files are handled differently than PHP files, which is why you can now use the control panel but the ban list isn't working.
If that doesn't work, either I could log into your account and see if I can fudge it, or you might have to ask your system administrator what permissions are required to make files writable to PHP. Servers can be pretty inconsistent when it comes to security.
Waccoon wrote:
OK, there's something about the file permissions that isn't right. Try downloading this file and running it in the root folder of your oekaki. That will refresh the permissions on all the files (but not folders or templates):
reclaim.php
If the script complains it cannot delete certain files, but the files have been reclaimed properly, you'll need to delete the old files manually via FTP.
To fix the templates, download all the templates to your computer, delete them from the server, re-upload them, and CHMOD them to 664. That will clear out the owner ID permissions. Note that it's somewhat troublesome to have spaces in file names. I'd recommend replacing them with underscores, to be safe. You'll need to reset the templates in the control panel if you rename the default template.
If all this still doesn't work, I can take a look at your board with your FTP login.
I ran the reclam.php file and these are the results:
OK: dbconn.php
OK: config.php
OK: ips.txt
OK: hosts.txt
OK: announce.php
OK: banner.php
OK: notice.php
Success! All BBS files should now be writable.
The files listed above have been CHMODed to 666. But there is only remaining problem and it's something in the banlist.php file when I try to ban a hostmask:
Warning: fwrite(): supplied argument is not a valid stream resource in /home/rainbow/public_html/functions.php on line 681
Warning: Cannot modify header information - headers already sent by (output started at /home/rainbow/public_html/functions.php:681) in /home/rainbow/public_html/globals.php on line 116
I tried to modify the header information, but I wound up with a blank page.
In which it leads to me that sometime might have gone wrong when entering the IP or hostmask to ban doesn't write the files on either the ips.txt or hosts.txt.
How can I fix this?
OK, there's something about the file permissions that isn't right. Try downloading this file and running it in the root folder of your oekaki. That will refresh the permissions on all the files (but not folders or templates):
reclaim.php
If the script complains it cannot delete certain files, but the files have been reclaimed properly, you'll need to delete the old files manually via FTP.
To fix the templates, download all the templates to your computer, delete them from the server, re-upload them, and CHMOD them to 664. That will clear out the owner ID permissions. Note that it's somewhat troublesome to have spaces in file names. I'd recommend replacing them with underscores, to be safe. You'll need to reset the templates in the control panel if you rename the default template.
If all this still doesn't work, I can take a look at your board with your FTP login.
Waccoon wrote:
The CHMOD numbers are wrong. Did you have to re-upload backups of these files? When the files are uploaded via FTP, the permissions must be different than if the installer creates them automatically.
Within an FTP program, change the following files to 664 (give write permissions to "groups").
- announce.php
- banner.php (if you have one)
- config.php
- dbconn.php
- hosts.txt
- ips.txt
- notice.php
Make sure any templates you want to edit are also set to 664, and that the templates folder is set to either 664 or 775.
If your login cannot be processed properly, the ban list won't update. Check the CHMOD numbers of the hosts.txt and ips.txt files to be sure.
I tried to CHMOD the following files to 664 for the files mentioned and for the templates, but it's not working at all. I'm still getting the same warning messages.
The CHMOD numbers are wrong. Did you have to re-upload backups of these files? When the files are uploaded via FTP, the permissions must be different than if the installer creates them automatically.
Within an FTP program, change the following files to 664 (give write permissions to "groups").
- announce.php
- banner.php (if you have one)
- config.php
- dbconn.php
- hosts.txt
- ips.txt
- notice.php
Make sure any templates you want to edit are also set to 664, and that the templates folder is set to either 664 or 775.
If your login cannot be processed properly, the ban list won't update. Check the CHMOD numbers of the hosts.txt and ips.txt files to be sure.
My oekaki is working functionally again, but there certain areas of my oekaki where I'm getting warning messages that permission to change content in the Control Panel (cpanel.php) and in the Templates (tedit.php / tedita.php) have been denied:
* Control Panel
Warning: fopen(dbconn.php): failed to open stream: Permission denied in /home/rainbow/public_html/cpanel.php on line 165
Warning: Cannot modify header information - headers already sent by (output started at /home/rainbow/public_html/cpanel.php:165) in /home/rainbow/public_html/globals.php on line 128
* Editing Templates
Warning: fopen(templates/APW Standard.php): failed to open stream: Permission denied in /home/rainbow/public_html/tedit.php on line 145
Warning: fwrite(): supplied argument is not a valid stream resource in /home/rainbow/public_html/tedit.php on line 146
Warning: fclose(): supplied argument is not a valid stream resource in /home/rainbow/public_html/tedit.php on line 147
Also, in the Edit News section, I'm getting numerous warning messages in the mySQL query that the access has been denied for the user "nobody@localhost", not using a password in the online.php and header.php files:
* Edit News - online.php file
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/header.php on line 19
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/header.php on line 19
Warning: mysql_affected_rows(): A link to the server could not be established in /home/rainbow/public_html/header.php on line 20
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/online.php on line 116
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/online.php on line 116
Access denied for user: 'nobody@localhost' (Using password: NO)
Warning: mysql_affected_rows(): A link to the server could not be established in /home/rainbow/public_html/online.php on line 119
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/online.php on line 120
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/online.php on line 120
Access denied for user: 'nobody@localhost' (Using password: NO)
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/online.php on line 128
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/online.php on line 128
Access denied for user: 'nobody@localhost' (Using password: NO)
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/online.php on line 131
* Edit News - header.php file
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/online.php on line 131
Access denied for user: 'nobody@localhost' (Using password: NO)
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/header.php on line 175
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/header.php on line 175
Warning: mysql_result(): supplied argument is not a valid MySQL result resource in /home/rainbow/public_html/header.php on line 176
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/header.php on line 180
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/header.php on line 180
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/rainbow/public_html/header.php on line 180
()
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/header.php on line 182
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/header.php on line 182
Warning: mysql_result(): supplied argument is not a valid MySQL result resource in /home/rainbow/public_html/header.php on line 183
Warning: mysql_query(): Access denied for user: 'nobody@localhost' (Using password: NO) in /home/rainbow/public_html/header.php on line 192
Warning: mysql_query(): A link to the server could not be established in /home/rainbow/public_html/header.php on line 192
Lastly, I'm running a test in the banlist.php file to place ban on IP address 33.37.39.34, but everytime I press submit, none of the data is written onto the ip.txt or hosts.txt files.
How can I get this all fixed? I'm still in a knot after my oekaki came back up only to find that all of the old data from 27 December 2005 was restored and I'm trying to get things all straightened out as soon as possible.