Closed jlibasci closed 5 months ago
jotamartos
commented
7 months ago All Joomla!-related files are inside the /opt/bitnami/joomla directory. Some of the files are symlinked to /bitnami/joomla but you can move those files to the original folder if needed. In your case, you are using a app's plugin so I suggest you ask the Joomla's or the Akeeba's developers and their documentation pages to know more about this.
markrids
commented
7 months ago Just adding this to help, as this is something I do quite regularly.
I take daily akeeba backups direct to OneDrive, so they are accessible separately from my website. if anything happens to my instance, I can always get to my backup file.
When I need to move my site to a new blueprint (if PHP level changes, for example), I spin up a new Instance. I use LAMP, but you could equally use Joomla. I then upload the Akeeba backup file to the new Instance, into the htdocs folders. From there, I unzip the Akeeba backup file. This puts everything into the right place. The kickstarter php etc are all already in the backup file. From there, browsing to the instance IP address automatically loads the installation page. Fill out the form with the relevant details, and follow it through. It will upload your data into your database and sort out all the configuration. The final part is to remove the Installation folder, so the next time you browse to your IP address, your site will load correctly.
There are a number of other fiddly bits, such as creating your SSL through cert-bot, and sorting the ownership to daemon:daemon to ensure it runs correctly, but that's pretty much it. I've been following that process for a couple of years now, so am comfortable it works ok.
Hope that helps!
jlibasci
commented
6 months ago How do I navigate to the htdocs directory from the browser -
/opt/bitnami/apache/htdocs
On Mar 5, 2024, at 11:13 AM, Mark Ridsdale @.***> wrote:
Just adding this to help, as this is something I do quite regularly.
I take daily akeeba backups direct to OneDrive, so they are accessible separately from my website. if anything happens to my instance, I can always get to my backup file.
When I need to move my site to a new blueprint (if PHP level changes, for example), I spin up a new Instance. I use LAMP, but you could equally use Joomla. I then upload the Akeeba backup file to the new Instance, into the htdocs folders. From there, I unzip the Akeeba backup file. This puts everything into the right place. The kickstarter php etc are all already in the backup file. From there, browsing to the instance IP address automatically loads the installation page. Fill out the form with the relevant details, and follow it through. It will upload your data into your database and sort out all the configuration. The final part is to remove the Installation folder, so the next time you browse to your IP address, your site will load correctly.
There are a number of other fiddly bits, such as creating your SSL through cert-bot, and sorting the ownership to daemon:daemon to ensure it runs correctly, but that's pretty much it. I've been following that process for a couple of years now, so am comfortable it works ok.
Hope that helps!
— Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-1979254562, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6NSGA6EORIRC2BF67DYWX4MBAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZZGI2TINJWGI. You are receiving this because you authored the thread.
jlibasci
commented
6 months ago All, I am trying to do is restore a Joomla site to Bitnami, I would think this would be basic feature of the product.
As bitnami has a number of symlink directories and protected directories there are some complexities that just need to be documented.
If was on my own server this is super simple, I am just looking for this information
Put the files into this directory (two files the kickstarter.php and the archive zip file)
Then navigate to this URL to access the kickstarter.php
I think if there was some better documentation around this the use of the product would definitely increase.
Cheers, Jason
On Mar 5, 2024, at 9:52 AM, Juan José Martos @.***> wrote:
All Joomla!-related files are inside the /opt/bitnami/joomla directory. Some of the files are symlinked to /bitnami/joomla but you can move those files to the original folder if needed. In your case, you are using a app's plugin so I suggest you ask the Joomla's or the Akeeba's developers and their documentation pages to know more about this.
— Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-1979086513, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6OSLFKDBNWRC6DNSHLYWXS2VAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZZGA4DMNJRGM. You are receiving this because you authored the thread.
markrids
commented
6 months ago I just browse to the static ip address. If I have already setup ssl, I browse to the domain name. For a LAMP server, that takes me to htdocs; for a Joomla server, it takes me to the joomla folder.
For a LAMP server, the files go into the htdocs folders. For a Joomla server, put them into the joomla folder.
My instructions would be:
This will setup the database & config from the archive & restore your website from the backup to the new server.
jlibasci
commented
6 months ago Every time I copy anything to the Joomla folder it disappears right after its uploaded -
I was able to do upload everything to the tmp folder but then I was not able to extract it to the correct location.
I was able to access the tmp folder from the ipaddress and perform the whole restore except it was not to the correct location.
On Mar 17, 2024, at 2:52 PM, Mark Ridsdale @.***> wrote:
I just browse to the static ip address. If I have already setup ssl, I browse to the domain name. For a LAMP server, that takes me to htdocs; for a Joomla server, it takes me to the joomla folder.
For a LAMP server, the files go into the htdocs folders. For a Joomla server, put them into the joomla folder.
My instructions would be:
put archive folder into the folder designated above (The extraction routines are in the embedded installation folder already) unzip the archive folder navigate to the static IP address fill out the forms presented This will setup the database & config from the archive & restore your website from the backup to the new server.
— Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2002596994, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6JZH666XTDQSE2R3UDYYXX7HAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGU4TMOJZGQ. You are receiving this because you authored the thread.
markrids
commented
6 months ago Oh, that doesn’t sound right.
Maybe spin up a new Joomla instance & try from a vanilla server.
This is the process I use, straight from my notes:
In SSH, create SSL certificate using bncert-tool sudo /opt/bitnami/bncert-tool
Upload zip file to bitnami home folder, so have correct ownership of bitnami:bitnami. Use filezilla to do this. You cant put it direct into the joomla folder because of permissions.
Move zip to stack/joomla, using SSH sudo mv upload.zip stack/joomla/upload.zip; cd stack/joomla; sudo chown daemon:daemon upload.zip; sudo unzip upload.zip;
Check ownership etc of files/folders (if you dont do this, the install will fail!) cd; sudo chown daemon:daemon -R stack/joomla/; sudo find stack/joomla/ -type f -exec chmod 0644 {} \; sudo find stack/joomla/ -type d -exec chmod 0755 {} \;
Run the install process
To be honest, this is why I switched to using a LAMP server. The whole load process becomes far more straightforward.
jlibasci
commented
6 months ago I deleted the entire instance and created a new instance but any file that is uploaded to the Joomla directory immediately disappears right after its done uploading.
On Mar 17, 2024, at 5:07 PM, Mark Ridsdale @.***> wrote:
Oh, that doesn’t sound right.
Maybe spin up a new Joomla instance & try from a vanilla server.
This is the process I use, straight from my notes:
In SSH, create SSL certificate using bncert-tool sudo /opt/bitnami/bncert-tool
Upload zip file to bitnami home folder, so have correct ownership of bitnami:bitnami. Use filezilla to do this. You cant put it direct into the joomla folder because of permissions.
Move zip to stack/joomla, using SSH sudo mv upload.zip stack/joomla/upload.zip; cd stack/joomla; sudo chown daemon:daemon upload.zip; sudo unzip upload.zip;
Check ownership etc of files/folders (if you dont do this, the install will fail!) cd; sudo chown daemon:daemon -R stack/joomla/; sudo find stack/joomla/ -type f -exec chmod 0644 {} ; sudo find stack/joomla/ -type d -exec chmod 0755 {} ;
Run the install process
To be honest, this is why I switched to using a LAMP server. The whole load process becomes far more straightforward.
— Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2002633257, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6MH744DK6CH7LMPYB3YYYHZDAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGYZTGMRVG4. You are receiving this because you authored the thread.
markrids
commented
6 months ago I couldn't load files direct to the joomla folder.
Hence it was two stages:
jotamartos
commented
6 months ago Hi both,
@markrids, you are using an old Bitnami Joomla version where the directory structure is different, but your steps seem correct, @jlibasci just need to use the correct path (/opt/bitnami/joomla directory).
If the Akeeba plugin takes a backup of all the Joomla's files, you can just rename the current directory, and replace it with the backup you took. Remember to set the permissions to bitnami/daemon and 775, 664 for the app to work properly.
As bitnami has a number of symlink directories and protected directories there are some complexities that just need to be documented.
All app files are inside the /opt/bitnami/joomla directory, but some files are symlinked to /bitnami/joomla. If you have problems with them, you can recover those files by removing the symlink and moving the files with mv.
markrids
commented
6 months ago Hi jotamartos,
I just tried this with a new instance using the 5.0.3 blueprint.
So, I uploaded the archive & moved it to the joomla folder, where I changed the ownership & unzipped it, overwriting the existing folder structure.
However, I had to set the permissions to daemon/daemon (not bitnami/daemon) to allow the installation to go ahead. The restoration script threw an error if I set permissions to bitnami/daemon: 'Neither your session save path in your server's php.ini not the installation/tmp directory is writeable. One of them must be writable for the installation to continue.'. I assume that's because the browser runs as 'daemon', not 'bitnami'.
Setting to daemon/daemon produced a flawless restoration.
Cheers, Mark
jlibasci
commented
6 months ago Ok I have started to document this so people can have a quick reference
Upgrade all components to the latest and greatest Match the version between your copy of joomla and the one offered by lightsail bitnami Create a new instance of joomla lightsail In AWS go to manage then networking then attach a static IP address to your install Purchase and download FileZilla Pro Download SSH key to connect to your site with the public ip address using SSH and FileZillaPro Username is bitnami to connect and select logon type key file and select the SSH key you downloaded Download the configuration.php from folder bitnami/joomla (this contains db info you will need later) Copy your kickstarter.php and your jpa backup file to /home/bitnami (now would be a good time to rename your kickstarter.php to a new a name which is required by akeeba the name just needs to be unique. Go back to the AWS services area and click the Connect using SSH to create a SSH connection First step is retrieve the DB password using the command - sudo cat /home/bitnami/bitnami_credentials save this password off to use during the install Next you need to move the your renamed kickstarter.php and your backupfile.jpa and change permissions on the jpa file. Do that performing the following commands sudo mv yourbackup.jpa stack/joomla/yourbackup.jpa; sudo mv renamedkickstarter.php stack/joomla/renamedkickstarter.php; cd stack/joomla; sudo chown daemon:daemon yourbackup.jpa;
On Mar 18, 2024, at 4:14 AM, Mark Ridsdale @.***> wrote:
Hi jotamartos,
I just tried this with a new instance using the 5.0.3 blueprint.
So, I uploaded the archive & moved it to the joomla folder, where I changed the ownership & unzipped it, overwriting the existing folder structure.
However, I had to set the permissions to daemon/daemon (not bitnami/daemon) to allow the installation to go ahead. The restoration script threw an error if I set permissions to bitnami/daemon: 'Neither your session save path in your server's php.ini not the installation/tmp directory is writeable. One of them must be writable for the installation to continue.'. I assume that's because the browser runs as 'daemon', not 'bitnami'.
Setting to daemon/daemon produced a flawless restoration.
Cheers, Mark
— Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2003278875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6NM27EV56GJEY3TBMDYY2V6JAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGI3TQOBXGU. You are receiving this because you were mentioned.
jlibasci
commented
6 months ago I am stuck with Joomla connecting the DB during the restore I have retrieved the following information from the old configuration file
public $host = ‘x.x.x.x:3306';
public $user = 'bn_joomla';
public $password = ‘I am using the password from the command sudo cat /home/bitnami/bitnami_credentials';
public $db = 'bitnami_joomla';
public $dbprefix = 'jos_'; When I enter this in the screen for the Akeeba restore it does not appear to work
On Mar 18, 2024, at 4:14 AM, Mark Ridsdale @.***> wrote:
Hi jotamartos,
I just tried this with a new instance using the 5.0.3 blueprint.
So, I uploaded the archive & moved it to the joomla folder, where I changed the ownership & unzipped it, overwriting the existing folder structure.
However, I had to set the permissions to daemon/daemon (not bitnami/daemon) to allow the installation to go ahead. The restoration script threw an error if I set permissions to bitnami/daemon: 'Neither your session save path in your server's php.ini not the installation/tmp directory is writeable. One of them must be writable for the installation to continue.'. I assume that's because the browser runs as 'daemon', not 'bitnami'.
Setting to daemon/daemon produced a flawless restoration.
Cheers, Mark
— Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2003278875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6NM27EV56GJEY3TBMDYY2V6JAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGI3TQOBXGU. You are receiving this because you were mentioned.

markrids
commented
6 months ago Use host of 'localhost'On 18 Mar 2024 15:39, jlibasci @.***> wrote: I am stuck with Joomla connecting the DB during the restore I have retrieved the following information from the old configuration file
public $host = ‘x.x.x.x:3306';
public $user = 'bn_joomla';
public $password = ‘I am using the password from the command sudo cat /home/bitnami/bitnami_credentials';
public $db = 'bitnami_joomla';
public $dbprefix = 'jos_'; When I enter this in the screen for the Akeeba restore it does not appear to work
On Mar 18, 2024, at 4:14 AM, Mark Ridsdale @.***> wrote:
Hi jotamartos,
I just tried this with a new instance using the 5.0.3 blueprint.
So, I uploaded the archive & moved it to the joomla folder, where I changed the ownership & unzipped it, overwriting the existing folder structure.
However, I had to set the permissions to daemon/daemon (not bitnami/daemon) to allow the installation to go ahead. The restoration script threw an error if I set permissions to bitnami/daemon: 'Neither your session save path in your server's php.ini not the installation/tmp directory is writeable. One of them must be writable for the installation to continue.'. I assume that's because the browser runs as 'daemon', not 'bitnami'.
Setting to daemon/daemon produced a flawless restoration.
Cheers,
Mark
—
Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2003278875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6NM27EV56GJEY3TBMDYY2V6JAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGI3TQOBXGU.
You are receiving this because you were mentioned.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
markrids
commented
6 months ago Sorry. Host is localhost, and User is root.Regards,Mark RidsdaleWelsh Fencinghttps://fencing.cymruOn 18 Mar 2024 15:56, Mark Ridsdale @.> wrote:Use host of 'localhost'On 18 Mar 2024 15:39, jlibasci @.> wrote: I am stuck with Joomla connecting the DB during the restore I have retrieved the following information from the old configuration file
public $host = ‘x.x.x.x:3306';
public $user = 'bn_joomla';
public $password = ‘I am using the password from the command sudo cat /home/bitnami/bitnami_credentials';
public $db = 'bitnami_joomla';
public $dbprefix = 'jos_'; When I enter this in the screen for the Akeeba restore it does not appear to work
On Mar 18, 2024, at 4:14 AM, Mark Ridsdale @.***> wrote:
Hi jotamartos,
I just tried this with a new instance using the 5.0.3 blueprint.
So, I uploaded the archive & moved it to the joomla folder, where I changed the ownership & unzipped it, overwriting the existing folder structure.
However, I had to set the permissions to daemon/daemon (not bitnami/daemon) to allow the installation to go ahead. The restoration script threw an error if I set permissions to bitnami/daemon: 'Neither your session save path in your server's php.ini not the installation/tmp directory is writeable. One of them must be writable for the installation to continue.'. I assume that's because the browser runs as 'daemon', not 'bitnami'.
Setting to daemon/daemon produced a flawless restoration.
Cheers,
Mark
—
Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2003278875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6NM27EV56GJEY3TBMDYY2V6JAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGI3TQOBXGU.
You are receiving this because you were mentioned.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
jlibasci
commented
6 months ago Ok that worked here is the guide for anyone else in the future
Migrating a Joomla Site to AWS Lightsail Bitnami
Moving your Joomla site to AWS Lightsail Bitnami requires careful steps to ensure a smooth transition. Follow these instructions meticulously to successfully migrate your Joomla site.
Begin by setting up a new instance of Joomla on AWS Lightsail. Note down the Joomla version you're installing.
Ensure your current Joomla site is upgraded to the same version as the Joomla Lightsail instance.
In AWS, navigate to "Manage your Lightsail instance," then go to "Networking" and attach a static IP address to your installation.
Obtain FileZilla Pro, a powerful FTP client, to facilitate file transfer.
From AWS, download the SSH key associated with your Lightsail instance. This key will be used to connect to your site via SSH using FileZilla Pro.
Using FileZilla Pro, connect to your site using the public IP address, username "bitnami," and select the SSH key you downloaded for authentication.
Locate and download the configuration.php file from the folder bitnami/joomla. This file contains essential database information needed later.
Copy your kickstarter.php and your Joomla backup file to /home/bitnami directory. Rename kickstarter.php to ensure its uniqueness.
Return to AWS services and click "Connect using SSH" to establish an SSH connection to your instance.
Use the command sudo cat /home/bitnami/bitnami_credentials to retrieve the DB password and save it for later use during the installation process.
Move your renamed kickstarter.php and backup file using the following commands:
bash Copy code sudo mv yourbackup.jpa stack/joomla/yourbackup.jpa sudo mv renamedkickstarter.php stack/joomla/renamedkickstarter.php cd stack/joomla sudo chown daemon:daemon yourbackup.jpa
Open a browser and navigate to your static IP address along with the name of your renamed kickstarter.php file (e.g., https://1.1.1.1/kickstarter.php).
Follow the Akeeba restore process using the following information:
DB Server: localhost DB Username: root DB Password: Retrieved from sudo cat /home/bitnami/bitnami_credentials DB Name: Use the dbname from the old configuration.php (likely bitnamijoomla) DB Prefix: jos (from configuration.php)
As part of the Akeeba restore process, reset your superadmin login credentials.
By following these steps diligently, you can effectively migrate your Joomla site to AWS Lightsail Bitnami, ensuring minimal downtime and a seamless transition.
On Mar 18, 2024, at 12:27 PM, Mark Ridsdale @.***> wrote:
Sorry. Host is localhost, and User is root.Regards,Mark RidsdaleWelsh Fencinghttps://fencing.cymruOn 18 Mar 2024 15:56, Mark Ridsdale @.> wrote:Use host of 'localhost'On 18 Mar 2024 15:39, jlibasci @.> wrote: I am stuck with Joomla connecting the DB during the restore I have retrieved the following information from the old configuration file
public $host = ‘x.x.x.x:3306';
public $user = 'bn_joomla';
public $password = ‘I am using the password from the command sudo cat /home/bitnami/bitnami_credentials';
public $db = 'bitnami_joomla';
public $dbprefix = 'jos_';
When I enter this in the screen for the Akeeba restore it does not appear to work
On Mar 18, 2024, at 4:14 AM, Mark Ridsdale @.***> wrote:
Hi jotamartos,
I just tried this with a new instance using the 5.0.3 blueprint.
So, I uploaded the archive & moved it to the joomla folder, where I changed the ownership & unzipped it, overwriting the existing folder structure.
However, I had to set the permissions to daemon/daemon (not bitnami/daemon) to allow the installation to go ahead. The restoration script threw an error if I set permissions to bitnami/daemon: 'Neither your session save path in your server's php.ini not the installation/tmp directory is writeable. One of them must be writable for the installation to continue.'. I assume that's because the browser runs as 'daemon', not 'bitnami'.
Setting to daemon/daemon produced a flawless restoration.
Cheers,
Mark
—
Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2003278875, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6NM27EV56GJEY3TBMDYY2V6JAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGI3TQOBXGU.
You are receiving this because you were mentioned.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***> — Reply to this email directly, view it on GitHub https://github.com/bitnami/vms/issues/1429#issuecomment-2004523690, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARX6N6KWBX3DY7BNNB6LUHTYY4PYFAVCNFSM6AAAAABEDZ23DGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGUZDGNRZGA. You are receiving this because you were mentioned.
jotamartos
commented
6 months ago Thanks for the guide. It'll be useful for others
Regarding the configuration to use
public $host = ‘x.x.x.x:3306'; public $user = 'bn_joomla'; public $password = ‘I am using the password from the command sudo cat /home/bitnami/bitnami_credentials'; public $db = 'bitnamijoomla'; public $dbprefix = 'jos';
and
DB Server: localhost DB Username: root DB Password: Retrieved from sudo cat /home/bitnami/bitnami_credentials DB Name: Use the dbname from the old configuration.php (likely bitnamijoomla) DB Prefix: jos (from configuration.php)
instead of using root and the password you have in the bitnami_credentials file, you can use the user and password that is set in the configuration file of the new instance you launch. That will make the deployment more secure as the application will use the specific user/password that was created for it.
github-actions[bot]
commented
6 months ago This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
github-actions[bot]
commented
5 months ago Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami - Joomla 4.4
What is the problem this feature will solve?
I can't figure out how to restore a akeeba backup to move a site to AWS bitnami. First challenge is where to put the kickstarter.php (without it being erased)
What is the feature you are proposing to solve the problem?
Might be documentation or a feature but moving Joomla sites to bitnami is huge market -
What alternatives have you considered?
I put the kickstarter.php in the temp directory