I have first installed the remoting framework on the latest 2.2 version, which gave just an 'Script end' error, and var_dump()ing the session ID, and the test I removed the comments, gave 'string (0)'. After updating to the newest 2.3, logging in gives me this error (includes var_dump): array(4) { ["faultcode"]=> string(6) "Server" ["faultactor"]=> string(35) "method '' not defined in service ''" ["faultstring"]=> string(0) "" ["detail"]=> array(1) { ["soapVal"]=> string(0) "" } } Error: Server: I'm running ISPConfig on Debian Etch, if you need to know. Could anyone help? -- Bas
Update PHP to the latest version then try again You can replace the existing PHP package in ispconfig by downloading the latest from http://www.php.net and renaming the folder to match the the old version so ISPconfig doesn't complain. My configure command in the compile_aps/compile file on line 129 reads like this ./configure --with-apxs=${INSTALL_ROOT}/httpd/bin/apxs --enable-track-vars --enable-sockets --enable-mbstring=all --with-config-file-path=${INSTALL_ROOT}/php --with-curl --with-dom --enable-ftp --prefix=${INSTALL_ROOT}/php ${WITH_OPENSSL} ${WITH_MYSQL} --enable-dom ${WITH_ZLIB_DIR} --without-pear || error "Could not configure PHP" Then try again
Hmmf, after recompiling PHP 5.2.3, with --enable-dom added, I get the following stuff, the sams as I got in 2.2 : string(0) "" string(0) "" Script end ...
The remoting framework runs fine on ISPCXonfig 2.2.14 if you enable xml. The errors you got are not a problem that XML is not enabled. In ISPConfig 5.2.3 it is not nescessary to enable xml anymore, so do not alter the compile script in this version! What is the exact client script, that you used. Did you add a remoting user and used this user in the remoting login function?
http://www.howtoforge.com/forums/showthread.php?t=13260&highlight=remoting This thread is an identical issue