We come across Code 401: Expired JWT Token when we have an expired CloudLinux token.

As part of our Server Management Services, we assist our customers with several Linux queries.

Today, let us see how we can get rid of the token error.

Code 401: Expired JWT Token

Sometimes, we may receive a notification from CloudLinux about the JWT token being missing or expired.

The error message will look like the following:

Check existing JWT token:

FAILED: JWT token expired. Please check for JWT token in path “/etc/sysconfig/rhn/jwt.token”. Try running “rhn_check” for getting a new token if it is absent. Server can’t collect and send statistics to Centralized Monitoring if you don’t have a correct JWT token. Link to FAQ and troubleshooting https://docs.cloudlinux.com/shared-pro/#faq-2. Please write to support at https://cloudlinux.zendesk.com/ if you can’t resolve the issue.

Command for disabling this cron checker: “cldiag –disable-cron-checkers check-jwt-toke

As we mentioned at the beginning of this article, this can happen when the token set up by CloudLinux is expired and is not updated.

However, we can remove the token and regenerate it.

moving ahead, let us see how our Support Techs perform the same for our customers.

To begin with, we move or remove the JWT token.

In addition, we create a new one by first moving the token file out of the way:

mv -v /etc/sysconfig/rhn/jwt.token{,.bak}

We need to register CloudLinux. It is important, so we make sure of this.

clnreg_ks --force

From there, since we have CloudLinux, we try to generate another token with this command:

rhn_check

Once we complete this, we make sure that the token is re-created. To check, we run the following command:

cat /etc/sysconfig/rhn/jwt.token

[Couldn’t fix it? We are glad to be of help]

Conclusion

In short, we saw how our Support Techs fix this error in an easy and effective way.