[SOLVED] WebEx Zimlet stopped working after upgrade

[markosulake]

I noticed that there was a newer version of WebEx Zimlet available. So I decided to undeploy current WebEx Zimlet 2.1.1 and deploy the newer 2.4 version, but after this I've not been able to validate my WebEx host account anymore.

When I go to Zimlets -> WebEx -> Manage Accounts -> Validate Account 1, I get "Test failed. This WebEx account is not valid.", and the only option is to click Ok. When I do that, I'll get a bit more detailed error message saying "Error parsing WebEx XML response or malformed XML". I'll attach screenshots.

I've now tried to undeploy/deploy three latest versions of WebEx Zimlet and they all are giving me now that same error. I've checked that my WebEx account is really working and is not locked or anything. The first time that I deployed version 2.4 of the Zimlet I didn't have "flush cache" checked, could that've something to do with this?

Any ideas what I could do?

Thanks!

[markosulake]

Any help on this would be really appreciated! How could I start debugging this on my own?

[ELam]

Well! I also encountered the same problem.

Nevertheless, I have not installed any WebEX Zimlet before. Version 2.4 is my first installation. Thus, I guess the problem not caused by "Flush Cache"

Anybody can provide help?? Thanks a lot

[tdesorbaix]

By looking at the error you show in the attached image, it seems that the proxy is trying to access a domain not allowed by the CoS.


You can check the allowed domains by the CoS with the following command :

zmprov gc YOURCOS | grep zimbraProxyAllowedDomains

If your webex domain is not allowed, you can add it with the following command :

zmprov mc YOURCOS +zimbraProxyAllowedDomains YOURDOMAIN

[ELam]

Thanks for your information, we have added the domain name onto the list or proxy and listed as below. Nevertheless, it still not work. I wish to see if I needed to re-deploy the Zimlet or restart the server (or service) before the revision comes into effective?

By the meantime, I wish to see if WebEx Support no longer Zimbra access?

##################################################
zimbraProxyAllowedDomains: api.tr.im
zimbraProxyAllowedDomains: *.webex.com
zimbraProxyAllowedDomains: twitter.com
zimbraProxyAllowedDomains: *.twitter.com
zimbraProxyAllowedDomains: *.facebook.com
zimbraProxyAllowedDomains: api.bit.ly
zimbraProxyAllowedDomains: *.tweetmeme.com
zimbraProxyAllowedDomains: *.digg.com
##################################################

[ELam]

Originally Posted by ELam

Thanks for your information, we have added the domain name onto the list or proxy and listed as below. Nevertheless, it still not work. I wish to see if I needed to re-deploy the Zimlet or restart the server (or service) before the revision comes into effective?

By the meantime, I wish to see if WebEx Support no longer Zimbra access?

##################################################
zimbraProxyAllowedDomains: api.tr.im
zimbraProxyAllowedDomains: *.webex.com
zimbraProxyAllowedDomains: twitter.com
zimbraProxyAllowedDomains: *.twitter.com
zimbraProxyAllowedDomains: *.facebook.com
zimbraProxyAllowedDomains: api.bit.ly
zimbraProxyAllowedDomains: *.tweetmeme.com
zimbraProxyAllowedDomains: *.digg.com
##################################################

Thanks for the provided information. I eventually according to the information and fix the problem. The WebEx can be connected successfully.