The free forums are no longer in use. It remains available as read-only archive.
12:41 am
January 4, 2011
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
5:24 pm
January 4, 2011
Hi Ovidiu, Thanks for your answer.
Hola Ovidiu, Gracias por tu respuesta.
Unfortunately it didn't the trick. The wp-content folder was already having 755 permissions but the plugins folder inside didn't. So I changed the permissions as you suggested but it dropped the same error again.
Desafortunadamente eso no hizo el truco. La carpeta wp-content ya tenia permisos 755 pero la carpeta plugins en su interior no. Asi que cambie los permisos como tu sugeriste pero me arrojo el mismo error otra vez.
I have checked the error log file and it is pointing to some errors related to the sql database and relationships, nothing about the XCloner plugin. Should I look for anything different?
Ya he checado el archivo de registro de error y apunta a algunos errores relacionados a la base de datos sql y relaciones, nada acerca del plugin XCloner. Deberia buscar por algo distinto?
Thanks in advance!
Gracias anticipadas!
XCloner! Support said:
Hi there! You should check your site error log, the 500 error message is detailed there, as a hint, try and apply 755 permissions on your wp-content/ and wp-content/plugins folders and see if it helps
Regards, Ovidiu
Where is the "site error log" stored? I have found files named error_log in several places, but none contain any messages from xCloner.
Quibbler: try and check with your hosting provider, they should be able to tell you where your main site error log is located and where you can see it.
Again, usually if you are receiving a 500 error when you are trying to access XCloner for the first time, it is usually related to a permission issue, so applying 755 or 750 on these folders should help:
- wp-content
- wp-content/plugins
- wp-content/plugins/xcloner-backup-and-restore
Ovidiu
Thank you for your response. All of the directories you mentioned already have permissions set at 755. Note that I am certain that it is not a host configuration issue because I have another site on the same host and in the same filesystem. I have used xCloner to backup that other site without any error messages.
What else might cause the problem?
Is there a way to get xCloner to be more specific about what operation it was attempting to process when the server returned the error?
10:20 am
September 26, 2010
10:58 am
September 26, 2010
Ah, now we are getting somewhere 🙂
Could you try and install the XCloner version 3.0 available here http://wordpress.org.....ownload/ , and try to generate a backup with that
Let me know if you have any further issues, and if so, please post a screenshot with the error. One more thing i advise is to try and exclude large files when creating a backup, XCloner 3.0 has an automatic option for excluding them if you check the XCloner Config System tab
Ovidiu
1 Guest(s)