Problem adding clients

Asked by kobus44

In server 1.1.1. & client 1.07, whenever I try to add a new client in the Xibo Client Options application, the app gives me a SOAP error, but I'm not sure it really is a SOAP error. My server is accessible through DynDNS, but on a different port than the standard 80 port for webservers. It is located at port 8080, and hence, I have to add this to the http:// line to make it work. This worked flawlessly in server 1.1.0 and client 1.05, however, I now get the following error code:

SOAP-ERROR: Parsing WSDL: Couldn't load from "http://xxx.xxx.xxx/xibo/xmds.pjp?wsdl"

Now, this is peculiar to me, as I have saved my server settings in the Xibo CLient Options application as being "http://xxx.xxx.xxx:8080/xibo". In other words, it seems to forget the :8080 addition whenever I try to update. Is there a quickfix to this? Otherwise, I have to revert back to 1.1.0

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
kobus44
Solved:
Last query:
Last reply:
Revision history for this message
Alex Harrington (alexharrington) said :
#1

This will be fixed in 1.2.0-rc1 which will be out very soon.

There's a bug filled and associated fix over in bugs if you can't wait.

Alex

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer

Revision history for this message
kobus44 (kobus44) said :
#2

Thanks, tried to solution offered in the bug, but no dice. Will revert back to the old database. Too bad...

Revision history for this message
Alex Harrington (alexharrington) said :
#3

Your server will need to be listening on port 8080 as well as 80 internally as it has to call its own methods on the web service.

Alex

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer

Revision history for this message
kobus44 (kobus44) said :
#4

Still, I will wait for the next update where this bug is properly addressed in the hard code. 1.1.0 was rock solid anyway so no biggie going back...