Support

Akeeba Backup for Joomla!

#36167 Akeeba Backup FTP Check not working and backup resulting in Bad Request

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

Puckmeister

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:

Hi, when using Akeeba Backup in a new Joomla 4 on a Mittwald Server, nothing happens when i click on the "Test FTP Connection" when trying tio use "Upload to remote FTP Server". There is no message or error, the buttons greys out and that was it.

When i do a baclup now, a file is written on the ftp-server, so i thought it would be ok. Restoring this backup works until opening front- or bnackend for the first time. It always results in a "Bad Request" Message and the website is not there.I can reproduce it everytime i try.

Please advice what to do now.

Thx in advance.

Best Chris

Puckmeister

Just tested other customers that are on J4:

I have this issue on all my customer websites using J4 and actual Akeeba Backup in combination, so actually i am not able to server reliable backups to my customers.

nicholas
Akeeba Staff
Manager

You are confusing three unrelated things.

The FTP connection test does work BUT your server may be blocking the request if you are using a complex password. Complex passwords may be misidentified as an attack by your server, typically because of a rule your host has added to their Apache's mod_security2 configuration.

However, the FTP test is optional. If you enter the correct connection information the backup will be uploaded to the FTP server, as you said happens.

If you can fully extract and restore the backup archive which was stored on your FTP server it means that the backup was fully uploaded. If there was a problem uploading a. you would have received a warning and the file would not have uploaded; b. if the file had only partially been uploaded you'd be getting an error during the extraction.

The Bad Request on the restored site means that the server has rejected the URL you gave it. If you have a live_site URL set up try removing it (leave it blank) in the Site Setup page of the restoration script. Otherwise try clearing all your browser cookies and cache before trying to access the restored site.

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!

Puckmeister

post-processing / FTP

The "Test FTP Connection" is working on all Joomla 3 instances on the same server without problems. I get a message that everything is ok, so the password should not be the problem. To be sure i changed the ftp password to a really simple one (start01) and also it worked perfectly in J3 but not in J4. In Joomla 4 i get no message whatever i try.

backup / restore

I just created a local backup of my site and copied it to a new folder, parallel to the source-joomla. I restored it with newest kickstart into a fresh database, live-url field is blank, and after finalizing i got a bad request. same server, fresh-database, just restored from a backup that never left the machine.

I don't know what to check now, fact is that after backup and restore the result is not a duplicate of the source site.

Puckmeister

Restoration issue is a combination of settings inside of WAF from admintools. i was able to unset this, but i am not sure how to handle this in general. There is a setting "allowed domains" inside of waf request filtering, which seems to be prefilled automatically. When backing up with akeeba this is saved too. After restore it does not work, because the new url is not listed in allowed sites. In joomla 3 the field is empty on all my customer sites.

If you have this case, you have to change this setting inside the database, i found no other was to correct this.

nicholas
Akeeba Staff
Manager

OK, now I have a bit more context. I had understood you were restoring on the same site. Yes, when you are restoring on a different site the Allowed Domains can get in the way. They won't get in the way when restoring to a local server (any domain which resolves to localhost or a reserved local network IPv4 address) since this is always allowed. When restoring to a different live site, however, they will indeed get in the way.

If you are doing a lot of restorations between live, test, staging and dev servers you can add all of these domains in the Allowed Domains.

If you don't care about this feature — it really only matters if your server can serve a site with any domain name you pass it — you can just set the Allowed Domains field to empty.

For restoring any backups you haven't done that you can follow the documented instructions to disable Admin Tools temporarily on the restored site so you can reconfigure this feature.

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!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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.