New Members Attachments Not Uploading

[WildFire.ca]

I have moved my forum to a new host about 10 days ago and have noticed that the new members cant upload attachments. When I made a new account and gave it admin privileges I got this message.

_Enjoy_your_breakfast__by_nocturnalMoTH.jpg:
Failed to write file. Check disc quotas and permissions for the path: /home/vhosts/couchlockcafe.com/httpdocs/attachments/5/9/8


Members that had accounts before the move are having no problems.

[Wayne Luke]

Make sure that the attachments directory and all subdirectories are CHMOD 1777.

[WildFire.ca]

Hello again Wayne, thank you for responding. I have applied the the permissions to that directory, I did it through ftp using the input 777, with apply to all sub-directory's and files checked. I also entered 1777, just to be sure. I am still having the same problem.
29527

[WildFire.ca]

Bump

[Steve Machol]

You need to apply this recursively so all new directories have the appropriate permissions:

chmod -R 777 /home/vhosts/couchlockcafe.com/httpdocs/attachments

[WildFire.ca]

Hello Steve thanks for replying. /httpdocs is the highest I can see in my dir structure. I have set httpdocs to 777, I have also set the attachments folder permissions to 777 with the switch on to apply to all folders and files. Its still not working and giving me the same error. Its is allowing new accounts to upload images to my albums with out any problems. I also noticed most of the other folders are set to 775 with the exception of /signaturepics and a few others. I can see that attachments/5/9/8 folder with the ftp progie and its set to 777, and its also got nothing in it.

I am just messing around with it but I just del'ed the attachments/5/9/8 and tried to upload an attachment and it still tried to upload to the same folder, but it didn't make it. I have made a new folder and the permissions 777 were applied automatically for the "8" folder.

Picture 003.jpg:
Failed to write file. Check disc quotas and permissions for the path: /home/vhosts/couchlockcafe.com/httpdocs/attachments/5/9/8

[Steve Machol]

Do not set httpdocs to 777. You need to do this:

chmod -R 777 /home/vhosts/couchlockcafe.com/httpdocs/attachments

Since the system did not make that directory this means you have not followed those instructions.

[Wayne Luke]

Depending on your system, you might have to change ownership of your attachments directory and everything within it to the same user and group as the Apache user. This would be true if your ISP recently "Hardened" the server. You would use CHOWN for this.

[WildFire.ca]

Ok I have changed the permissions 2 different ways now I have used ftp and also my hosts file manager. I tried to telnet in but was having a hell of a time loging on. I dont know if its me or just that I havent used telnet for ever. I tried open couchlockcafe.com, nata thing happend. Got "could not open connection to the host". I went looking for what I could find on owner of my files and I found this. I will look in to how to use CHOWN as thats new to me. Thank you for your help

29543

[WildFire.ca]

After 22 emails and 10 phone calls I have finally gotten our host company to change the ownership of all the Attachment folders and files files over to Apache. Just the Attachments folder, every other folder in the sites directory, the includes, install folders ect are named chouchl. Now no one on the site can upload or view any attachments, new or old members.

At one point they offered to unharden our domain, IDK if that would help or not.

[WildFire.ca]

bueller bueller

:confused:

We have changed the owner ship of the attachments back to us(chouchl) and we are still experiencing the original problem.

[Steve Machol]

If the error is this:

"could not open connection to the host".

Then it's still a server/hosting issue. You need to contact your host. There is nothing we can do about this.

[WildFire.ca]

The reason I was getting that error was I was trying to telnet in to a shared server on a shared IP, that I can't telnet in too. I have to ask our host company to do the chown commands for us, and they take for ever to do anything. We are still having the new members can't upload pics problem. There server/our site is making the new folders, the folders are being made owner as Apache. This makes it so the site can not access the folder, its also making the folders with the wrong Permissions. I am fixing the problem by going through every folder in the attachments folder and looking for single folder owned by Apache, so what I then do is the file, via ftp and remake it with the same name and then change the permissions. This fixes it, it used to take me a while to do but I am getting real good at it now.

[WildFire.ca]

We are looking for a solution, if you guys have one. Should I be making a repair ticket, I am at a loss here, as what to do?

[Steve Machol]

I'm afraid post #12 is still applicable. This is a server issue.

[WildFire.ca]

So from what you are saying you cant help me cause I have to get my host company to apply the Unix commands. You are unwilling to help cause i have to ask my server host to issue the commands, I cant manually input them my self? So basically your software does not work with hosted server company's? Cause I can get my host to issue what ever command you are suggesting but the fact that I cant do it my self on my shared server you are unwilling to help? I am rather confused here, I can get the host company to do what ever you suggest and they have done what you suggested and it didn't work,it brought our site to stand still, until we got them to reverse your last suggestion. But when I try to telnet in my self and it produces an error cause you can not telnet in to a shared server with a shared IP addy, but I have no problems issuing the commands you suggest, I just cant do them my self, I have to relay them to the host company and get them to do it, and cause of this you are unwilling to help us?

[Trevor Hannant]

Why should a software company provide hosting tools/support?

[cellarius]

Sorry, that's nonsense. That's a problem that originates with your server. Nobody here has access to your server's settings. This is not about anybody being unwilling, but about it just being impossible.

[Steve Machol]

It's not that we are 'unwilling'. As I tried to explain this is a server issue. We are 'unable' to do anything about that. Only your host can. Sorry if that wasn't clear.

If your host refuses to fix this then the 'unwilling' adjective could be correctly applied to them.

[WildFire.ca]

I have taken some time to think about it, and have thought about what you have said, and I agree with you 100%. Its a problem with my server, on there end, the software worked fine at the last place, and only started having problems once we moved. They have informed me that the server is hardened, I am going to try to get them to unharden it see if that helps. Sry I got up'pty before they were telling me it was a software problem(pass the blame type thing) but when calmed down enough too think about it, it is them, has to be, worked fine at the last place.
Thanks for your help I am off to harass them now(: