benh359 at August 10th, 2013 11:09 — #1
Hi, I haven't been able to get the "updateip" tool to work properly when installing Magento onto AWS - I am just trying to remove the default /magento/ install directory so my site works in the root domain.
I have run the updateip tool various times and followed instructions on various threads (eg http://community.bitnami.com/t/magento-bitnami-domain/14164) every time I just end up with the standard Bitnami congratulations landing page still in the root and am then unable to browse to /magento/
Any help would be much appreciated.
kaysa at August 12th, 2013 12:22 — #2
Sorry, it is a bug in the magento image. We are fixing it and we will release a new version. In the meantime please edit the /opt/bitnami/apache2/conf/httpd.conf file and comment the line:
Then include this line in the /opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf. This file should look like the below:
# BitNami applications installed in a prefix URL
After that change restart apache with
sudo /opt/bitnami/ctlscript.sh restart apache
benh359 at August 12th, 2013 13:57 — #3
Thanks Kaysa, is that instead of running updateip completely or in addition to?
beltran at August 13th, 2013 04:05 — #4
You can do it manually instead of running "updateip". This issue was fixed in latest Magento 188.8.131.52-3 version.
kaysa at August 13th, 2013 09:25 — #5
Sorry for the late answer. That should be changed after executing the updateip tool. In any case, as Beltran mentions we have released a new version that fixes this.
therealkris at August 15th, 2013 16:05 — #6
I am having the same trouble getting the updateip tool working properly. I set up the instance today and cannot get it to load to the root domain. I have followed the same steps as above but I still get the bitnami landing page and cannot browse to /magento.
I'm using the 64 bit version of BitNami Magento 184.108.40.206-1
kaysa at August 16th, 2013 16:47 — #7
Did you remove (or comment out) the line:
In any case, could you use an instance with a newer version of Magento? This issue is fixed in 220.127.116.11-3 and it that version running the updateip tool should be enough.
pedroschmitt at August 17th, 2013 10:05 — #8
I have this problem too.
At aws marketplace i can only find the "18.104.22.168-2". The 22.214.171.124-3 is not there yet.
But i could find searching at community´s AMI.
With the 126.96.36.199-3 the tool "updateip" worked!
victor at August 19th, 2013 10:40 — #10
It takes a while to get our latest images published on the AWS marketplace. Meanwhile, you can use our AMIs directly from our website as you have done:
pedroschmitt at September 2nd, 2013 17:49 — #11
I see that are a 188.8.131.52-4 version now. Could you tell what is the diference from 184.108.40.206-3?
victor at September 3rd, 2013 04:16 — #12