Site-Manager
Site-Manager copied to clipboard
UNABLE TO COMMUNICATE WITH SITE
Hi
just installed the module and I am getting "UNABLE TO COMMUNICATE WITH SITE" in site overview.
What seems to be a bit odd is that the remote installs have a very high Action ID eg 25032012.
The dev tool spits out "XMLHttpRequest cannot load http://mylocalsite/?ACT=25032012&site_id=1&k=b89a541ff5458ad6f9882034aad995ef&method=ping"
The monitored site is on EE version 2.5.3. The client manager is running on 2.5.2.
Any ideas?
Hmm, that Action ID does seem strange.
Can you able to check in the EE database for the site where you have installed Site manager server and look for a table called exp_actions? This table should list out all the Actions that have been setup and there should be a record for the "Site_manager_server" module.
Can you verify that the Action IDs match what you are seeing in the site setup (e.g. 25032012)?
The Action Id is the same: 25032012.
What happens when you enter the URL directly I to the browser address bar? Do you get an error?
ie: http://mylocalsite/?ACT=25032012&site_id=1&k=b89a541ff5458ad6f9882034aad995ef&method=ping
I'm getting the same error message, but more specifically I'm getting this:
Severity: Warning
Message: require_once(Rijndael.php) [function.require-once]: failed to open stream: No such file or directory
Filename: core/Loader.php(727) : eval()'d code
Line Number: 70
I'm getting the same error, but when I do your URL up above on either my production server or my local machine I just get the expression engine error of
The action you have requested is invalid.
Thinking this might be a case sensitive filenaming issue. Like @litzinger mentioned, it looks like it is unable to load the encryption library. Looking into it.
Thanks for taking a look, I love the concept of your project as it drives me crazy having to move the DB everytime I make theme changes that have new channels.
Was there ever a solution for the problem @litzinger noted? I'm in the same boat at the moment. Would love to know if there was a way around it.
Thanks!
Never mind, looks like providing an explicit path to:
PATH_THIRD."site_manager_server/helpers/phpseclib/Crypt/Rijndael.php
took care of it!
Was having problems with not being able to communicate with site. @danieldecker's line actually fixed my problem as well, can this be changed and merged?