I am working on a testing server and used AkeebaSOLO to backup and restore the site on the testing system. I wanted to backup the testing system with AkeebaSOLO but when I go to login, AkeebaSOLO kicks me to the original server domain. I can't seem to login on this new domain. I sure this is a simple htaccess or config fix, but I can't find it.
#29267 Logging into Akeeba Solo on new domain
Posted in ‘Akeeba Solo (standalone)’
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
Akeeba Solo version
n/a
Latest post by on Sunday, 25 March 2018 17:17 CDT
Friday, 23 February 2018 08:37 CST
tampe125
Akeeba Staff
Hello,
this happens because Akeeba Solo saves the site URL in its configuration.
Including Solo in the archive is useful only if you're going to install the backup on the same server. Otherwise I'd strongly suggest you to exclude from your backup and (if you really need it locally) to install it again. To save some time you can export all the backup profiles from your live site and then import them again after installing Solo in your test server.
this happens because Akeeba Solo saves the site URL in its configuration.
Including Solo in the archive is useful only if you're going to install the backup on the same server. Otherwise I'd strongly suggest you to exclude from your backup and (if you really need it locally) to install it again. To save some time you can export all the backup profiles from your live site and then import them again after installing Solo in your test server.
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Sunday, 25 March 2018 17:17 CDT
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.