Friday, November 24, 2023

sudo apt-update throwing "connection timed out error"

 If you face this "connection timed out error"

$ sudo apt update 
  Could not connect to in.archive.ubuntu.com:80 (*2403:8940:ffff::f*), connection timed out Could not connect to in.archive.ubuntu.com:80 (103.97.84.254), connection timed out
Err:8 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease
  Unable to connect to in.archive.ubuntu.com:http:
Err:9 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease
  Unable to connect to in.archive.ubuntu.com:http:
------------------------------------------------------------------------
 
1)sudo nano /etc/apt/sources.list
2) replace all http://**xx**.archive.ubuntu.com/ubuntu... to http://archive.ubuntu.com/ubuntu ...
 
https://askubuntu.com/questions/1198621/apt-get-cannot-connect-to-ubuntu-archives  
 

Wednesday, November 22, 2023

Create a bootable USB stick on Ubuntu

 

Download the Ubuntu to your system

  1. Insert your USB stick (select ‘Do nothing’ if prompted by Ubuntu)
  2. On Ubuntu 18.04 and later, use the bottom left icon to open ‘Show Applications’
  3. In older versions of Ubuntu, use the top left icon to open the dash
  4. Use the search field to look for Startup Disk Creator
  5. Select Startup Disk Creator from the results to launch the application

REFERENCES:

https://ubuntu.com/tutorials/create-a-usb-stick-on-ubuntu#3-launch-startup-disk-creator

Saturday, November 11, 2023

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

 

See the current value of max-old-space-size (in MB)

 

node -e 'console.log(v8.getHeapStatistics().heap_size_limit/(1024*1024))'

 

 

That said, to increase the memory, in the terminal where you run your Node.js process:

 export NODE_OPTIONS="--max-old-space-size=8192"
 
Reference 
https://stackoverflow.com/questions/53230823/fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-failed-javas 

Thursday, October 26, 2023

Test using REQBIN

 

 

1) Go to the website https://reqbin.com/curl


2) paste the curl and run to see validation errors

Wednesday, October 11, 2023

RESIZE AWS DISK SPACE - increase volume for ubuntu ec2 instance

 

To increase the storage space of an Amazon EC2 instance, you can follow these general steps. Keep in mind that this process may vary slightly depending on the EC2 instance type and your specific requirements:

  1. Create a Backup (Snapshot): Before making any changes, it's crucial to create a backup (snapshot) of your EC2 instance's EBS (Elastic Block Store) volume. This ensures that you have a point-in-time copy of your instance's data that you can restore if anything goes wrong during the resizing process.

    To create a snapshot, go to the AWS Management Console, navigate to the "EC2" service, select "Volumes" from the left sidebar, find your instance's EBS volume, right-click it, and choose "Create Snapshot."

  2. Stop the EC2 Instance: To make changes to the instance's storage, you will typically need to stop it first. In the AWS Management Console, right-click your instance, and choose "Instance State" > "Stop."

  3. Resize the EBS Volume: After stopping the instance, you can resize the EBS volume attached to it. Here's how:

    a. In the AWS Management Console, go to "EC2" and navigate to the "Volumes" section.

    b. Find the EBS volume that is attached to your EC2 instance.

    c. Right-click the volume and choose "Modify Volume."

    d. In the "Modify Volume" dialog, increase the volume size to your desired capacity.

    e. Confirm the changes, and AWS will perform the resize operation. This process usually completes quickly, but it might take a few minutes.

  4. Start the EC2 Instance: Once the volume is resized, you can start your EC2 instance again. Right-click your instance in the AWS Management Console and choose "Instance State" > "Start."

  5. Resize the File System: After resizing the EBS volume, you'll need to resize the file system on the instance to make use of the additional storage space. This step depends on the operating system you're using:

    • For Linux: If you're using Linux, you can use the resize2fs command to resize the file system. For example, if you're using ext4, you can run:

      bash
      lsblk //to find out partition name xvda1
      df -hT //to find the type of partition 
      sudo growpart /dev/xvda 1
      sudo resize2fs /dev/xvda1
      
       
  1. Verify the Storage Increase: 

     

    df -h 

Remember that these steps might vary slightly based on your specific EC2 instance type, region, and operating system. Always take precautions and create backups before making changes to your EC2 instance's storage to prevent data loss.

Wednesday, September 27, 2023

Set Up Firebase Integration

 

    • Go to the Firebase Console (https://console.firebase.google.com/) and create a new project or use an existing one.
    • Once the project is created, navigate to the "Project settings" and click on the "Cloud Messaging" tab to find your server key and sender ID. You'll need these for server-side integration.

     

    If server key is not available:

         

    1. Go to this link and enable: "Cloud Messaging" service:

    https://console.cloud.google.com/apis/api/googlecloudmessaging.googleapis.com

     

       2. In the project settings, add a web app (if you don't already have one) and download the Firebase configuration JSON file. You'll need this for server authentication.

     3. To get VAPID key, in the "cloud message" generate web push certificate key pair

     

     

     

     

     

     

     

     

     

     

     

     

     

    References: https://stackoverflow.com/questions/37427709/firebase-messaging-where-to-get-server-key

Saturday, August 26, 2023

DOCKER

REFERENCES:

https://www.freecodecamp.org/news/where-are-docker-images-stored-docker-container-paths-explained/

 

1)  The output contains information about your storage driver and your docker root directory

$ docker info 
 
2) A Docker container consists of network settings, volumes, and images.
 
 Ubuntu: /var/lib/docker/
 
3) Docker images
  Docker images are stored in /var/lib/docker/overlay2
 
4) Docker Volumes
 
$ docker run --name nginx_container -v /var/log nginx 
 
5)Clean up space used by Docker
$ docker system prune -a 
 
6) To get container size and container info
$ docker ps -s
$ docker ps -a 
 
7) pull down an image from a repository, 
docker pull 
create a container from an image that does not yet exist locally, each layer is
pulled down separately, and stored in Docker's local storage area, which is
usually /var/lib/docker/ 
 
8) Check out the sizes of the images:
docker image ls
9) create a volume
docker volume create my-vol 
10) List Volumes
docker volume ls

11) Inspect volume
docker volume inspect my-vol
 12) To backup volume
 docker run --volumes-from --container_name-- -v $(pwd):--path-- ubuntu tar cvf --path--/storage.tar /app/storage/app/public
13) To restore volume
docker run --rm --volumes-from --container_name-- -v $(pwd):--path-- bash -c "cd storage/app/public && tar xvf --path--/storage.tar" 
14) To restore volume 
docker exec -it docker-webserver-1 /bin/bash 
 
TTo Set up ssl certificate:

docker compose run --rm certbot certonly --manual --preferred-challenges dns -d example.com -d *.example.com -v
 
docker ps
docker restart docker-name
docker system df
 df -h
docker builder prune
docker exec -it docker-webserver-1 /bin/sh
docker logs docker-webserver-1
Dangling images are images that are not associated with any running containers and are not tagged with a specific version or name. These images are typically left behind when you build or pull new images, and older, unused versions are no longer needed. They can accumulate over time and consume disk space. 
docker image prune
docker container prune 

Thursday, June 15, 2023

Report Generation for SonarCloud using Bitegarden Report

 

 

 

java -Dsonar.token=SONAR_TOKEN -Dlicense.file=/home/mysupply/Downloads/bitegarden-sonarcloud-report-1.3.4/LICENSE.txt -Dsonar.projectKey=examplecode1_phpbackend -Dsonar.organizationKey=examplecode1  -Dreport.type=0 -jar bitegarden-sonarcloud-report-1.3.4.jar

Wednesday, June 14, 2023

ERROR for site owner: Invalid domain for site key google recaptcha

 

If you encounter the error message "Invalid domain for site key" when working with Google reCAPTCHA, it typically means that the site key you are using is not associated with the domain or website where you are trying to implement reCAPTCHA.

To resolve this issue, you need to ensure that you have registered the correct domain or website with Google reCAPTCHA and obtained the appropriate site key. Follow these steps to fix the problem:

  1. Go to the Google reCAPTCHA admin console: https://www.google.com/recaptcha/admin.
  2. Sign in with the Google account that is associated with the reCAPTCHA implementation.
  3. If you haven't already done so, register your domain or website by clicking on the "+ Add" button under the "Register a new site" section.
  4. Provide the necessary information, including the label for your site and the domain name(s) where reCAPTCHA will be used.
  5. Once you have registered your site, you will receive a site key and a secret key.
  6. Ensure that you are using the correct site key for the specific domain or website where you are implementing reCAPTCHA. The site key should match the domain you specified during registration.
  7. Update your website's code with the correct site key. Double-check that you have entered the site key accurately and without any additional spaces or characters.
  8. Save the changes and deploy the updated code to your website.

By following these steps and using the correct site key associated with the domain or website, you should be able to resolve the "Invalid domain for site key" error.

 

 

Add the site key to 

(search for recaptcha)

clients: supplier portal , admin portal , user portal (to their env.docker files)

Add secret key to

server: laravel back-end

 

Tuesday, May 23, 2023

Steps to setup Google Recaptcha

 To implement Google reCAPTCHA on your website, follow these general steps:

    Sign up for reCAPTCHA: Go to the reCAPTCHA website (https://www.google.com/recaptcha) and sign in with your Google account. You will need to register your website and obtain API keys.

    Choose reCAPTCHA type: Decide whether you want to use reCAPTCHA v2 or reCAPTCHA v3. reCAPTCHA v2 provides the traditional "I'm not a robot" checkbox, while reCAPTCHA v3 is a background verification system that assigns a score to user interactions.

    Obtain API keys: Once you have registered your website, you will receive a site key and a secret key. These keys will be used to integrate reCAPTCHA into your website.

    Add reCAPTCHA script to your HTML: Insert the reCAPTCHA script tag into the <head> section of your HTML file. This script is provided by Google and loads the reCAPTCHA functionality on your web page.

    Add reCAPTCHA widget: Place the reCAPTCHA widget where you want it to appear on your website. For reCAPTCHA v2, this is typically a checkbox element. For reCAPTCHA v3, you will need to add a script to initiate the verification process.

    Verify the response: When a user submits a form or performs an action, you need to verify the reCAPTCHA response on your server-side code. Send the response token to Google's reCAPTCHA API for verification using your secret key.

    Handle the verification response: After submitting the reCAPTCHA response to Google, you will receive a verification response. Based on this response, you can determine if the user is a human or a bot and proceed accordingly.

The implementation details can vary depending on your programming language and framework. Google provides detailed documentation and code examples for various platforms, which you can refer to for specific implementation steps.

Remember to handle the verification on the server-side, as client-side verification can be bypassed by malicious users.
 

Other references:

https://www.freecodecamp.org/news/how-to-setup-recaptcha-v3-in-laravel/

Facing issues in Microsoft Azure Portal, Office.com??

 1)To fix issues, create a new global admin user temporarily

Steps: i) Login to office.com(Microsoft 365 account)

           ii) Select 'Admin' from the top left(::- App Launcher)

           iii) Go to 'Users' section in the left side bar

            iv) Sielect 'Active Users' from the sub menu

             v) Use 'Add User' option to create new user with 'Global Admin' prevelege.

             vi)Assign pwd, ensure to remember them

              vii)Enable MFA if required

              viii) Assign all unpaid licenses.

    After creating, do the required task, like verifying publisher or enabling MFA.

Once the task is done you may delete the test user

         

Tuesday, May 9, 2023

Become MICROSOFT verified publisher

References: 

https://learn.microsoft.com/en-us/azure/active-directory/develop/mark-app-as-publisher-verified
https://portal.azure.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade

 

If you are already enrolled in the Microsoft Partner Network (MPN)(Microsoft partner center) and have met the pre-requisites, you can get started right away:

    1)Sign into the Azure Portal, Search 'App Registration' portal 

    2)Choose an app and click 'Branding & properties' from the left side menu.

    3)Click Add MPN ID to verify publisher and review the listed requirements.

    4)Enter your MPN ID and click Verify and save.

 

 

Other Portals you might require for MFA and other tasks:

 

1)Azure active Directory

2) Azure AD Identity  (Risky users issue)

 

 


Wednesday, April 12, 2023

How to host godaddy domain in AWS S3

 https://medium.com/tensult/aws-hosting-static-website-on-s3-using-a-custom-domain-cd2782758b2c