XF 1.5 Getting Error Message When Trying to Attach a File

[Matthew Hutchinson]

My board is 19 months old. I haven't changed anything in the ACP. I just tried attaching a file to a post and got this:



Some of my users reported the same error last month, but it resolved itself a couple hours later.

EDIT: One of my users just posted a message reporting the same error.

 

[Ozzy47]

Are you using the flash uploader?

Admin CP -> Home -> Options -> Attachments -> Use Flash Uploader

If so, disable it and have the user try to upload the same image again.

 

[Matthew Hutchinson]

I had both HTML5 and Flash enabled. Just disabled Flash, and no dice.

 

[Ozzy47]

Are there any errors in the error log?

 

[Matthew Hutchinson]

Are there any errors in the error log?

I checked the server error log. It was clean. Is there another log I should check?

 

[Ozzy47]

Hmm, check the permissions on internal_data/ and data/ folders, they should be 777 so it can write to it.

 

[Matthew Hutchinson]

Every folder is 755, including those two. FileZilla is listing them as last being modified the day I upgraded to XF in June 2016.

 

[Ozzy47]

Hmm, I am at a loss then, hopefully someone else comes along with a different idea.

 

[Matthew Hutchinson]

I think it might be server-side. Earlier this week, I installed XF 2.0 in a test folder off my live board's root so I could tinker with the new features, and I created a new mySQL database exclusively for the test board. I was working with it at around midnight and posted several messages to see how everything looked. Two of them included image attachments. Everything was working smoothly. Meanwhile, my users were posting away on the live board.

I just tried attaching a file to a new thread on my test board. XF 2 stopped the upload and crossed out the file name.

EDIT: Another user just commented that they've encountered the same error a few times before. It seems to resolve itself after an hour or two, so it's apparently a recurring issue. Nevertheless, I'd like to find a permanent solution.

 

[Paul B]

If it's happening randomly and sporadically then your sysadmin or host would be best placed to investigate and resolve it.

 

[Matthew Hutchinson]

If it's happening randomly and sporadically then your sysadmin or host would be best placed to investigate and resolve it.

I'm inclined to agree...

:: curses under breath ::