(SOLVED) A problem occurred communicating with module server

[rvwilliams]

Hi

I'd kept my site on 1.9.4.3 waiting for some bugs to be fixed. Then I decided that the time was right to upgrade to 1.10.3. The upgrade appeared to work OK with no error messages. However when I go to the Module Manager I get the error
A problem occurred communicating with the module server
I've checked arg_separator.output and this is set to '&'.

I've had to restore 1.9.4.3.

What's going wrong and how do I fix it?

Richard Williams

[Dr.CSS]

I would look in the system info page for any yellow ! or red X...

[rvwilliams]

Hi

Thanks for the info. I did do this immediately after the upgrade and there were none.

Richard Williams

[rvwilliams]

Hi

I've now done a clean install of 1.10.3.0 to a different folder on the server with completely new and empty data base tables and I'm still getting the same error. I've got green ticks in System Information except for config_file where I can't change permissions on config.php due to the hosting provider running suexec.

It looks to me as if something is being blocked by the server but I've no idea if this is correct or what might be blocked.

Any more ideas on this?

Richard Williams

[rvwilliams]

Hi

The major change between 1.9.4.3 and 1.10.x was the dropping of nuSOAP in ModuleManager and replacing it with a RESTFUL interface. It seems to me that the problem I'm having is connected in some way with this change. Are there any ports etc. that need to be open for the new RESTFUL interface to work?

Richard Williams

[rvwilliams]

Finally got there. By inserting some debugging code into class.modmgr_utils I discovered that the cmsmadesimple.org URL was being blocked by the hosting company so the version check was failing.