After Plesk update to Wordpress, Magento and concrete5 sites do not upgrade anymore.

[Arjan Oskam]

After the automatic update of Plesk to Plesk 12.5.30 # 22 we got a lot of problems.
First Plesk could no longer search for updates (This has been solved by doing the following:
[Root @ mail /] # nano / etc / hosts
72.21.81.253 autoinstall.plesk.com (added)
[Root @ mail /] # / usr / local / psa / admin / sbin / autoinstaller --debug --separate log -Select release-current --upgrade-installed-components
)
Then I found out none of the CMS systems I used are working properly anymore, namely:
- I can't get/find updates for Wordpress nor Magento nor concrete5.
- I can't get/find theme updates for Wordpress nor Magento nor concrete5.
- I can't retrieve/find plugin updates for Wordpress nor Magento nor concrete5.
- I can't get/find new plugins for Wordpress nor Magento nor concrete5.
- I can't get/find new themes for Wordpress nor Magento nor concrete5.

Everywhere it is indicated that there are no updates. When I try to add an plugin in Wordpress I get the following message: "There has been an unexpected error. There may be something wrong with WordPress.org or the server configuration. If this problem persists, please ask in the forum for help..."

We can't find anything about this, and we cannot seem to solve this ourselves.
Has anyone had this problem before or does anyone know the source of this problem?

 

[IgorG]

Looks like something wrong with network configuration. Are you sure that hostname WordPress.org is correctly resolvable and accessible from your Plesk server?

 

[trialotto]

@Arjan Oskam

You should NOT add the line "72.21.81.253 autoinstall.plesk.com" to /etc/hosts.

Remove that line from /etc/hosts and recheck the presence of the problems, that you encountered earlier.

Furthermore, the problems with the CMS can be closely related to the /etc/hosts setting (that essentially is in conflict with /etc/hostname), but some other reasons can be present.

Just keep me posted, please retry when having edited the /etc/hosts file and post some output, if you have it.

Regards...

 

[Arjan Oskam]

@Arjan Oskam

You should NOT add the line "72.21.81.253 autoinstall.plesk.com" to /etc/hosts.

Remove that line from /etc/hosts and recheck the presence of the problems, that you encountered earlier.

Furthermore, the problems with the CMS can be closely related to the /etc/hosts setting (that essentially is in conflict with /etc/hostname), but some other reasons can be present.

Just keep me posted, please retry when having edited the /etc/hosts file and post some output, if you have it.

Regards...

Then I get the following error:

And the updates on Magento, Wordpress and Concrete and all the other problems are still there!

 

[trialotto]

@Arjan Oskam

Try to issue the command: wget http://autoinstall.plesk.com/plesk-installer (wget or curl, in order to determine whether you can actually establish a connection)

If you cannot connect, have a look at the firewall (in order to determine whether the plesk.com IP has not been blocked. This check should not really matter, but it can do no harm).

Just let me know what the results are.

Regards....

 

[Arjan Oskam]

@Arjan Oskam

Try to issue the command: wget http://autoinstall.plesk.com/plesk-installer (wget or curl, in order to determine whether you can actually establish a connection)

If you cannot connect, have a look at the firewall (in order to determine whether the plesk.com IP has not been blocked. This check should not really matter, but it can do no harm).

Just let me know what the results are.

Regards....

[15:40:57] Rick: curl http://autoinstall.plesk.com/plesk-installer
curl: (6) Could not resolve host: autoinstall.plesk.com; Unknown error
[15:41:10] Rick: wget http://autoinstall.plesk.com/plesk-installer
--2016-02-19 15:39:51-- http://autoinstall.plesk.com/plesk-installer
Resolving autoinstall.plesk.com (autoinstall.plesk.com)... failed: Name or service not known.
wget: unable to resolve host address ‘autoinstall.plesk.com’

Is the error I get then!

 

[trialotto]

@Arjan,

The issue in this case is that you have some networking problems, as @IgorG suggested immediately.

This problem has to be solved by your hosting provider or network administrator.

Regards....