Check Home Folder Space

df -h ~

Explanation of the command:
– `df`: Displays disk space usage.
– `-h`: Shows the output in a human-readable format (e.g., GB, MB).
– `~`: Refers to the home directory of the current user.

The output will show details like:
– Filesystem
– Size
– Used
– Available
– Use% (percentage of space used)
– Mounted on

If you want to check the space for the entire system, use:

df -h

For more detailed usage by directories in the home folder, you can use:

du -sh ~/*

This will display the space used by each directory within your home folder.

### To Check Disk Space Usage for the Filesystem

df -h /home/admin1

This command provides:
– Total size of the filesystem where `/home/admin1` resides.
– Used space.
– Available space.
– Percentage of usage.

—

### To Check Space Used by Files in `/home/admin1`
If you want to see the space used by individual files or folders within `/home/admin1`:

du -sh /home/admin1/*

This command displays the size of each file and folder in `/home/admin1`.

—

### To Summarize Total Usage for `/home/admin1`
To get the total space used by the `/home/admin1` directory:

du -sh /home/admin1

This will give a single value representing the total size of the `admin1` directory.

—

### 1. **Navigate to the `.cache` Directory**
If the `.cache` directory is in your home directory (e.g., `/home/admin1/.cache`), navigate to it:

cd /home/admin1/.cache

—

### 2. **Delete the Contents of `.cache`**
Run the following command to delete all files and folders inside the `.cache` directory:

rm -rf /home/admin1/.cache/*

– `rm`: Removes files.
– `-r`: Deletes directories and their contents recursively.
– `-f`: Forces deletion without prompting for confirmation.
– `*`: Matches all files and folders inside `.cache`.

—

### 3. **Confirm the Directory is Empty**
To verify that the `.cache` directory is now empty:

ls -la /home/admin1/.cache

—

### 4. **Optional: Delete Hidden Files**
If there are hidden files (starting with a `.`), include them as well:

rm -rf /home/admin1/.cache/.* 2>/dev/null

The `2>/dev/null` suppresses error messages if no hidden files are present.

—

### 5. **Restart Applications (Optional)**
Some applications may recreate their cache when restarted. Restart any affected applications if needed.

> ⚠️ **Caution:** Deleting `.cache` content can remove temporary data for certain applications, but it is generally safe to do so. Always double-check if there is critical data before proceeding.

—

### 1. **Locate the Android SDK Installation Path**
The Android SDK is typically installed in one of these default directories:
– `$HOME/Android/Sdk` (e.g., `/home/admin1/Android/Sdk`)
– `/usr/lib/android-sdk`

If you're unsure of the location, you can check the `ANDROID_HOME` or `ANDROID_SDK_ROOT` environment variables:

echo $ANDROID_HOME
echo $ANDROID_SDK_ROOT

—

### 2. **Delete the Android SDK Directory**
Once you identify the installation directory, delete it using the `rm` command. Replace “ with the actual path.

For example:

rm -rf ~/Android/Sdk

Or if it is located elsewhere:

sudo rm -rf /usr/lib/android-sdk

—

### 3. **Remove Environment Variables**
Check and remove any environment variables related to the Android SDK:

– Open the shell configuration file (depending on your shell):
– Bash: `~/.bashrc`
– Zsh: `~/.zshrc`
– Fish: `~/.config/fish/config.fish`

– Search for lines defining `ANDROID_HOME`, `ANDROID_SDK_ROOT`, or paths pointing to the SDK, and delete them. For example:

export ANDROID_HOME=~/Android/Sdk
  export ANDROID_SDK_ROOT=~/Android/Sdk
  export PATH=$ANDROID_HOME/emulator:$ANDROID_HOME/tools:$ANDROID_HOME/tools/bin:$ANDROID_HOME/platform-tools:$PATH

– Save the file and reload it:

source ~/.bashrc  # or ~/.zshrc, depending on your shell

—

### 4. **Uninstall Android Studio (Optional)**
If you're using Android Studio and wish to remove it too:
– If installed via a package manager (e.g., Snap):

sudo snap remove android-studio

– If installed manually, delete the directory where it is installed.

—

### 5. **Clean Up**
You can remove residual files (optional):

rm -rf ~/.android
rm -rf ~/.gradle

This ensures all Android-related configurations and cache are removed.

—

### **If Installed via Snap**
1. Run the following command to remove Android Studio:

sudo snap remove android-studio

—

### **If Installed Manually**
1. Locate the installation directory:
– The default directory is usually in `~/android-studio` or `/opt/android-studio`.

2. Delete the installation directory:

rm -rf ~/android-studio

Or, if it’s in `/opt`:

sudo rm -rf /opt/android-studio

—

### **Remove Configuration and Cache Files**
1. Delete Android Studio's configuration and cache files located in the home directory:

rm -rf ~/.AndroidStudio*
   rm -rf ~/.android
   rm -rf ~/.gradle
   rm -rf ~/Android

—

### **Remove Environment Variables**
1. Open your shell configuration file:
– For Bash: `~/.bashrc`
– For Zsh: `~/.zshrc`
– For Fish: `~/.config/fish/config.fish`

2. Search for lines that set `ANDROID_HOME`, `ANDROID_SDK_ROOT`, or any Android-related paths, and delete them.

3. Reload the shell configuration:

source ~/.bashrc  # or ~/.zshrc, depending on your shell

—

### **Uninstall Dependencies (Optional)**
If you want to remove dependencies like Java JDK, you can uninstall them using:

sudo apt remove openjdk-* -y
sudo apt autoremove -y

—

### **Verify Removal**
Check if Android Studio is completely removed:
1. Ensure no installation directories exist:

ls ~/android-studio
   ls /opt/android-studio

2. Check environment variables:

echo $ANDROID_HOME
   echo $ANDROID_SDK_ROOT

If everything is removed, Android Studio has been successfully uninstalled.

—

### **1. Remove the `.config` Directory**
If you want to remove all configurations in your home directory's `.config` folder:

rm -rf ~/.config

**Note:** This will delete configuration files for applications. Use it only if you are sure you no longer need them.

—

### **2. Clear Cache Files**
The cache files are usually located in the `.cache` directory in your home folder. To remove them:

rm -rf ~/.cache

—

### **3. Find and Remove Unused Files**
You can identify and remove unused or large files:

#### **3.1 List Large Files**
Find large files in your home directory:

find ~ -type f -size +100M -exec ls -lh {} ;

You can adjust `+100M` to a smaller size (e.g., `+10M`) to find moderately large files.

#### **3.2 Remove Specific Unused Files**
If you find files that are no longer needed, remove them:

rm /path/to/file

#### **3.3 Remove Temporary Files**
Clear temporary files:

sudo rm -rf /tmp/*

—

### **4. Use Disk Cleanup Tools**
You can use tools to automate cleaning tasks:

#### **4.1 Using `apt` for Package Cleanup**
For systems using `apt` (e.g., Ubuntu/Debian):

sudo apt autoremove -y
sudo apt autoclean
sudo apt clean

#### **4.2 Using `bleachbit`**
Install and run `bleachbit` for advanced cleanup:

sudo apt install bleachbit
bleachbit

This provides an interactive GUI to select what you want to clean.

—

### **5. Verify Free Disk Space**
After cleanup, check your available disk space:

df -h

—

### **Proceed with Caution**
Deleting `.config` and `.cache` can reset application settings and remove stored data. Backup critical files before proceeding:

cp -r ~/.config ~/backup-config
cp -r ~/.cache ~/backup-cache

Here’s how to resolve this issue:

—

### **1. Check the Status of DDEV Projects**
Run the following command to list all DDEV projects and their statuses:

ddev list

Identify the `all4cloud` project and confirm its status. If it’s in an `exited` or problematic state, proceed with the steps below.

—

### **2. Stop and Remove the Project**
To clean up the containers and reset the project:

#### **Stop the Project**

ddev stop all4cloud

#### **Remove the Project**
This removes containers and other resources associated with the project:

ddev delete all4cloud

#### **Clean Docker Containers**
Sometimes, DDEV does not remove all containers. Use Docker directly:

docker ps -a | grep all4cloud

If you see exited containers, remove them:

docker rm <container_id>

—

### **3. Clean the DDEV Project Directory**
Navigate to the DDEV project directory and ensure there are no lingering files:

cd /home1/ddev-projects/all4cloud-wordpress-website

Check for DDEV configuration files and remove them if needed:

rm -rf .ddev

—

### **4. Restart Docker**
Sometimes, restarting Docker resolves container-related issues:

sudo systemctl restart docker

—

### **5. Recreate the Project**
Once everything is cleaned up, you can recreate and restart the project:
1. Navigate to the project directory:

cd /home1/ddev-projects/all4cloud-wordpress-website

2. Start DDEV:

ddev start

—

### **6. Additional Cleanup (If Required)**
If the issue persists, try these additional steps:
– Prune unused Docker resources:

docker system prune -f

– Rebuild the project:

ddev config
  ddev start

These steps should resolve the issue. Let me know if you encounter further problems!

Here’s how you can resolve it step by step:

—

### **1. Unlist the Existing Project**
To remove the incorrect project root from DDEV's configuration, run:

ddev stop --unlist all4cloud

This will stop the project and remove it from DDEV's list of active projects.

—

### **2. Verify Project Directory**
Make sure you are in the correct directory where the project is located:

cd /home/admin1/ddev-projects/all4cloud-wordpress-website

If the project root should indeed be `/home/admin1/ddev-projects/all4cloud-wordpress-website`, proceed to the next step.

—

### **3. Reconfigure DDEV**
Reinitialize the DDEV configuration for the project:

ddev config

Follow the prompts to set up the project. Ensure the project root, type (e.g., WordPress), and other configurations are correct.

—

### **4. Start the Project**
After reconfiguration, start the project again:

ddev start

—

### **5. Clean Up Any Stale Containers (If Needed)**
If the issue persists, check for any stale containers associated with the project:

docker ps -a | grep all4cloud

Remove any containers related to the project:

docker rm -f <container_id>

—

### **6. Prune DDEV Global Configuration (If Needed)**
If the problem is still unresolved, you can manually edit the global DDEV configuration to remove the incorrect project reference:
1. Open the DDEV global configuration file:

nano ~/.ddev/global_config.yaml

2. Locate the `all4cloud` project and remove its entry.

3. Save and exit.

4. Restart DDEV:

ddev restart

—

### **7. Try Starting Again**
Return to the correct project directory and start the project:

cd /home/admin1/ddev-projects/all4cloud-wordpress-website
ddev start

—

These steps should resolve the issue. Let me know if you encounter further problems!

Here are the steps:

—

### **1. Navigate to the Correct Directory**
Ensure you are in the directory of the project:

cd /home/admin1/ddev-projects/all4cloud-wordpress-website

—

### **2. Reconfigure the DDEV Project**
Run the following command to reinitialize the DDEV configuration for the project:

ddev config

During the setup:
– Confirm the project type (e.g., WordPress).
– Ensure the project name is `all4cloud` or whatever name you prefer.

—

### **3. Start the Project**
After reconfiguring the project, start it:

ddev start

This will create and start the necessary Docker containers.

—

### **4. Cleanup Stale Containers (If Necessary)**
If you encounter further issues, there might be stale containers or networks. Clean them up:

docker system prune -f
docker network prune -f

—

### **5. Verify DDEV Project List**
Check if the project is properly listed:

ddev list

Ensure the `all4cloud` project is shown with the correct directory (`/home/admin1/ddev-projects/all4cloud-wordpress-website`).

—

### **6. Troubleshooting Persistent Issues**
If the problem persists:
– Check DDEV logs for more details:

ddev logs

– Reset the global DDEV state (last resort):

ddev poweroff
  rm -rf ~/.ddev
  ddev start

This process should fix the issue and get the project running again. Let me know if you face further challenges!

—

### **1. Free Up Space on Your Disk**
Docker images, containers, volumes, and networks can consume significant space. Clean up unused Docker resources:

#### **1.1 Remove Unused Images**
Remove dangling and unused images:

docker image prune -a -f

#### **1.2 Remove Unused Containers**
Remove stopped containers:

docker container prune -f

#### **1.3 Remove Unused Volumes**
Volumes can take up a lot of space:

docker volume prune -f

#### **1.4 Remove Unused Networks**

docker network prune -f

—

### **2. Increase Docker Disk Image Size**
If you're using Docker Desktop or a similar setup, you can increase the disk image size allocated to Docker.

#### **On Docker Desktop:**
1. Open **Docker Desktop**.
2. Go to **Settings** > **Resources** > **Advanced**.
3. Adjust the **Disk Image Size** slider to a higher value (e.g., 60–100 GB).
4. Click **Apply & Restart** to save the changes.

#### **On Linux with `dockerd`:**
1. Check where Docker stores its images:

docker info | grep "Docker Root Dir"

2. If the partition is full, consider moving Docker's root directory to a partition with more space:
– Stop Docker:

sudo systemctl stop docker

– Create a new directory (e.g., `/new-docker-storage`):

sudo mkdir /new-docker-storage

– Move existing data:

sudo rsync -aP /var/lib/docker/ /new-docker-storage

– Update Docker’s configuration:

sudo nano /etc/docker/daemon.json

Add or modify the following:

{
       "data-root": "/new-docker-storage"
     }

– Restart Docker:

sudo systemctl start docker

—

### **3. Verify Free Disk Space**
After cleanup and adjustments, check available disk space:

df -h

Ensure the partition hosting Docker has sufficient space.

—

### **4. Restart DDEV**
After resolving disk space issues, restart your DDEV project:

ddev restart

—

By following these steps, you should resolve the low disk space issue and ensure Docker can function without interruption. Let me know if you need further assistance!

### **1. Prepare the Database File**
Make sure you have your database dump file (e.g., `database.sql` or `database.gz`) ready to be imported. Place it in a location accessible from your terminal.

### **2. Navigate to Your DDEV Project Directory**
Change to your DDEV project directory:

cd /home/admin1/ddev-projects/all4cloud-wordpress-website

### **3. Import the Database**
You can import the database using the following command:

ddev import-db --src=/path/to/your/database.sql

If your database dump is compressed (e.g., `.gz`), you can use:

ddev import-db --src=/path/to/your/database.sql.gz

### **4. Verify the Import**
After the import process completes, you can check the status of your database:

ddev mysql

This command opens the MySQL command line interface for your DDEV project's database. You can run SQL queries to verify the tables and data are present.

### **5. Set Up Environment Variables (If Needed)**
If your project relies on environment variables for database connections (like in a WordPress setup), ensure they are set up correctly in your `.ddev/.env` file.

### **6. Restart the DDEV Project (If Necessary)**
If you encounter issues after the import, try restarting your DDEV project:

ddev restart

### **Note:**
If the database already exists and you want to drop it before importing, you can use:

ddev mysql -e "DROP DATABASE IF EXISTS your_database_name;"

Replace `your_database_name` with the actual name of your database.

### **Conclusion**
These steps should help you successfully import your database into your DDEV project. If you run into any errors or need further assistance, feel free to ask!

### **1. Check the DDEV Configuration**
Navigate to your DDEV project directory:

cd /home/admin1/ddev-projects/all4cloud-wordpress-website

Then, view the `.ddev/config.yaml` file:

cat .ddev/config.yaml

Look for the `db` section, which may include the database name.

### **2. Use the DDEV Command**
You can also retrieve the database name directly using the DDEV CLI. Run the following command:

ddev db describe

This command provides details about the database, including the name, user, and host.

### **3. Default Naming Convention**
By default, DDEV projects often follow this naming convention for the database:
– The database name is typically the same as the project name. For example, if your project is named `all4cloud`, the database name would likely be `db_all4cloud`.

### **4. MySQL Access**
If you have MySQL access to the database, you can also log in and check:

ddev mysql

Then run:

SHOW DATABASES;

This will list all databases associated with your DDEV project, allowing you to confirm the name.

### **Summary**
You can find the database name for your DDEV project in the `.ddev/config.yaml` file, through the `ddev db describe` command, or by checking directly in the MySQL interface after logging in with `ddev mysql`. Let me know if you need further assistance!

### **1. Install `libnss3-tools`**
Open your terminal and run the following command to install the `libnss3-tools` package, which includes `certutil`:

sudo apt update
sudo apt install libnss3-tools

### **2. Verify Installation**
After installation, you can verify that `certutil` is installed correctly by running:

certutil -version

This should display the version of `certutil`.

### **3. Install mkcert**
If you haven't installed `mkcert` yet, you can do so by following these steps:

#### **3.1. Install mkcert with Homebrew (if available)**
If you have Homebrew installed, you can use it to install `mkcert`:

brew install mkcert

#### **3.2. Manual Installation (if Homebrew is not available)**
You can also download `mkcert` manually:

# Download the latest mkcert binary
wget https://github.com/FiloSottile/mkcert/releases/latest/download/mkcert-linux-amd64 -O mkcert

# Move it to a directory in your PATH
sudo mv mkcert /usr/local/bin/

# Make it executable
sudo chmod +x /usr/local/bin/mkcert

### **4. Install Local CA**
Now that `certutil` and `mkcert` are installed, run the following command to set up the local Certificate Authority:

mkcert -install

### **5. Create Certificates**
You can now create certificates for your local development projects using:

mkcert example.com "*.example.com" localhost 127.0.0.1 ::1

Replace `example.com` with your desired domain names.

### **6. Verify mkcert Installation**
To ensure that `mkcert` is functioning correctly, you can list the created certificates:

mkcert -CAROOT

This command shows the path where `mkcert` stores its certificates.

### **Conclusion**
After completing these steps, `certutil` should be installed, and you should be able to use `mkcert` to create trusted SSL certificates for your local development environment. Let me know if you have any further questions or run into any issues!

Here's how to resolve this issue:

### **1. Ensure Browsers are Installed**
Make sure you have Firefox and/or Chrome/Chromium installed on your system. You can install them with the following commands if they are not already installed:

#### **For Firefox:**

sudo apt update
sudo apt install firefox

#### **For Chrome:**
To install Google Chrome, you need to download the `.deb` package from the official website:

wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install ./google-chrome-stable_current_amd64.deb

#### **For Chromium:**

sudo apt update
sudo apt install chromium-browser

### **2. Ensure Firefox is the Default Browser (Optional)**
If you prefer using Firefox and it is installed, you might want to set it as the default browser:

xdg-settings set default-web-browser firefox.desktop

### **3. Install mkcert in Firefox**
If Firefox is already installed, you may need to ensure that it can access the NSS database:

#### **3.1. Create a New Profile (Optional)**
If you are using a custom profile in Firefox, create a new default profile to see if that resolves the issue:
1. Open Firefox.
2. In the address bar, type `about:profiles`.
3. Create a new profile and set it as default.

#### **3.2. Run mkcert with Firefox**
After ensuring Firefox is installed, you can try running the `mkcert -install` command again:

mkcert -install

### **4. Check for Chrome/Chromium Security Database**
If you prefer using Chrome or Chromium, ensure they are installed and run the following command to find the path to their security databases. You can check their location with:

find ~/.config/google-chrome/ -name "Certificate*"
find ~/.config/chromium/ -name "Certificate*"

### **5. Manual Certificate Installation (If Necessary)**
If the above steps do not resolve the issue, you can manually add the certificates created by `mkcert` to your browser's certificate store:
– Open the certificate management in your browser (e.g., in Firefox, navigate to `about:preferences#privacy` > View Certificates).
– Import the `.pem` files generated by `mkcert` from the `mkcert` directory.

### **Conclusion**
After completing these steps, you should be able to run `mkcert -install` without errors. If you continue to encounter issues, please let me know!

### **1. Check Browser Profiles**
Sometimes, `mkcert` cannot find the security databases because it’s looking in the wrong profile. Make sure your browsers are set to use the default profile or check if multiple profiles exist.

#### **For Firefox:**
1. Open Firefox.
2. Type `about:profiles` in the address bar and press Enter.
3. Ensure that a default profile is set. If you have multiple profiles, try switching to the default one.

#### **For Chrome:**
1. Open Chrome.
2. Go to the address bar and type `chrome://version/`.
3. Check the "Profile Path" to see which profile is being used.

### **2. Check Permissions**
Ensure that `mkcert` has the necessary permissions to access the browser's configuration files. This is especially relevant if you are running in a restricted environment or have changed permissions.

### **3. Reinstall mkcert**
Try reinstalling `mkcert` to ensure it has proper access to the browser's databases:
1. Remove the existing installation:

sudo rm /usr/local/bin/mkcert

2. Reinstall it using the method you prefer (e.g., manually or with Homebrew).

### **4. Manually Install the Root CA in Firefox and Chrome**
If the automatic installation does not work, you can manually add the root CA created by `mkcert`:

#### **For Firefox:**
1. Find the root CA file:

mkcert -CAROOT

This will show you the path to the `rootCA.pem` file.

2. Open Firefox and navigate to `about:preferences#privacy`.
3. Click on "View Certificates" under the "Certificates" section.
4. Go to the "Authorities" tab and click on "Import."
5. Select the `rootCA.pem` file and check "Trust this CA to identify websites."

#### **For Chrome:**
1. Open Chrome and go to `chrome://settings`.
2. Scroll down and click on "Advanced."
3. Under the "Privacy and security" section, click on "Manage certificates."
4. Go to the "Authorities" tab and click "Import."
5. Select the `rootCA.pem` file and check "Trust this certificate for identifying websites."

### **5. Restart Your Browsers**
After performing the above steps, make sure to close and restart both browsers to ensure they recognize the new certificate settings.

### **6. Rerun mkcert -install**
After performing the steps above, try running the `mkcert -install` command again:

mkcert -install

### **Conclusion**
These steps should help you resolve the issue with `mkcert` and allow you to install the local CA successfully. If you still encounter problems, please let me know!

### **1. Remove Any Existing mkcert Installation**
First, ensure that there are no remnants of `mkcert`:

sudo rm /usr/local/bin/mkcert

### **2. Download and Install mkcert**
You can download and install `mkcert` manually using the following commands:

#### **2.1. Download mkcert**

wget https://github.com/FiloSottile/mkcert/releases/latest/download/mkcert-linux-amd64 -O mkcert

#### **2.2. Move mkcert to a Directory in Your PATH**

sudo mv mkcert /usr/local/bin/

#### **2.3. Make it Executable**

sudo chmod +x /usr/local/bin/mkcert

### **3. Install the Local CA**
Now that `mkcert` is installed, run the following command to set up the local Certificate Authority:

mkcert -install

### **4. Verify the Installation**
After running the installation, you can verify that `mkcert` is installed correctly:

mkcert -version

### **Conclusion**
By following these steps, you should have `mkcert` installed properly, and you should be able to run `mkcert -install` without errors. If you encounter any further issues, please let me know!

### Step-by-Step Installation of mkcert

1. **Open Your Terminal**:
Make sure you're in a terminal session where you can run commands.

2. **Download mkcert**:
Use `wget` to download the `mkcert` binary:

wget https://github.com/FiloSottile/mkcert/releases/latest/download/mkcert-linux-amd64 -O mkcert

3. **Move mkcert to the Correct Directory**:
Move the downloaded binary to `/usr/local/bin/`, which is a common directory for user-installed binaries:

sudo mv mkcert /usr/local/bin/

4. **Make mkcert Executable**:
Change the permissions to make the `mkcert` binary executable:

sudo chmod +x /usr/local/bin/mkcert

5. **Verify mkcert Installation**:
Check if `mkcert` is now installed correctly by running:

mkcert -version

6. **Install the Local CA**:
After confirming the installation, run:

mkcert -install

### Troubleshooting

If you still see "No such file or directory" after running the above commands, consider the following:

– **Check for Errors in Downloading**:
Ensure the `wget` command completed successfully without errors. You can check by looking at the output of the command.

– **Check if mkcert Exists**:
After running the `wget` command, you can check if the `mkcert` file exists in your current directory:

ls -l mkcert

If the file is not there, the download may have failed.

– **Use Curl as an Alternative**:
If `wget` is not working for you, you can try using `curl` instead:

curl -Lo mkcert https://github.com/FiloSottile/mkcert/releases/latest/download/mkcert-linux-amd64

### Final Step

Once you have verified that `mkcert` is installed and can be executed, you can proceed with your SSL certificate setup.

Let me know if you run into any issues or need further assistance!

### **1. Go to the Latest mkcert Release Page**
You can find the latest version of `mkcert` on its [GitHub Releases page](https://github.com/FiloSottile/mkcert/releases). Look for the latest version and note its version number.

### **2. Use the Updated Command**
To download the latest `mkcert` for Linux, use the following command (replace `latest` with the actual version number if necessary):

wget https://github.com/FiloSottile/mkcert/releases/latest/download/mkcert-linux-amd64 -O mkcert

### **3. Move and Install mkcert**
After downloading, continue with these steps:

sudo mv mkcert /usr/local/bin/
sudo chmod +x /usr/local/bin/mkcert

### **4. Verify Installation**
Check if `mkcert` was installed correctly:

mkcert -version

### **5. Install the Local CA**
Finally, run the command to install the local CA:

mkcert -install

### **Alternative Download Method**
If you continue having issues with the `wget` command, you can also download the file using your web browser by visiting the [GitHub Releases page](https://github.com/FiloSottile/mkcert/releases). Download the appropriate file for your system, then move it to `/usr/local/bin/` and make it executable as shown above.

### **Conclusion**
This approach should help you successfully download and install `mkcert`. Let me know if you encounter any further issues!