# Cannot enable historian core via Docker **URL:** \ **Category:** Ignition\ **Tags:** vision, ignition83, perspective\ **Created:** [December 3, 2025, 8:14pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602 "2025-12-03T20:14:52Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ejaegler](https://avatars.discourse-cdn.com/v4/letter/e/df788c/32.png) [@ejaegler](https://forum.inductiveautomation.com/u/ejaegler)\ **Post date:** [December 3, 2025, 8:14pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/1 "2025-12-03T20:14:52Z")
```python version: '2.4' services: ignition: build: context: ignition args: IGNITION_VERSION: 8.3.1 ports: - 80:8088 - 443:8043 - 8060:8060 volumes: - ignition-data:/usr/local/bin/ignition/data cap_add: - SYS_RAWIO - CAP_NET_BIND_SERVICE - CAP_NET_RAW environment: - ACCEPT_IGNITION_EULA=Y - IGNITION_EDITION=standard - TZ=America/Chicago - GATEWAY_MODULES_ENABLED=com.inductiveautomation.opcua.drivers.ablegacy,com.inductiveautomation.eam,com.inductiveautomation.opcua.drivers.logix,com.inductiveautomation.opcua,com.inductiveautomation.symbol-factory,com.inductiveautomation.opcua.drivers.tcpudp,com.inductiveautomation.vision,web-browser,com.inductiveautomation.historian,com.inductiveautomation.perspective,com.inductiveautomation.historian.sql - DISABLE_QUICKSTART=true - GATEWAY_ADMIN_USERNAME=admin - GATEWAY_ADMIN_PASSWORD=password command: > -m 4096 -- gateway.resolveHostNames=true -Dignition.license.leased-activation-terminate-sessions-on-shutdown=true volumes: ignition-data: ``` I am having an issue with enabling the historian core for 8.3.x in a docker environment. I have com.inductiveautomation.historian added for the gateway\_modules\_enabled. When I click on enable module ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/8/d829e2370a4642dc22321ea05716d340459e8b4d.png) I get the following error message: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/a/1a232f2567fb1ffc3deaa6aa284e46539edea09c.png) I downloaded the module from the inductive website, restarted the gateway, and I still get the same error. Any help would be greatly appreciated. ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [December 3, 2025, 9:05pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/2 "2025-12-03T21:05:25Z")
Can you show us the logs on the gateway? ---
**Author:** ![ejaegler](https://avatars.discourse-cdn.com/v4/letter/e/df788c/32.png) [@ejaegler](https://forum.inductiveautomation.com/u/ejaegler)\ **Post date:** [December 3, 2025, 9:28pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/3 "2025-12-03T21:28:55Z")
[Ignition-dc03](https://forum.inductiveautomation.com/uploads/short-url/8wGq0SYrHSPUaLhmN5zAAMbW3qU.idb) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/e/aec537a5010674728dc498091355f848d3528462.png) [dc2ce34c\_Ignition\_logs\_20251203-1527.idb](https://forum.inductiveautomation.com/uploads/short-url/8wGq0SYrHSPUaLhmN5zAAMbW3qU.idb) (132 KB) ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [December 3, 2025, 9:33pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/4 "2025-12-03T21:33:49Z")
That looks like you are having authentication issues on the gateway, have you got an LDAP connection set up that is not working? ---
**Author:** ![ejaegler](https://avatars.discourse-cdn.com/v4/letter/e/df788c/32.png) [@ejaegler](https://forum.inductiveautomation.com/u/ejaegler)\ **Post date:** [December 3, 2025, 9:49pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/5 "2025-12-03T21:49:21Z")
> [@David\_Stone](#): > > LDAP connection I do not have an LDAP connections that I know of. I am using the default system identity provider ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [December 3, 2025, 9:58pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/6 "2025-12-03T21:58:11Z")
`Bad IPv6Address: [[${jndi:ldap://10.12.54.58:54491/nessus}]]` This is the bit that I'm getting that detail from. Somewhere your system has a bad hostname/path configured. `Bad Authority: [5eaed2c.jville.com/..]` I am also interested in this entry too, does this resemble part of a config you have set up? ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [December 4, 2025, 6:30pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/7 "2025-12-04T18:30:43Z")
One aspect with use of `GATEWAY_MODULES_ENABLED` env var with Ignition 8.3 is that you're basically enforcing the set of enabled modules--enabling or disabling a given module from the UI is blocked. Enable/disable of modules is now retained in the `data/modules.json` configuration file, so use of this env var is no longer needed to enforce loading of modules (which in 8.1 was based on mere presence of the module file on the filesystem). If you want to be able to control which modules are enabled/disabled, you can omit specifying `GATEWAY_MODULES_ENABLED`. Since the config is now persisted in your `data` volume, container lifecycle events will no longer have disabled modules come "back to life" like would happen in `8.1` without `GATEWAY_MODULES_ENABLED`. Starting a "stock" `inductiveautomation/ignition:8.3.1` container with your `GATEWAY_MODULES_ENABLED` does result in Historian Core and Historian SQL modules being enabled: ![SCR-20251204-lesf](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/b/cb64e9ceedbcc693bfa1b595e1b37599e5970487.png) ---
**Author:** ![ejaegler](https://avatars.discourse-cdn.com/v4/letter/e/df788c/32.png) [@ejaegler](https://forum.inductiveautomation.com/u/ejaegler)\ **Post date:** [December 5, 2025, 4:03pm UTC](https://forum.inductiveautomation.com/t/cannot-enable-historian-core-via-docker/112602/8 "2025-12-05T16:03:58Z")
Thanks for the on this issue today Kevin. There were persistent environmental variables that were over riding what was being stated in the docker compose file.