Support

UNiTE, Remote CLI, eXtract Wizard

#3602 403 error

Posted in ‘UNiTE and Remote CLI’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
Tool
UNiTE
Tool version
n/a

Latest post by nicholas on Sunday, 14 February 2010 05:47 CST

user8261
Hi,

I have set up cronjob, but it sends me errors everytime

JoomlaPack JSON CRON Helper
403 operation is not allowed
Last operation has failed.


what can I do?

dlb
Does your backup work from the back end? Do you have the front end backup enabled and a secret word set? Does your secret word match what you used in the cron job?


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user8261
neither from backend nor from frontend
I set up cron script like that:
/usr/bin/php -q /home/schel4ok/public_html/stendart/www/administrator/components/com_joomlapack/assets/scripts/cron1.php

and every script run I have this message
JoomlaPack JSON CRON Helper
403 operation is not allowed
Last operation has failed.

dlb
Let's start with the back end backup. If that doesn't work, neither will a cron backup. Please try it from the back end then zip and post your backup log.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user8261
Invalid AJAX Response: 500 Internal Server Error 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. JoomlaPack_Debug_Log-20100209.zip

dlb
The first problem is your Output folder. The Output folder and it's contents are automatically excluded from the backup. You have your Output folder pointed to the root of the site, so the whole site is excluded.

The warning that you get about the default Output folder is a security warning. That is a known location used by a popular backup extension, that makes it easier for the bad guys to attack your backup file. The default folder is protected by a custom .htaccess file, but your backup is safer if it is stored above the web root where it is not accessible from the web at all. Everything works if you use the default folder.

I'm not sure why you got the 500 error. The Output folder may not be the only issue. Let's change that back to default and see if the problem goes away.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user8261
I made backup from backend successfully to folder, which is out of ROOT.

But cronjob still not working using same profile.
It sends me 403 error once again.

JoomlaPack JSON CRON Helper
Starting backup
403 operation is not allowed
Unknown server response type
Last operation has failed.

I attach log of my last backend backup. JoomlaPack_Debug_Log-20100210-2.zip

dlb
Cron is not my friend, time for me to get Nicholas involved. :D


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
Again, this is not a CRON issue, it's a server issue. Your server simply refuses to serve the web request. This is dependent on the server configuration, you should ask your host if they have some anti-DoS system installed which intercepts multiple successive requests to the same resource.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user8261
I asked hoster about this problem and they said that they have no such systems.
But I found on your forum that front-end backup must be enabled for cronjob. I think it must be written right on the cron tab to avoid lots of questions on the forum.

Now after enabling front-end backup I have slightly different error description.

JoomlaPack JSON CRON Helper
Starting backup
403 access is not allowed
Unknown server response type
Last operation has failed.

user8261
I went to joomlapack settings once again and put secret code into corresponding field in front-end section of settings.

It's much better to make tooltip on cron page in backend that user must do these steps prior to setup cron script. Because these steps are not obvious.

Now I've got message that my cron backup is ok. But I noticed one strange thing: my manual backup archive weight = 1.73 Gb and after cron backup with same settings archive is only 338.56 Mb.
Why it is so?

dlb
One of them isn't right, probably the small one. Please zip and post the backup log.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user8261
here is report downloaded from backend.
I don't know which one it is. There was no choice there. Hope this is report from last cronjob backup. LAST_JoomlaPack_Debug_Log.zip

and this is report from my manual backend backup taken from previous post
JoomlaPack_Debug_Log-20100210-2.zip

dlb
I found part of it. You did some cleanup between backups. There was an administrator.zip, components.zip and images.zip that were included in one, but not the other. That doesn't account for the entire difference. Were there other files that you deleted?


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
Regarding the instructions, there is this documentation thing I've written. It's accessible by clicking the "Help" button in the toolbar of the CRON Scripts Manager ;) The page is here http://joomlapack.net/help-and-support/documentation/joomlapack-user-guide/item/651.html and it clearly reads:

The front-end backup feature MUST BE ENABLED in the JoomlaPack Configuration for the CRON scripts to work at all and you MUST configure the correct secret word and site URL in the CRON script configuration BEFORE using them.


So, I think it has you covered.

About the other issue, as Dale said, you cleaned up your site's files in the meantime. Yeap, this certainly explains a size difference. It's always a good idea to either clean up such files (best practice, security-wise) or manually exclude them from the backup using the Files Exclusion feature of JoomlaPack.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user8261
when I click on help button it shows me "Profiles management" page.

Though I remember that I read this article about cron setup, but actually I stopped to read just before this paragraph. Because "how cron script works" seemed to not so important. I supposed that all important information I need must be included in "CRON script configuration" paragraph. That's why I missed this thing.

About backup size. You are right I deleted 3 archives from host in the meantime, because after successful backup I didn't need them anymore. Just forgot about them and I don't expect the difference will be more than 1Gb.
That appeared to me terrible.

nicholas
Akeeba Staff
Manager
Hmm... looks like the help button redirects to the wrong page :( Yeah, it's an important chapter, but I couldn't cram it on the page, that's why I have it in the manual. Anyway, version 3.0 will have a completely different CRON backup method, which won't require turning on the front-end backup.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!