Why You Shouldn't Upgrade To Windows 11 Today

What are your thoughts on Windows 11?  Is it worth the upgrade?  What does this new OS offer that's so great?  How is this different than previous versions of Windows you've used in the past?  What do you feel about Microsoft's latest operating system release?

These are all questions I often hear, and with good reason. There has been a lot of hype around the newest iteration of the world's most popular operating system, but is there any substance behind that hoopla, or will you be just as disappointed with what turns out to be released when September rolls around. Let me help answer these questions for you by explaining some of my concerns regarding upgrading to Windows 11.

Windows 11 has excellent user interfaces as transparency, floating style, and glassy look increase its hotness. Anyway, some users upgraded their PCs to Windows 11, and they faced some issues in Internet connectivity, though they had to downgrade their Windows to 10. These types of problems are confronted because of the system requirement as Windows 11 strict system requirements. If you install Windows 11 and your system requirements don't match, you may encounter these types of problems.

Even some software will also stop working, and you need to wait for them to be updated to use. And a lot of companies fixed their products in the pre-release of Windows 11. Still, some major companies started working on making their software Windows 11 friendly, and the updates will be available in the upcoming days. To avoid such issues, I will recommend waiting for a week or more.

Windows 11 system requirements:

• Processor: 1 GHz or faster with 2 or more cores on a compatible 64-bit processor or System on a Chip (SoC)
• Storage: 64 GB or larger storage device
• Memory: 4 GB RAM
• System firmware: UEFI, Secure Boot capable
• Display: >9-inch with HD Resolution (720p)
• Graphics card: DirectX 12 compatible graphics / WDDM 2.x
• TPM: Trusted Platform Module (TPM) version 2.0 or PTT you can turn these on from BIOS
• Internet connection: Microsoft account and internet connectivity required for setup for Windows 11 Home

Let us know in the comment section if you faced any problems while using Windows 11.

Read More

How to fix Google AdSense error "We apologize for the inconvenience..."

Google Adsense Publisher

Google AdSense is an excellent way for bloggers to make money from their blogs. You can sign up as an advertiser and place ads on your site that will generate revenue based on impressions, clicks, or conversions.

While using Google AdSense, you may face a lot of issues and errors. From the beginning to start with a new AdSense account until you get your first payment. Anyway, I will let you know about other issues some other time. Right now, I'm letting you know about the basic problem many AdSense publishers face while using the AdSense dashboard.

When you click on the Policy Center or Payment settings, the below error will propagate. 

We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it.

It's very frustrating because many others will say to fix the Google AdSense issue, "We apologize for the inconvenience..." then clear cookies, cache even some will say log out and then log in after some days bla bla bla. I will tell you don't listen to them. :P

The only reason for this error is that you are using Ads Blocker, no matter which ads blocker you are using, but the ads blocker is the only reason for this issue.

How to fix Google AdSense error "We apologize for the inconvenience..."

1. Disable Ads Blocker.
2. Hit Refresh or F-5.

Disable Ad Blocker for Google AdSense

After disabling Ad Blocker hit Refresh

I'm sorry for making this tutorial a little bit longer. That's what the Google Search Engine algorithm wants me to do; otherwise, you won't find my tutorial on top of other pages.  

Video Tutorial

Read More

How To Enable HTTPS/SSL Certificate for Custom Domain in Blogger

HTTPS For Blogger

Blogger with a custom domain and without SSL is nothing. You will lose your visitors as a search engine like Google will send your website back because HTTPS is essential, as search engines now need trust before sending a visitor to any link. If a site does not have HTTPS or SSL, a search engine like google or any other will try to send your website to the bottom or even off to any other pages, with this way, you will lose organic traffic. No matter how strong your content is, a search engine will not bring your site up if you don't have an SSL Certificate installed.

What is an SSL Certificate?

SSL Certificate installation is the process of installing a digital certificate onto your website or blog. SSL will ensure that all data transferred between you and your visitors are encrypted, making it difficult for hackers to steal sensitive information like credit card numbers.

Why is SSL Important?

SSL plays an essential role in SEO, and it's mandatory to have an HTTPS if you want to rank your website with various search engines like Google, Bing, Yandex, etc. Even almost all browsers are now issuing a warning message of "not secure" if your website doesn't have a valid SSL Certificate Installed.

According to SemRush

As of 2021, more than 500 million blogs exist out there, with more than 409 million visitors each month.  Users produce around 70 million new posts and 77 million new comments each month. Content marketing predicts to be an industry worth $412.88 billion.

Now, let's make it short you came here to know how to install an SSL certificate on your blogger blog or enable HTTPS on your blogger blog. Before moving on further, make sure in blogger in Settings find Publishing and confirm that Custom domain installed, and Redirect domain is active.

No please follow the below steps to install a free SSL certificate for the blogger blog.

Steps:

• Go to Settings
• Go down to HTTPS

You will see below HTTPS availability Status: No.

• Just turn on HTTPS availability, and you will see the Status Unknown.

• After this, refresh the page, and now you will see Status: Pending - HTTPS Availability is being processed. Try again later.

Now you have to wait for 5-10 minutes, and Google Trust Services LLC will issue you an SSL Certificate for Free Forever.

• Now refresh the page, and you will see Status is available.

• Now turn on the HTTPS redirects

And that's all. 

I know you must have some queries, but before you ask me a question, I'm trying to cover almost all of your questions here below. If you still have any questions, you can ask me in the comment section below.

Why is my blogger site not secure?

Because you did not enable HTTPS for your blogger, go to Settings, scroll down to HTTPS and turn HTTPS redirects.

Blogger HTTPS availability is Status unknown?

When you turn on HTTPS availability, the Status will become unknown, refresh the page, and you will see the result.

Blogger HTTPS not working?

Sometimes it happens when you google issue an SSL certificate, but you still see the HTTPS is not working, don't be panic. It will take some time, it can be up to 30minutes, and your certificate will become available globally. 

What to do when blogger SSL Error "Status: Pending - HTTPS Availability is being processed. Try again later?".

Don't be panic. Google is issuing an SSL certificate, and it may take a while.

How much time does blogger take to issue an SSL?

It will take 5-10minutes, but it can take up to 30minutes in rare cases.

It took more than 30 minutes. HTTPS availability status is still pending. What to do?

May any conflict happens, in this case, you have to verify certain things; first, check your custom domain is setup correctly and working, and make sure your custom domain is not expired. Then you have to turn off HTTPS availability and turned it on again after a minute. And then, wait for 5-10 minutes, and you will get your FREE SSL certificate for your custom domain in blogger.

HTTPS availability Status: Failed - HTTPS SSL Certificate failed to be processed?

This is the error when your domain is not properly working or DNS is removed, or not accessible or maybe you just recently change it to blogger, please give it some time, DNS normally takes 12hrs-72hrs to propagate properly. Once your domain working properly then you can simply Install HTTPS for your blogger.

Video Tutorial

Read More

How To Deploy Private GitHub Repository To Any Hosting - CI/CD

GitHub to Web Hosting 

You can deploy private GitHub repo to cPanel, Hostinger, or any Web Hosting Manager. Automatic deployment for your CI/CD. This method will work for that. I'm a web developer by profession, I face this issue a lot until I find this method.

Deploying while cPanel Git version control you will face the issue "GitHub cannot access private repository" while submitting Github private repo unless until you setup a private key of cPanel to your GitHub Deploy keys.

Here you don't need to have SSH access or any root access for this method. All you need is an FTP ACCOUNT.

Let's start

In this method, I will be using the Deployment of GitHub Private Repo to cPanel.

1. You have to create an FTP account.

You need to setup the following details.
Log In: it will be the username

Domain: it will be your domain name.

Password: Write a password whatever you like. But keep it safe we will use re-use it, in github.

 

2. In FTP Accounts, click on Configuration FTP Client, to get FTP Username and FTP Server Address.

3. Now go to your repository Settings > Secrets > Actions and click on New repository secret.

https://github.com/{USERNAME}/{REPO_NAME}/settings/secrets/actions

4. Now add a repository secret these details one by one.

Name: FTP_SERVER

Value: YOUR_FTP_SERVER_ADDRESS

Name: FTP_USERNAME

Value: YOU_FTP_USERNAME

Name: FTP_PASSWORD

Value: YOUR_FTP_PASSWORD

In my case its

Name: FTP_SERVER

Value: ftp.recmail.net

Name: FTP_USERNAME

Value: admin_github@blog.hit4visit.com

Name: FTP_PASSWORD

Value: s^E7tXj+O00U

5. Now add an action workflow. Change its name from main.yml to cPanelDepolyment.yml

    Copy the code below and add it to the workflow, click on start commit and then commit new file.

Version 1 code:

name: Publish Website to Web Hosting
on:
  push:
    branches:
      - main
jobs:
  FTP-Deploy-Action:
    name: FTP-Deploy-Action
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2.1.0
      with:
        fetch-depth: 2
    - name: FTP-Deploy-Action
      uses: SamKirkland/FTP-Deploy-Action@3.1.1
      with:
        ftp-server: ${{ secrets.FTP_SERVER }}
        ftp-username: ${{ secrets.FTP_USERNAME }}
        ftp-password: ${{ secrets.FTP_PASSWORD }}

Version 2 code:

name: Publish Website to Web Hosting V2
on:
  push:
    branches:
      - main
jobs:
  web-deploy:
    name: 🎉 Deploy
    runs-on: ubuntu-latest
    steps:
    - name: 🚚 Get latest code
      uses: actions/checkout@v2

    - name: 📂 Sync files
      uses: SamKirkland/FTP-Deploy-Action@4.3.0
      with:
        server: ${{ secrets.FTP_SERVER }}
        username: ${{ secrets.FTP_USERNAME }}
        password: ${{ secrets.FTP_PASSWORD }}

And boom, now you can do CI/CD of your project. Now, wait a few minutes until it deploys its initial code, after that once you push to the branch your setup, for older "master" or new version "main" or whatever you setup as default or you want its push to be updated, it will automatically update on your website. 

Video Tutorial

Read More