# \[IGN-7019\] HTTP ERROR 400 Invalid SNI **URL:** \ **Category:** Ignition Early Access\ **Tags:** perspective\ **Created:** [January 10, 2023, 3:46pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432 "2023-01-10T15:46:43Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [January 10, 2023, 3:46pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/1 "2023-01-10T15:46:43Z")
Just jumped a staging server up to the 8.1.25 nightly 2023-01-09 snapshot and every HTTPS access is getting SNI errors. In the wrapper logs I see this: ```python INFO | jvm 1 | 2023/01/10 15:38:20 | W [o.e.j.s.HttpChannel] [15:38:20]: handleException /data/perspective/runnable-projects org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI ``` In the browser I see this: ## HTTP ERROR 400 Invalid SNI | URI: | /web | | --- | --- | | STATUS: | 400 | | MESSAGE: | Invalid SNI | | SERVLET: | - | | CAUSED BY: | org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI | ### Caused by: `org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:266) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:207) at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:501) at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100) at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:558) at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:379) at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:146) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100) at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:416) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:385) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:272) at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:140) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:934) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1078) at java.base/java.lang.Thread.run(Unknown Source)` In our case I am accessing the system via alternate DNS names that do not match the certificate, but this has not been an issue like this before. Going to roll back the staging server for now, but was hoping for some feedback if this is a known issue or there is a workaround so I can decide how to approach this upgrade again in the future. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 10, 2023, 4:18pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/2 "2023-01-10T16:18:10Z")
What version are you upgrading from? ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [January 10, 2023, 4:20pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/3 "2023-01-10T16:20:11Z")
8.1.22 ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 10, 2023, 4:26pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/4 "2023-01-10T16:26:09Z")
We're looking at this, but right now it seems that the Jetty upgrade we did for 8.1.25 may have enabled SNI by default. ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [January 11, 2023, 5:47pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/5 "2023-01-11T17:47:57Z")
This issue should be fixed in the latest early access build. See: [Nightly 8.1 Changelogs - 2022 - #187 by sreis](https://forum.inductiveautomation.com/t/nightly-8-1-changelogs-2022/54636/187) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 11, 2023, 5:59pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/6 "2023-01-11T17:59:59Z")
Time to start a 2023 changelog topic? ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [January 11, 2023, 6:04pm UTC](https://forum.inductiveautomation.com/t/ign-7019-http-error-400-invalid-sni/68432/7 "2023-01-11T18:04:33Z")
Oh yeah, probably. I've let Sabrina know 👍