Page 2 of 2

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon Dec 19, 2011 6:07 pm
by croontje
Yes, I read it, that's why I wanted to post the solution here just to be sure. This was the default config of my host :)

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Wed Mar 07, 2012 3:27 pm
by flatcap1
I also got "A problem occurred communicating with the module server" error but changing:
arg_separator.output = "&" to
arg_separator.output = "&" in
C:\xampp\php\php.ini

somehow fixed it.

Thanks CMSMS forum members

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Wed Mar 07, 2012 4:00 pm
by Rolf
croontje wrote:No problem.

I just discovered the bugreport about this issue but I don't think the devs will fix it :)

http://dev.cmsmadesimple.org/bug/view/7290
Reto Hugi (reto) wrote:Is fixed in 1.10.3 - thank you!

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon Apr 16, 2012 9:59 am
by didurov
I have same problem in 1.10.3 version.
URL: http://www.cmsmadesimple.org/ModuleRepo ... equest/v2/
it give me: "A problem occurred communicating with the module server"

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon May 21, 2012 12:01 am
by crankshaft
I have the same problem with a fresh install of 1.10.3.

I have changed the php.ini setting to "&" makes no difference.

Also, even using wget or trying to access the repository url in a web browser also fails with Error 404 not found !

http://www.cmsmadesimple.org/ModuleRepo ... equest/v2/

It seems that this URL is wrong ??

I have another CMSMS running on same server (1.5.1) that works fine but uses a different url:

http://modules.cmsmadesimple.org/soap.p ... Repository

but that URL will not work in 1.10.3 ?!

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon May 21, 2012 10:58 am
by crankshaft
I have also checked the class and it states:

[removed]

So 1.10.3 already includes the mod, I have modified php.ini as recommended and restarted apache and still no fix.

The URL in the module manager: http://www.cmsmadesimple.org/ModuleRepo ... equest/v2/

cannot be accessed, even outside of CMSMS by using a web browser or wget from the command line, so is this a problem with the server which is hosting the repository ??

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon May 21, 2012 11:07 am
by janvl
Hi,

The URL for a functioning 1.10.3 install says:
http://www.cmsmadesimple.org/ModuleRepo ... equest/v2/

Check the chunksize as well, it could produce problems if set wrong.

Download Chunk Size (Kb):
256 Kb

These settings work for a german shared hosting site.

Kind regards,
Jan

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon May 21, 2012 11:15 am
by crankshaft
Hi Thanks;

1. Version 1.10.3
2. Chunksize set to 256.
3. php.ini seperator character set to '&'
4. Module URL = http://www.cmsmadesimple.org/ModuleRepo ... equest/v2/
4. removed

But I have tried to emphasize before that I cannot even access the url even WITHOUT using cmsms.

So, can someone please click on this url and let me know if they receive the following error message:

Code: Select all

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<__html><head>
<title>404 Not Found</title>
</head></__body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<__body></__html>
or if they are able to see the xml output ??

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon May 21, 2012 11:23 am
by janvl
If I click the link I get:
--------------
Not Found

The requested URL was not found on this server.
--------------
Jan

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Mon May 21, 2012 12:03 pm
by crankshaft
I can't see any errors in apache access or error logs, which log file is likely to show me what the problem is ??

Thanks

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Thu May 24, 2012 4:52 pm
by calguy1000
a: There is nothing wrong with the module repository. Just tested it from my house.
b: The URL specified WILL generate an error if you just copy/paste it into the browser
it requires more data. This is intentional
c: The module repository / cmsms website is NOT blocking any hosts by domain or IP address (that I know of).

If you are still having problems then maybe it is that your host is not allowing outgoing connections. maybe there is some other condition that we are not aware of, that is causing your site not to be able to talk to the module repository. This will take some significant debugging.

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Thu May 24, 2012 5:05 pm
by calguy1000
Simple test #1:
{fetch file='http://api.geonames.org/citiesJSON?nort ... rname=demo'}

Actually... I had a thought.
See if curl is available in your phpinfo. I bet it isn't.

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Thu May 24, 2012 5:09 pm
by calguy1000
yeah, that'd be the problem. if curl isn't available and/or isn't a new enough version then there'll be problems.

There are some bugs in the http_request class (some of which I have fixed for 1.11). But without a recent version of curl on your host there isn't much we can do for now.

Re: ModuleManager: Error communicating with server (1.10.2)

Posted: Fri May 25, 2012 12:57 am
by crankshaft
calguy1000 wrote:Simple test #1:
{fetch file='http://api.geonames.org/citiesJSON?nort ... rname=demo'}

Actually... I had a thought.
See if curl is available in your phpinfo. I bet it isn't.
Hi, the test code returns several records like this:

Code: Select all

{"geonames":[{"fcodeName":"capital of a political entity","toponymName":"Mexico City","countrycode":"MX","fcl":"P","fclName":"city, village,...","name":"Mexiko-Stadt","wikipedia":"","lng":-99.12766456604,"fcode":"PPLC","geonameId":3530597,"lat":
However, the problem with Module Manager is still there.

Also, I am running an earlier version of CMSMS (1.5.1) on the same server and there's no problem with the module manager on that install.
Edit
----
Installing php5-curl solved the problem, although the fetch file example above still executed sucessfully without php5-curl installed.