New install for both Zimbra Talk and ZCS 8.6P7.
I got 503 error after login to Zimbra. I tried change nginx config but it does not help. Anything else to check.
Error 503
- DualBoot
- Elite member
- Posts: 1326
- Joined: Mon Apr 18, 2016 8:18 pm
- Location: France - Earth
- ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
- Contact:
Re: Error 503
it seems you have a difference between what you see and what you really get.
Network traces show 404 error "proxy?target=https..."
I think you should check the target the proxy try to join.
Network traces show 404 error "proxy?target=https..."
I think you should check the target the proxy try to join.
The Guy - DualBoot
PostMaster - WikiMaster - SysAdmin
"Free Your Mind. Think Open Source"
april.org
Zetalliance Member - zetalliance.org
PostMaster - WikiMaster - SysAdmin
"Free Your Mind. Think Open Source"
april.org
Zetalliance Member - zetalliance.org
- jorgedlcruz
- Zimbra Alumni
- Posts: 2782
- Joined: Thu May 22, 2014 4:47 pm
Re: Error 503
Are you using a valid SSL on the Zimbra Talk server?
Have you configured properly the Proxy part on Zimbra?
Best regards
Have you configured properly the Proxy part on Zimbra?
Best regards
Re: Error 503
I use commercial wildcard certificate. Proxy enable as instruction.
I got some error from prosody.log
Jul 27 21:15:03 s2sout24f4a90 info Sending error replies for 1 queued stanzas because of failed outgoing connection to inet.co.th
Jul 27 21:15:10 s2sin19fd2e0 info Incoming s2s stream focus.inet.co.th->inet.co.th closed: This host does not serve inet.co.th
Jul 27 21:15:10 s2sout175b7f0 info Session closed by remote with error: host-unknown (This host does not serve inet.co.th)
Jul 27 21:15:10 s2sout175b7f0 info Outgoing s2s stream focus.inet.co.th->inet.co.th closed: host-unknown (This host does not serve inet.co.th)
on zimbra server domain name mail0.inet.co.th user e-mail is user@mail0.inet.co.th
I got some error from prosody.log
Jul 27 21:15:03 s2sout24f4a90 info Sending error replies for 1 queued stanzas because of failed outgoing connection to inet.co.th
Jul 27 21:15:10 s2sin19fd2e0 info Incoming s2s stream focus.inet.co.th->inet.co.th closed: This host does not serve inet.co.th
Jul 27 21:15:10 s2sout175b7f0 info Session closed by remote with error: host-unknown (This host does not serve inet.co.th)
Jul 27 21:15:10 s2sout175b7f0 info Outgoing s2s stream focus.inet.co.th->inet.co.th closed: host-unknown (This host does not serve inet.co.th)
on zimbra server domain name mail0.inet.co.th user e-mail is user@mail0.inet.co.th
-
- Posts: 1
- Joined: Tue Nov 08, 2016 10:13 pm
Re: Error 503
Hi,
I have the same error such as the picture, how i can configure the proxy target?
¿Can you help me with this?
Regards.
I have the same error such as the picture, how i can configure the proxy target?
¿Can you help me with this?
Regards.
Re: Error 503
Hi,
The error in the picture is clearly a misconfiguration. The actual target parameter in these calls is determined from what you configure in Admin UI for Zimbra Talk Zimlet. This is what is shown at the end of the talk server installation.
The cause for these calls returning a 404 is one of these:
- zimbra mailboxd is not able to resolve the hostname of the talk server
- zimbra mailboxd is not able to connect to the talk server
- the talk server does not use certificate trusted by zimbra mailboxd
- the setting for zimbraProxyAllowedDomains was not done correctly (chech your COS!)
- zimbra mailboxd is configured to use some proxy that is not able to connect to the talk server
The error in the picture is clearly a misconfiguration. The actual target parameter in these calls is determined from what you configure in Admin UI for Zimbra Talk Zimlet. This is what is shown at the end of the talk server installation.
The cause for these calls returning a 404 is one of these:
- zimbra mailboxd is not able to resolve the hostname of the talk server
- zimbra mailboxd is not able to connect to the talk server
- the talk server does not use certificate trusted by zimbra mailboxd
- the setting for zimbraProxyAllowedDomains was not done correctly (chech your COS!)
- zimbra mailboxd is configured to use some proxy that is not able to connect to the talk server