Support

Akeeba Backup for Joomla!

#36243 Testing Akeeba Backup with WebCron.org get error 302

Posted in ‘Akeeba Backup for Joomla!’
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

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

dunwin

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!


EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.


Description of my issue:

I am testing out Akeeba Backup with WebCron.org as our ISP is stooping support for CRON jobs

I have an account with WebCron and credit. 

When I test the Web Cron job it fails with 302 error explanation below.

I have copied the link from my Akeeba settings and set timeout  to 180 as recommended.

Any ideas what I am doing wrong?

10.3.3 302 Found

The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).

If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

      Note: RFC 1945 and RFC 2068 specify that the client is not allowed
      to change the method on the redirected request.  However, most
      existing user agent implementations treat 302 as if it were a 303
      response, performing a GET on the Location field-value regardless
      of the original request method. The status codes 303 and 307 have
      been added for servers that wish to make unambiguously clear which
      kind of reaction is expected of the client.

 David Unwin

nicholas
Akeeba Staff
Manager

Please contact WebCRON.org's support. They are supposed to follow 302 redirects. Maybe they have an option you need to enable which did not exist in the past.

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!

dunwin

OK, Will do. Please leave this ticket open and I will report back on what WebCRON Support have to say.

 David Unwin

dunwin

Hi Nicholas,

Here is the answer I received from WebCron Support

"I had a look at your cron task and I have checked the last call log for this task.

 The webcron error code is 928 for this call which means that the backup script did not return within the selected timeout (180 seconds).  You may want to try the timeout just above (600 seconds) and check if the backup script returns within this new time frame."   So, I changed the default timeout from 180 to 600. This resolved the problem - See screen shot   Kind regards David  

 David Unwin

dunwin

Screen shot attached

 David Unwin

nicholas
Akeeba Staff
Manager

Ah, that makes sense! If you had been given a 9xx code I would have told you the same, I know this is a special error code WebCRON uses for timeouts during an Akeeba Backup run :) 

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!

dunwin

Ok , great...closing this ticket now

 

 David Unwin

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.