Support

Site Restoration

#22146 Restore issue --- exactly the same as ticket #21988

Posted in ‘Site restoration’
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
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by on Saturday, 28 March 2015 18:20 CDT

Tuesday, 24 February 2015 23:08 CST

ml09616
 Hi folks,

I am having exactly the same issues as Chris (user id 'cpaschen'), and on exactly the same host (BlueHost).

Refer to his post: #21988 – Restore looping after pre-installation checklist

As mentioned, I am getting exactly the same issues in the same way.

I too am using Using Kickstart PRO 4.0.0, although I am using Akeeba backup pro 4.1.2, though this will not make a difference.

Could you put me in touch with Chris to ask has his issue been resolved, and how? There is no update on the Akeeba site tickets.

I had hoped to avoid you having to spend/waste time on what is both a duplicate issue, and one which I think is associated with the host rather than Akeeba, so apologies in advance for my posting this ticket..... I couldnt find another way of making contact.

thanks,

Mike

Wednesday, 25 February 2015 03:10 CST

nicholas
If you are sure this is the SAME issue (caused by a .htaccess in the main site's folder when restoring to a subdirectory whose root is inside the main site's folder) then I have to ask: did you try the same solution as ticket 21988? The solution Chris applied was what I posted in my last reply https://www.akeebabackup.com/support/site-restoration/21988-restore-looping-after-pre-installation-checklist.html#p121807 i.e. move the subdomain root outside the public_html folder. If you read his last reply, he does say so:
I'm pretty sure that they probably do have this as a sub-directory under the main domain. Sorry I didn't think of that - but THANKS for documenting the issue so clearly.

So, there :)

FYI, this is not a BlueHost issue. It's how Apache the web server is supposed to work. I have been telling people to put their subdomain root outside public_html since the last 8 years. I was even bitten once by this when I didn't pay attention to cPanel's default – and I should have known better. The bottom line is that it's a very likely issue to occur, it's nobody's fault and it's really easy to fix: create the subdomain afresh, this time putting its root outside public_html.

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!

Wednesday, 25 February 2015 09:12 CST

ml09616
Hi Nicolas,
thanks for your reply.
I did indeed read the other post fully...... and understand that the subdomain being created for the Joomla/Akeeba restore, should be outside the main sites root as in the 2nd image you posted in the other thread.

In my case, it is inside the main root, under public_html (which I know from your post, that it shouldn't be).

My problem is that I cannot create it outside the main root........ BlueHost cPanel just wont let me do that. The "home/public_html" part is hard coded, and all I can enter is the subdomain name.

I will get on to BlueHost to see what they say.

This is my first time with BlueHost, but with many other hosts, I have never had this issue before though, on many restores into subdomains which were under the public_html...... but I guess the htaccess files in the home directories on those other hosts permitted the restore?

This is why I wanted to contact the other poster, Chris, to see what he did to fix his issue.

thanks again... love your work, and your support!!!!!
Mike

Wednesday, 25 February 2015 09:57 CST

nicholas
The actual fix would depend on your .htaccess contents.

I'll go on a hunch here and suppose that you are using the .htaccess Maker to create your main site's .htaccess file. In this case you can just read our troubleshooter page where we describe what you need to do.

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!

Thursday, 26 February 2015 08:29 CST

ml09616
Hi Nicolas...
Well..... I tried changing the htaccess file in both subdomain and root...no go (I'm not using .the .htaccess Maker)

I contacted BlueHost, who said it can't be fixed because the site is optimised for WordPress (the root domain has a WP site.

So...... I will go to another host (which I wanted to do in the first place.... (no disrespect to BlueHost).

Easy as... :-) :-) :-)

Mike

Thursday, 26 February 2015 10:02 CST

nicholas
Your host's excuse is, um, how to put it politely? It's pathetic. They could easily fix the vhost configuration and put the subdomain outside the public_html. Since they don't want to do that I think that moving to a different host is the best thing you can do.

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!

Saturday, 28 March 2015 18:20 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.
Edited by on 2015-03-28 18:20 CDT

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!