GitHub Authentication Token Setup for Your Local Repository

Are you Getting 403 errors when pushing updates to your GitHub repo?

If you are getting 403 (forbidden) errors when pushing updates to your GitHub repo then you might need to use a GitHub user authentication token for GitHub Authentication.

GitHub Authentication Changes July 2020

In July of 2020 GitHub announced the deprecation of user passwords for all Git operations.

In August of 2021 GitHub no longer accepted user name and passwords and replaced with user based authentication tokens.

I believe GitHub for Desktop was not affected but all other 3rd party tools were affected by this change.

Steps to Generate and Install a GitHub Authentication Token on Your Repository

Step 1: Generate a GitHub token for your account

Important to note that you can create more than one GitHub token or just one for all repositories under that account. This is up to you, the developer.

To generate a GitHub user authentication token, start by clicking on Developer settings and select Personal access tokens.

On the next screen, You’ll configure the scope and access options for your new GitHub token. Click the Green Generate token button at the bottom of the screen.

Make sure to copy and save this new GitHub token somewhere safe as you’ll only get one chance to copy it when you create it. If you mess this part up, you can just delete the old token and easily generate another.

Video: Creating GitHub Token Authentication

GitHub Token Authentication Requirements for Git Operations

Step 2: Configure GitHub to Use Your Authorization Token

Configure GitHub to Use Your Authorization Token with your repository with the Git remote command. Use the set-url argument and pass are URL with the following parts.

  1. https://
  2. Your GitHub Account name that appears in your GitHub URL
  3. A colon
  4. The GitHub Authentication Token you generated on Step 1.
  5. “”
  6. Same as # 2 (Account Name from URL)
  7. Forward Slash
  8. Your Repository Name

I used Git for Windows Git bash command line to execute this command.

$ git remote set-url origin https://[GitHub Account Name]:[Token][GitHub Repo Name]/[my-secure-repo-name]

Video: Setting the Token on a Local Repo

How to set a GitHub Authentication Token on a Local Repository

Playing MP4 Files on Samsung Smart TV

My First Attempt at Creating a Homemade Media Web App that Works on a Samsung Smart TV

I’ve been thinking about building a media web app for a while now and today was the first day I tested it on a Samsung Smart TV to see if it would work.

There are lots of ways you can do this but I’m trying to take the path of least resistance. For background, the MP4 file format now plays without plugins in most modern web browsers.

For my early “Alpha” tests, I just made a local web server with folders that could be browsed and put some media in there. This works for Chrome, Firefox etc. You can click and watch the video no problem.

Does the Samsung Smart TV Play MP4 Files?

The answer is a bit frustrating as it is Yes and No. WTF!

First, let’s deal with the No. The Samsung native web browser will not play a MP4 file if you link directly to it in my testing.

Next is the Yes. This happens when you add a USB Mass Storage Device to the TV. My Samsung Smart TV had 3 USB ports. I used one for a wireless Mouse / Keyboard combo device and one for a simple 10GB USB stick I had laying around for testing.

Once I added the USB Mass Storage Device to the Samsung TV USB port the Smart TV web browser would let me download the MP4 files to the USB stick then I would watch them by choosing the Mass Storage Device as the media data source.

I’m come back to add some screenshots soon.

If you found this, I hope it helped you solve your issue. 😉

~Cyber Abyss