# Ignition 8 char licence for use in Dockerised instances

**URL:** <https://forum.inductiveautomation.com/t/ignition-8-char-licence-for-use-in-dockerised-instances/95072>\
**Category:** Ignition\
**Created:** [August 23, 2024, 11:22am UTC](https://forum.inductiveautomation.com/t/ignition-8-char-licence-for-use-in-dockerised-instances/95072 "2024-08-23T11:22:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![batman01793](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@batman01793](https://forum.inductiveautomation.com/u/batman01793)\
**Post date:** [August 23, 2024, 11:22am UTC](https://forum.inductiveautomation.com/t/ignition-8-char-licence-for-use-in-dockerised-instances/95072/1 "2024-08-23T11:22:23Z")

</div>

Hi I have a few questions about the new key type I will be using if I move my servers to a Dockerised set up.  
I understand that my licence key will be a new version consisting of 8 chars not 6 anymore.  
I understand the need for this so that I only host 1 version of the same licence on a dockerised instance - so makes sense.  
I have a few questions about the licence server that checks for the activation status & keeps my ignition instances live.  
1: what port does the licence check need to use to complete its check?  
2: is there a redundancy in IA's licence checking servers so if there is a problem a replacement spools up etc - so my plant does not experiance downtime  
3: what is the checking frequency for the license ?

I will be building dockerised instances of Highbyte & Ignition to enable easy deploy and recovery when setting up new sites - also to easily manage ignition version updates with AWS. I just want to understand a little better the ports and the risks of moving away from the static license file to a live version that checks for validity over X period of time.