SSH Key Already Added

### **1. Check if the Key is Already in Use**
– If you previously added the SSH key to another account (e.g., on GitHub, Bitbucket, GitLab), remove it from the old account before adding it to a new one.

### **2. Generate a New SSH Key (If Needed)**
If you don’t want to remove the existing key from another account, generate a new SSH key and use it:

ssh-keygen -t ed25519 -C "your-email@example.com"

– When prompted for a filename, save it with a new name (e.g., `id_ed25519_new`).
– Then, add it to your SSH agent:

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519_new

– Finally, add the new public key (`~/.ssh/id_ed25519_new.pub`) to your Git provider.

### **3. Check Which Key is Being Used**
If you're unsure which SSH key is in use, check with:

ssh -T git@github.com

or

ssh -T git@bitbucket.org

### **4. Remove and Re-add the SSH Key**
If the key is already in your SSH agent but isn’t working, remove and re-add it:

ssh-add -D  # Removes all SSH keys
ssh-add ~/.ssh/id_rsa  # Or replace with your correct key file

Let me know if you need help with a specific platform (GitHub, Bitbucket, GitLab, etc.). 🚀

### **Possible Causes & Fixes**

#### **1. Check Directory Permissions**
If you're trying to clone the repository inside a directory where you don’t have write permissions, change the permissions or use a different directory.

– Check the current directory’s permissions:

ls -ld .

– If it says **root** or another user owns it, you may not have permission to write there.

– Change to a writable directory (e.g., `home` or `Documents`):

cd ~/Documents  # Or another directory where you have write permissions
  git clone git@bitbucket.org:openeratech/frontend.git

– If you need to fix permissions, you can use:

sudo chown -R $USER:$USER .

—

#### **2. Check SSH Key Authentication**
If the directory permissions are correct, but you still face issues, your SSH key might not be properly configured.

– Test SSH connection to Bitbucket:

ssh -T git@bitbucket.org

– If you see **"Permission denied"**, your SSH key might not be added to Bitbucket.

– Add the SSH key:

ssh-add ~/.ssh/id_rsa  # Replace with your SSH key if it's different

– If you haven’t added your SSH key to Bitbucket, copy it and add it to **Bitbucket → Personal Settings → SSH Keys**:

cat ~/.ssh/id_rsa.pub

—

#### **3. Run Git with `sudo` (If Necessary)**
If you are in a system directory where only `root` has permission (not recommended), you may need to use:

sudo git clone git@bitbucket.org:openeratech/frontend.git

But it’s better to **change to a writable directory** instead of using `sudo`.

—

#### **4. Ensure You Have Disk Space**
Check if your disk is full:

df -h

If your system storage is full, free up space before cloning.

—

### **Final Steps**
Try cloning again in a different writable directory:

cd ~
git clone git@bitbucket.org:openeratech/frontend.git

Let me know if you still face issues! 🚀

Please make sure you have the correct access rights
and the repository exists.

—

### **1. Verify SSH Key Setup**
Run the following command to check if your SSH key is added to the SSH agent:

ssh-add -l

– If it shows **"The agent has no identities"**, you need to add your key.

—

### **2. Manually Add SSH Key**
Try adding your SSH key manually:

ssh-add ~/.ssh/id_rsa  # Replace with your actual key if different

If you’re unsure whether the key exists, check:

ls -la ~/.ssh/

– The default key file should be **id_rsa** or **id_ed25519**. If missing, generate a new SSH key.

—

### **3. Check If the Key is Added to Bitbucket**
Get your public SSH key:

cat ~/.ssh/id_rsa.pub  # Or id_ed25519.pub if using ED25519

Copy the output and **add it to your Bitbucket account**:
1. Go to [Bitbucket SSH Settings](https://bitbucket.org/account/settings/ssh-keys/)
2. Click **"Add Key"**, paste the copied key, and save.

—

### **4. Test SSH Connection**
Run this command to verify SSH authentication with Bitbucket:

ssh -T git@bitbucket.org

– If successful, you should see:

authenticated via ssh key.
  You can use git to connect to Bitbucket.

– If it still says **Permission denied (publickey)**, ensure that you are using the correct key.

—

### **5. Force SSH to Use the Correct Key**
If you have multiple SSH keys, create or modify the SSH config file:

nano ~/.ssh/config

Add the following:

Host bitbucket.org
  IdentityFile ~/.ssh/id_rsa  # Change to your correct key if different
  User git

Save and exit (`CTRL + X`, then `Y`, then `Enter`).

Then restart the SSH agent:

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_rsa

Try cloning again:

git clone git@bitbucket.org:openeratech/frontend.git

—

### **6. If Running as Root**
You're running this inside `/var/www` as **root**. Check if your SSH key is available to the root user:

sudo ls -la /root/.ssh/

If your SSH key is missing, copy it from your regular user:

sudo cp -r ~/.ssh /root/
sudo chown -R root:root /root/.ssh

Then, try cloning again.

—

### **7. Use HTTPS as a Workaround**
If SSH continues failing, you can clone using HTTPS instead:

git clone https://bitbucket.org/openeratech/frontend.git

– It will ask for your Bitbucket username and app password (if 2FA is enabled, use an **App Password** instead of your account password).

—

Try these steps and let me know if you need more help! 🚀

You can use git to connect to Bitbucket. Shell access is disabled

—

### **1. Check Repository Permissions**
Make sure your Bitbucket account has **read access** to the repository:

1. Go to **Bitbucket → Repository Settings**.
2. Under **User and Group Access**, ensure your account has at least **Read** or **Write** permissions.
3. If using **a team workspace**, ensure your SSH key is added to the correct workspace.

—

### **2. Verify Git Remote URL**
Check if you're using the correct remote URL:

git remote -v

If it's incorrect, update it:

git remote set-url origin git@bitbucket.org:openeratech/frontend.git

Try cloning again:

git clone git@bitbucket.org:openeratech/frontend.git

—

### **3. Ensure You Have Write Access to `/var/www`**
Since you're trying to clone inside `/var/www`, **make sure the user has write permissions**:

ls -ld /var/www

If the owner is **root**, change ownership to `ubuntu`:

sudo chown -R ubuntu:ubuntu /var/www

Or try cloning in your home directory to test:

cd ~
git clone git@bitbucket.org:openeratech/frontend.git

If this works, then it's a **permission issue with `/var/www`**.

—

### **4. Try Cloning with `sudo`**
If permissions are strict and you must use `/var/www`, try:

sudo git clone git@bitbucket.org:openeratech/frontend.git

However, it's better to adjust permissions instead of using `sudo`.

—

### **5. Test SSH Key Explicitly**
If you have multiple SSH keys, force Git to use the correct one:

GIT_SSH_COMMAND="ssh -i ~/.ssh/id_rsa" git clone git@bitbucket.org:openeratech/frontend.git

(Change `id_rsa` if your key is different.)

—

Try these steps and let me know if it works! 🚀

Please make sure you have the correct access rights
and the repository exists.

—

## **1. Check Which User Owns the SSH Key**
You're trying to clone as `root`. However, your SSH key might be set up under the `ubuntu` user.

Run this to check if `root` has SSH keys:

ls -la /root/.ssh/

– If **`id_rsa` and `id_rsa.pub` (or `id_ed25519` and `id_ed25519.pub`)** exist, list the key:

cat /root/.ssh/id_rsa.pub

– If this key is **not** added to Bitbucket, add it in **Bitbucket → Personal Settings → SSH Keys**.

### **If `/root/.ssh/` is empty:**
It means SSH keys are configured only for the `ubuntu` user. Run:

ls -la /home/ubuntu/.ssh/

If keys exist there, **copy them to `root`**:

sudo cp -r /home/ubuntu/.ssh /root/
sudo chown -R root:root /root/.ssh

Then try cloning again.

—

## **2. Force Git to Use the Correct Key**
If multiple keys exist, force Git to use the correct one:

GIT_SSH_COMMAND="ssh -i /root/.ssh/id_rsa" git clone git@bitbucket.org:openeratech/frontend.git

—

## **3. Try Cloning as `ubuntu` Instead of `root`**
Since SSH is authenticated as `ubuntu`, you should **avoid using `root`** for cloning. Instead, switch to the `ubuntu` user:

su - ubuntu
cd /var/www
git clone git@bitbucket.org:openeratech/frontend.git

If you **must** use `/var/www`, give `ubuntu` write access:

sudo chown -R ubuntu:ubuntu /var/www

Then try cloning again as `ubuntu`.

—

## **4. Add SSH Key to the SSH Agent**
If cloning still fails, ensure the SSH key is added:

eval "$(ssh-agent -s)"
ssh-add /root/.ssh/id_rsa  # Or your correct SSH key

Then test SSH again:

ssh -T git@bitbucket.org

If it authenticates, retry:

git clone git@bitbucket.org:openeratech/frontend.git

—

## **5. Debug SSH Authentication**
Run:

ssh -vT git@bitbucket.org

This will show **which SSH key** is being used. If it's not using `/root/.ssh/id_rsa`, you may need to configure SSH manually.

Modify **`/root/.ssh/config`** (or `/home/ubuntu/.ssh/config` if using `ubuntu`):

nano ~/.ssh/config

Add:

Host bitbucket.org
  IdentityFile ~/.ssh/id_rsa  # Change if your key is different
  User git

Save and exit (`CTRL + X`, then `Y`, then Enter).

Then restart SSH agent:

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_rsa

Try cloning again.

—

## **6. Use HTTPS Instead of SSH (Alternative)**
If SSH still fails, use HTTPS instead:

git clone https://bitbucket.org/openeratech/frontend.git

This will prompt for your **Bitbucket username** and **App Password** (not your normal password if 2FA is enabled).

—

### **Final Steps**
– **If cloning works as `ubuntu` but not as `root`**, avoid using `root` for Git operations.
– **If using multiple SSH keys**, ensure the correct one is being used with `GIT_SSH_COMMAND` or `~/.ssh/config`.
– **If SSH fails, try HTTPS cloning.**

Let me know if you need further assistance! 🚀

### **Solution: Fix Folder Permissions**

#### **1. Check the Owner of `/var/www`**
Run the following command:

ls -ld /var/www

This will show the owner and permissions of the `/var/www` directory. If it is owned by `root`, your `ubuntu` user does not have write permissions.

—

#### **2. Change Ownership to the `ubuntu` User**
Since you're using the `ubuntu` user, give it ownership of `/var/www`:

sudo chown -R ubuntu:ubuntu /var/www

Then, try cloning again:

git clone git@bitbucket.org:openeratech/frontend.git

—

#### **3. (Alternative) Grant Write Permissions**
If you don't want to change ownership but just allow writing, set write permissions:

sudo chmod -R 775 /var/www

or give full permissions (not recommended for production):

sudo chmod -R 777 /var/www

Then, try cloning again.

—

#### **4. (If You Must Use `root`) Clone as `root`**
If you must clone into `/var/www` without changing permissions, switch to `root`:

sudo su
cd /var/www
git clone git@bitbucket.org:openeratech/frontend.git

But it's better to keep the `ubuntu` user for security reasons.

—

### **Final Check**
Try creating a test file to confirm permissions:

touch /var/www/testfile

If you see **"Permission denied"**, the folder still has restrictive permissions.

—

After fixing the permissions, retry cloning. Let me know if you need further help! 🚀

—

### **1. Check If Your Web Server Is Running**
Since you're using **Apache** on AWS EC2, check its status:

sudo systemctl status apache2

or if using **Nginx**:

sudo systemctl status nginx

– If it’s not running, start it with:

sudo systemctl start apache2  # for Apache
  sudo systemctl start nginx  # for Nginx

– To make it start automatically on boot:

sudo systemctl enable apache2

—

### **2. Find Your EC2 Public IP**
Get your public IP address with:

curl ifconfig.me

or check the AWS **EC2 Dashboard → Instances**.

You can then access your site by opening:

http://YOUR_PUBLIC_IP/

If using a domain, make sure it points to your EC2 instance.

—

### **3. Ensure Firewall Rules Allow HTTP/HTTPS**
Check if your firewall allows **port 80 (HTTP) and 443 (HTTPS)**:

sudo ufw status

If **inactive**, enable it:

sudo ufw enable

Allow necessary ports:

sudo ufw allow 80
sudo ufw allow 443
sudo ufw allow 22  # (For SSH)

Reload the firewall:

sudo ufw reload

For AWS Security Group settings:
1. Go to **AWS EC2 → Security Groups**.
2. Edit **Inbound Rules**.
3. Ensure rules exist for:
– **HTTP (80)** → Anywhere (0.0.0.0/0)
– **HTTPS (443)** → Anywhere (0.0.0.0/0)

—

### **4. Check If Your Site Files Are in `/var/www/html/`**
Navigate to the web root:

cd /var/www/html/
ls -l

If your site files are missing, move your Laravel/Vue or WordPress files there.

For Laravel:

sudo mv /var/www/share/public /var/www/html

Then set correct permissions:

sudo chown -R www-data:www-data /var/www/html
sudo chmod -R 755 /var/www/html

—

### **5. Restart the Web Server**

sudo systemctl restart apache2

Then open your browser and visit:

http://YOUR_PUBLIC_IP/

If you’re using SSL (Cloudflare/Let’s Encrypt), try:

https://YOUR_DOMAIN/

—

#### **Still Not Working?**
– Run:

sudo tail -f /var/log/apache2/error.log

Check for errors.
– Ensure DNS records point to your EC2 instance if using a domain.

Let me know what you see! 🚀

—

### **1. Create a Virtual Host Configuration File**
Run the following command to create a new site configuration file:

sudo nano /etc/apache2/sites-available/yourdomain.conf

Replace `yourdomain` with your actual domain name or project name.

—

### **2. Add Virtual Host Configuration**
Paste the following content inside the file:

<VirtualHost *:80>
    ServerAdmin admin@yourdomain.com
    ServerName yourdomain.com
    ServerAlias www.yourdomain.com

    DocumentRoot /var/www/yourproject/public

    <Directory /var/www/yourproject/public>
        Options Indexes FollowSymLinks
        AllowOverride All
        Require all granted
    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

– **Replace `yourdomain.com`** with your actual domain or public IP.
– **Set `DocumentRoot`** to the correct location of your Laravel, WordPress, or Vue project.
– For **Laravel**, make sure to point to the `public` folder.
– **If using SSL**, later you'll need to set up Let's Encrypt or Cloudflare.

Save and exit: **`CTRL + X`, then `Y`, then ENTER`**.

—

### **3. Enable the Site**
Activate the new configuration with:

sudo a2ensite yourdomain.conf

Disable the default Apache site (optional but recommended):

sudo a2dissite 000-default.conf

Then, restart Apache:

sudo systemctl restart apache2

—

### **4. Set File Permissions**
Ensure Apache has the correct ownership:

sudo chown -R www-data:www-data /var/www/yourproject
sudo chmod -R 755 /var/www/yourproject

—

### **5. Enable `.htaccess` (for Laravel/WordPress)**
If your site requires `.htaccess`, make sure **mod_rewrite** is enabled:

sudo a2enmod rewrite
sudo systemctl restart apache2

—

### **6. Verify Your Configuration**
Check if Apache is running without errors:

sudo apachectl configtest

If it says:

Syntax OK

You're good to go.

—

### **7. Access Your Site**
– If using a **domain**, update your **DNS records** to point to your EC2 instance.
– If using an **IP address**, visit:

http://your-public-ip/

—

### **8. (Optional) Enable SSL with Let's Encrypt**
If you have a domain and want **HTTPS**, install Let's Encrypt:

sudo apt install certbot python3-certbot-apache -y

Then, run:

sudo certbot --apache -d yourdomain.com -d www.yourdomain.com

This will automatically set up SSL.

—

### **Final Steps**
If your site is not working:
– Check Apache logs:

sudo tail -f /var/log/apache2/error.log

– Check if the firewall allows traffic:

sudo ufw allow 80
  sudo ufw allow 443
  sudo ufw enable

– Ensure the DNS is pointing to your EC2 IP.

Let me know if you need more help! 🚀