# Errors from browsers with ssl\_session\_tickets off (nginx) **URL:** \ **Category:** Server\ **Created:** [July 20, 2016, 12:58pm UTC](https://community.letsencrypt.org/t/errors-from-browsers-with-ssl-session-tickets-off-nginx/18124 "2016-07-20T12:58:45Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Overlord](https://avatars.discourse-cdn.com/v4/letter/o/ecc23a/32.png) [@Overlord](https://community.letsencrypt.org/u/Overlord)\ **Post date:** [July 28, 2016, 8:11pm UTC](https://community.letsencrypt.org/t/errors-from-browsers-with-ssl-session-tickets-off-nginx/18124/5 "2016-07-28T20:11:09Z")
I’m posting this here both because this question was recently asked and because it took me many hours of troubleshooting to figure out the issue as while I found several references to the problem on Google, no one seemed to have a real solution. So here it is: ssl\_session\_tokens off breaks if it’s not set the same for all ssl-enabled server{} blocks. So if you have 2 server configurations and and you have ssl\_server\_tokens set to on in one (which is the default so it counts even if you omit it) and set to off in another, it will break the one where it’s set to off in certain browsers. The easiest way to resolve this, unless you have multiple http{} blocks, is to just set it to off in the http{} block. I have not tested to see if you you can have different settings in different http{} blocks as I haven’t had need to set up more than one http{} block. For others looking for this issue, I want to add that Chrome will respond with: ERR\_SSL\_PROTOCOL\_ERROR while Firefox responds with: SSL\_ERROR\_RX\_UNEXPECTED\_NEW\_SESSION\_TICKET and curl responds with: gnutls\_handshake() failed: An unexpected TLS packet was received. IE seemed to work, surprisingly. --- _[View the full topic](https://community.letsencrypt.org/t/errors-from-browsers-with-ssl-session-tickets-off-nginx/18124)._