You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A way to fix this after install is to do something like (for both spamrl and api hostname):
for i in `zmprov gac`; do zmprov mc $i +zimbraProxyAllowedDomains *.spamrl.com; done
for i in `zmprov gac`; do zmprov mc $i +zimbraProxyAllowedDomains *.api.hostname.tld; done
This should be incorporated into the addon to check/adjust
If you have multiple COS (Class of Service) objects setup, then reporting spam or accessing the interface, results in a proxy error:
HTTP ERROR 403 Problem accessing /service/proxy. Reason Forbidden)
You can verify this by looking in the access logs:
/opt/zimbra/log/nginx.access.log
63182:1.2.3.4:59520 - [email protected] [07/Mar/2017:10:14:16 -0300] "POST /service/proxy?target=https://api.hostname.tld/api/authticket/create/username/[email protected] HTTP/1.1" 403 462 "http://webmail.host.tld/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0" "127.0.0.1:8080"
A way to fix this after install is to do something like (for both spamrl and api hostname):
This should be incorporated into the addon to check/adjust
https://wiki.zimbra.com/wiki/Zimlet_Developers_Guide:Proxy_Servlet_Setup
The text was updated successfully, but these errors were encountered: