This started to happen after I emptied the cache. As stated in my previous reply, I now get asked for credentials. The current situation is a little bit different now. (Yep, unfortunately I had already looked at the article you provided). In fact there have never been any errors visible there It had no effect though…Īnd no, no errors on the stats page. I tried extending both server and client timeout values to 30min. #stick-table type ip size 200k expire 30m # bind x.x.x.x:143 name imap # Not allowing unencrypted imap. # No need to Load Balance port 587 and 465.
Option httpchk GET /microsoft-server-activesync/healthcheck.htmīind x.x.x.x:25 name smtp # VIP-IP, port not open to the public internet, only against Postfix Server ex2 2.2.2.2:443 check ssl inter 15s verify required ca-file /etc/ssl/certs/ca-bundle.crt Server ex1 1.1.1.1:443 check ssl inter 15s verify required ca-file /etc/ssl/certs/ca-bundle.crt Option httpchk GET /autodiscover/healthcheck.htm Use_backend be_ex2013_autodiscover if autodiscover Redirect scheme https code 301 if ! # redirect 80 -> 443 (for owa)Īcl eas url_beg /Microsoft-Server-ActiveSync Http-response set-header X-Content-Type-Options nosniffīind *:443 ssl crt /etc/ssl/certs/exchange_certificate_and_key_nopassword.pem Http-response set-header X-Frame-Options SAMEORIGIN # http-response set-header Strict-Transport-Security max-age=31536000 \ includeSubdomains \ preload Ssl-default-server-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!MD5:!DSS Ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!MD5:!DSS Could someone plz take a look at the following configuration file and tell me some good advice, thanks! global I’ve been playing with timeout client and timeout server options to no avail. In other words, everything looks normal (I just get disconnected for some reason) I’ve been looking at haproxy.log, but at the time of the disconnect there’s just no (new) information to be found there. (Windows Outlook works just fine, no problems there). I then get automatically connected again for a while, and the same thing happens over and over again. If I start Outlook for Mac it works just fine for a minute or two, but after that I just get disconnected from the Exchange server. In other words, the EWS protocol in Exchange seem to have problems with my config file and I can’t figure out why. The thing is, everything works fine with HAp and Exchange 2013 EXCEPT Outlook (2016) for MAC. I’ve been scratching my head with this problem for far too long now.
0 kommentar(er)
