I have Multi-server Setup.
I have multiple domains being a Zimbra Hosting Provider.
I installed Zimbra Talk to the letter.
I configured the Zimbra Talk Admin Zimlet fine.
I deployed the Zimbra Talk zimlet to both of my mailbox servers (they installed fine).
I enabled the zimlet to one domain for testing.
When I login wityh a user on that domain, I get an error from the Zimbra Talk Zimlet:
An error occurred while initializing the zimlet "biz_zcs_vnc_talk_zimlet". Please notify administrator.
SyntaxError: Unexpected token < in JSON at position 1
Also noticed that if I run the Prosody (update-prosody-conf) script file, I get some errors too:
zimbraDefaultDomainName: mydomain.net
updating domains in ini from ldap
updated Rosterfilter for Domain mydomain.net
./update-prosody-conf: line 141: [: missing `]'
updated Rosterfilter for Domain mydomain.com
./update-prosody-conf: line 141: [: missing `]'
I performed various tests such as connecting to the Zimbra Talk server usung: https://xmpp.mydomain.tld/http-bind and it responds:
It works! Now point your BOSH client to this URL to connect to Prosody.
I assume Prosody is working fine.
Any help will be appreciated.
Regards,
Dennis
Error initializing Zimbra Talk zimlet on domain user
-
- Posts: 6
- Joined: Thu Sep 29, 2016 4:08 pm
Re: Error initializing Zimbra Talk zimlet on domain user
same error here but single server environment, attached is the snapshot.
please help
please help
Re: Error initializing Zimbra Talk zimlet on domain user
we have the same error on our single server environment
Re: Error initializing Zimbra Talk zimlet on domain user
Hi,
what you see is that for some call instead of the expected JSON value the backend returned some xml. This mostly happens when the zimbra proxy customization is not done correctly.
Please see https://wiki.zimbra.com/wiki/How_to_Ins ... y_settings
In addition - please restart the zimbra proxy after running zmproxyconfgen.
what you see is that for some call instead of the expected JSON value the backend returned some xml. This mostly happens when the zimbra proxy customization is not done correctly.
Please see https://wiki.zimbra.com/wiki/How_to_Ins ... y_settings
In addition - please restart the zimbra proxy after running zmproxyconfgen.