# What Happened To 8.1.8

**URL:** <https://forum.inductiveautomation.com/t/what-happened-to-8-1-8/49714>\
**Category:** Ignition\
**Created:** [August 9, 2021, 5:27pm UTC](https://forum.inductiveautomation.com/t/what-happened-to-8-1-8/49714 "2021-08-09T17:27:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![boeked](https://avatars.discourse-cdn.com/v4/letter/b/5e9695/32.png) [@boeked](https://forum.inductiveautomation.com/u/boeked)\
**Post date:** [August 9, 2021, 5:27pm UTC](https://forum.inductiveautomation.com/t/what-happened-to-8-1-8/49714/1 "2021-08-09T17:27:12Z")

</div>

What happened to the 8.1.8 release from last week (8/2/2021)? It appears to be removed from the website. If it was removed for quality reasons similar to 8.1.6 it is deeply concerning about IA’s ability to test updates before release. From a system integrator perspective, it doesn’t look good for the quality of the product we are trying to sell from IA when patches keep getting removed. I have a customer that was targeting 8.1.8 for a patch to a production system. I now have to get back and say we need to use 8.1.9. I am sure that will bring up a discussion of what happened to 8.1.8.

The fortunate thing of this is I was giving time before we applied the patch, waiting to see if what happened with 8.1.6 happens to 8.1.8. It appears that it has.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 9, 2021, 5:28pm UTC](https://forum.inductiveautomation.com/t/what-happened-to-8-1-8/49714/2 "2021-08-09T17:28:29Z")

</div>

> [@8.1.8 LTS Pulled, 8.1.9 Emergency Release](https://forum.inductiveautomation.com/t/8-1-8-lts-pulled-8-1-9-emergency-release/49670):
>
> After 8.1.8’s release, we found a fairly severe regression. As a result we’ve pulled version 8.1.8 from our website, and released version 8.1.9 as a patch for the issue. The Issue Upgrading to version 8.1.8 would reset the gateway’s HTTP, HTTPS, and Metro ports back to their default values (8088, 8043, and 8060, respectively). This is not intended behavior. Workaround If a system has already been upgraded, then any ports there were not set to the default values before the upgrade need to be …