If you are receiving the following 403 errors:

• "message": "The used authentication method is not allowed on this route."
• "message": "This route can only be accessed by anonymous users."

Then keep reading for how to resolve them.

Attempting to log in to a Drupal site using REST API and I had to battle a few head winds along the way.  What is worse, they were self imposed!

Creating a new account in Mail on OSX Big Sur (11.2) and complete the required information for:

• Email
• Username
• Password
• Account type: IMAP
• Incoming mail server
• Outgoing mail server

I receive a message "Unable to verify account name or password."

Working on a new CentOS 7 server, Node wasn't installed.  You can quickly this through using the prompt node -v

node not found

In Plesk, the extension had been installed, however this doesn't mean correctly.  So I needed to install Node and npm on the CentOS 7 server.

Recently I have been investigating one of my Linux server's speed using the copy [cp] command.  This came about due to 'upgrading' the server from Centos 6 to 7.  Once I had migrated a domain, I ran the following command

I had been running a few Centos 6 servers just past their EOL (30th November 2020) and it was time to kick in to action a plan I had been working on when I realised EOL was on my doorstep.

When those simple annoyances are too frustrating!  Yes we have all been there and I was really hoping that Apple would have fixed what is obviously a bug.

Attempting to load changes in a staging site and the bountiful error page of

Working through migration on a new Centos 7 server, the default mailbox size is 100MB.  Yes a well organised account doesn't need more than 100MB.  However, how to resolve this size for the outlier people with big mailboxes.

In one of our domains being migrated contains an account with 300MB plus and on another domain 400MB plus.  To change the  default size from 100MB run through shell the following command

Running a common composer command, post an upgrade on the server to Centos 7 and I received the following error:

The purple warning notification of annoyance recently came my way!  I received the following warning:

Publishing changes from background threads is not allowed; make sure to publish values from the main thread (via operators like receive(on:)) on model updates.

What was happening?

The functionality of the code uses URLSession to get a user's name via API and the display is simple piece that initially message of Hello {user}.