The update isn’t showing up in Dashboard > Updates
You should have the choice to revive the module through the central Updates page in the WordPress Dashboard. Accepting for the time being that you’re sure that one more type of the module is open yet it’s not appearing for you to present, benevolently investigate the going with:
Is your permit key dynamic? Assuming you have changed space names (for example in the event that you’ve moved from an improvement site to your live area), go to the module settings page and once again save your permit key to initiate it on the live space.
Has your membership lapsed? On the off chance that you purchased the module over a year prior and haven’t restored then your membership might have lapsed. You should restore or re-buy the module to get another permit key before you can refresh.
Has the update just barely been delivered? In the event that the new rendition of the module was delivered as of late, it may not be accessible for you to introduce yet. It can now and then take some time for updates to open up on all destinations. If it’s not too much trouble, return later to check whether the update is showing up for you.
Programmed update is inaccessible for this module
This cautioning implies that your permit key isn’t dynamic on your ongoing space. You can refresh the module assuming you have a legitimate and dynamic permit key.
This ordinarily occurs assuming you have moved to an alternate space since you initially enacted the permit key. For instance, maybe you began utilizing the module on an arranging site and have since moved to your live area name.
To fix the issue, just:
Sign into your Account.
On the ‘Request History’ tab, click on ‘View Licenses’ close to the important buy.
Click ‘Deal with Sites’ on the following page.
From this page, you can add and eliminate URL’s that your permit key is dynamic on.
When the permit is dynamic on the right area, you will actually want to refresh the module from the WordPress Dashboard.
Error: SSL23_GET_SERVER_HELLO (or comparative SSL blunder)
This SSL error implies that your host is utilizing an obsolete variant of OpenSSL and doesn’t uphold the SSL Protocols that we are utilizing to give the most recent rendition of the module. To tackle the issue, you really want to ask your web host or server director to refresh their OpenSSL programming.
On the off chance that this is absurd, kindly send us a help demand with your WordPress logins and we can actuate your permit key physically if necessary.
This 403 blunder implies that something on your site is hindering the new adaptation of the module from being downloaded. For instance, this can be brought about by a security module or a document consents issue.
WPBeginner have given a superb article on How to Fix the 403 Forbidden Error in WordPress which will assist you with tracking down the reason for the issue.
Error: Update Package Unavailable
This implies there’s an issue with your permit key and it isn’t dynamic on your site.
If it’s not too much trouble, go to the module settings page and make sure that your permit key is dynamic. Assuming that it says your permit key is substantial however you’re actually getting this error when you attempt to refresh the module, kindly erase your permit key and reappear it.
It is possible that you have moved to an alternate space since you previously initiated the permit key. If so, you really want to go to the module settings page on the old space and erase the permit key so you can re-actuate it on the new area. On the off chance that the old area does not exist anymore, if it’s not too much trouble, send us a help solicitation and we will physically deactivate the permit key from your old space.
If it’s not too much trouble, make sure that your server has sufficient plate space for the update. When in doubt, you ought to expect that you really want sufficient room for 2x the size of the .compress document containing the module. On the off chance that this isn’t the issue, kindly send us a help demand.
Couldn’t make directory….
Assuming you get a error saying that a registry couldn’t be made, this could be brought about by one of these issues:
Document authorizations on server
The vast majority who report this error have a record or organizer consents issue on their server. You will get a similar blunder when you attempt to introduce or refresh any module, as it’s not intended for our module.
If it’s not too much trouble, take a stab at refreshing the module physically all things being equal. In the event that that doesn’t work, take a stab at introducing the new adaptation of the module through FTP.
To fix the issue, you should contact your facilitating organization and request that they change the envelope consents so you can introduce modules.
In the event that your site is facilitated on a Windows server, the ‘Couldn’t make index’ error can likewise be brought about by a similarity issue. You can fix this by introducing the free Windows Compatibility Fix module.