# \[IGN-13832\] Ignition Docker Image at Kubernetes with Error to show the projects

**URL:** <https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168>\
**Category:** Ignition 8.3 Early Access\
**Tags:** perspective\
**Created:** [July 30, 2025, 8:08pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168 "2025-07-30T20:08:36Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![AGDC04](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/agdc04/32/6366_2.png) [@AGDC04](https://forum.inductiveautomation.com/u/AGDC04)\
**Post date:** [July 30, 2025, 8:08pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/1 "2025-07-30T20:08:36Z")

</div>

Hello!,

I'm testing the Kubernetes integration with the Docker Image.  
I'm able to deploy and use the gateway, but when try to open the Launch page for Perspective projects have this error:

com.inductiveautomation.perspective.gateway.comm.Routes$MissingGatewayAddressException

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/a/1a6b8901c727acd348ab1e4123e1915381a0ba00.png)

I'm able to open the project by the link on perspective with no issue just the Gateway page not show the projects.

Using Ingress with Nginx to access the internal service, gateway is not using TLS, only at Ingress have TLS

```python
com.inductiveautomation.perspective.gateway.comm.Routes$MissingGatewayAddressException: null

at com.inductiveautomation.perspective.gateway.comm.Routes.getRunnableProjects(Routes.java:1854)

at com.inductiveautomation.ignition.gateway.dataroutes.Route.service(Route.java:361)

at com.inductiveautomation.ignition.gateway.dataroutes.RouteGroupImpl.service(RouteGroupImpl.java:120)

at com.inductiveautomation.ignition.gateway.dataroutes.RouteGroupCollectionServlet.serviceInternal(RouteGroupCollectionServlet.java:133)

at com.inductiveautomation.ignition.gateway.dataroutes.AbstractRouteGroupServlet.service(AbstractRouteGroupServlet.java:40)

at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:614)

at org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1379)

at org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)

at org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1614)

at com.inductiveautomation.catapult.filters.GatewayFilter.doFilter(GatewayFilter.java:116)

at jakarta.servlet.http.HttpFilter.doFilter(HttpFilter.java:97)

at org.eclipse.jetty.ee10.servlet.FilterHolder.doFilter(FilterHolder.java:208)

at org.eclipse.jetty.ee10.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1586)

at org.eclipse.jetty.ee10.servlet.ServletHandler$MappedServlet.handle(ServletHandler.java:1547)

at org.eclipse.jetty.ee10.servlet.ServletChannel.dispatch(ServletChannel.java:819)

at org.eclipse.jetty.ee10.servlet.ServletChannel.handle(ServletChannel.java:436)

at org.eclipse.jetty.ee10.servlet.ServletHandler.handle(ServletHandler.java:464)

at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:575)

at org.eclipse.jetty.ee10.servlet.SessionHandler.handle(SessionHandler.java:717)

at org.eclipse.jetty.server.handler.ContextHandler.handle(ContextHandler.java:1060)

at org.eclipse.jetty.rewrite.handler.RewriteHandler$LastRuleHandler.handle(RewriteHandler.java:159)

at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)

at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)

at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)

at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)

at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)

at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)

at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)

at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)

at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)

at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:143)

at org.eclipse.jetty.server.Handler$Sequence.handle(Handler.java:805)

at org.eclipse.jetty.server.Handler$Sequence.handle(Handler.java:805)

at org.eclipse.jetty.server.Server.handle(Server.java:182)

at org.eclipse.jetty.server.internal.HttpChannelState$HandlerInvoker.run(HttpChannelState.java:662)

at org.eclipse.jetty.server.internal.HttpConnection.onFillable(HttpConnection.java:418)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:322)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:99)

at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:478)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:441)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:293)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.run(AdaptiveExecutionStrategy.java:201)

at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:311)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:979)

at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1209)

at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1164)

at java.base/java.lang.Thread.run(Unknown Source)

```

---

<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:** [July 30, 2025, 9:14pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/2 "2025-07-30T21:14:26Z")

</div>

I think the mixed negotiation is what's confusing things.

If we're detecting the incoming request as secure (via HTTPS protocol) but you don't have any HTTPS settings configured, you'll get that error:

```python
if (!req.getRequest().isSecure() && settings.httpPort().isPresent()) {
    gatewayAddress = new HttpURL(
        "http", settings.address(), settings.httpPort().getAsInt(), null).toString();
} else if (settings.httpsPort().isPresent()) {
    gatewayAddress = new HttpURL(
        "https", settings.address(), settings.httpsPort().getAsInt(), null).toString();
} else {
    throw new MissingGatewayAddressException();
}

```

I don't know if there's some better way to have the traffic show up as HTTP to the Ignition gateway while still negotiating as HTTPS outside of Kubernetes. @kcollins might 😃

---

<div class="post-metadata">

**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:** [July 30, 2025, 10:13pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/3 "2025-07-30T22:13:41Z")

</div>

If it is sitting behind an Ingress, you'll probably want to:

1. Configure your public address settings in Ignition.
2. Supply `gateway.useProxyForwardedHeader=true` gateway arg after reading [this](https://docs.inductiveautomation.com/docs/8.3/platform/gateway/web-interface/network/web-server-settings#use-proxy-forwarded-headers-explained).

Number 2 there will bridge the gap of communicating to Ignition that you're terminating TLS upstream.

---

<div class="post-metadata">

**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:** [July 30, 2025, 10:15pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/4 "2025-07-30T22:15:22Z")

</div>

Bonus: the Helm Chart we're working on will make it relatively easy to use the same `Secret` that is linked to your Ingress for TLS termination with the Gateway web server for end-to-end encryption without a lot of setup headaches. Stay tuned!

---

<div class="post-metadata">

**Author:** ![AGDC04](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/agdc04/32/6366_2.png) [@AGDC04](https://forum.inductiveautomation.com/u/AGDC04)\
**Post date:** [July 31, 2025, 10:24am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/5 "2025-07-31T10:24:31Z")

</div>

Interesting, I use the same settings for 8.1.48 gateways, today I manage around 9 Gateways using the same settings, so I created a new deploy with the new 8.3 to check the changes. They have the proxy forwarded header, but the public address is auto. I'll try to setup the public address with the right link first and if not work also create a certificate for the gateway. @kcollins I'm using most of the scripts you build for the ICC and the unofficial docker image repo for some scripting to automate a few task, thanks for all the work building that scripts.

---

<div class="post-metadata">

**Author:** ![AGDC04](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/agdc04/32/6366_2.png) [@AGDC04](https://forum.inductiveautomation.com/u/AGDC04)\
**Post date:** [July 31, 2025, 11:35am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/6 "2025-07-31T11:35:11Z")

</div>

Just a missing comment, Everything works except the Perspective Launch page app/home/perspective/session-launcher

---

<div class="post-metadata">

**Author:** ![AGDC04](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/agdc04/32/6366_2.png) [@AGDC04](https://forum.inductiveautomation.com/u/AGDC04)\
**Post date:** [August 1, 2025, 11:02am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/7 "2025-08-01T11:02:36Z")

</div>

Appling a TLS at the Gateway Web Settings worked. Now the Launch Page is loading correctly

---

<div class="post-metadata">

**Author:** ![Marco\_Keller](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Marco\_Keller](https://forum.inductiveautomation.com/u/Marco_Keller)\
**Post date:** [August 4, 2025, 7:36am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/8 "2025-08-04T07:36:53Z")

</div>

I am experiencing the same issue, but I am using Docker with Traefik as a reverse proxy, which handles the certificates and terminates the HTTPS connection. The connection between Traefik and Ignition is not encrypted (port 8088). Therefore, I am unable to set up TLS in Ignition because the certificates are managed by Traefik.  
This works perfectly in Ignition 8.1 without a TLS setup, but the problem occurs in 8.3.  
(Forwarded headers are enabled and the public address and ports are set.)

Is there an alternative to the TLS setup in Ignition to avoid this problem?

---

<div class="post-metadata">

**Author:** ![AGDC04](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/agdc04/32/6366_2.png) [@AGDC04](https://forum.inductiveautomation.com/u/AGDC04)\
**Post date:** [August 4, 2025, 11:06am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/9 "2025-08-04T11:06:59Z")

</div>

Some years ago I have a Docker deployment, but on this case is using the nginx and lets encrypt images to manage the certificate

```python
version: "3.7"

services:

    reverse-proxy:
        image: "jwilder/nginx-proxy:latest"
        container_name: "reverse-proxy"
        volumes:
            - "html:/usr/share/nginx/html"
            - "dhparam:/etc/nginx/dhparam"
            - "vhost:/etc/nginx/vhost.d"
            - "certs:/etc/nginx/certs"
            - "/run/docker.sock:/tmp/docker.sock:ro"
            - "acme:/etc/acme.sh"
            - "/home/ubuntu/ignition/Nginx/proxy.conf:/etc/nginx/proxy.d/proxy.conf:ro"
            - "/home/ubuntu/ignition/Nginx/my_proxy.conf:/etc/nginx/conf.d/my_proxy.conf:ro"
        restart: "unless-stopped"
        networks:
            - "net"
        ports:
            - "80:80"
            - "443:443"
    letsencrypt:
        image: "jrcs/letsencrypt-nginx-proxy-companion:latest"
        container_name: "letsencrypt-helper"
        volumes:
            - "html:/usr/share/nginx/html"
            - "dhparam:/etc/nginx/dhparam"
            - "vhost:/etc/nginx/vhost.d"
            - "certs:/etc/nginx/certs"
            - "/run/docker.sock:/var/run/docker.sock:ro"
            - "acme:/etc/acme.sh"
        environment:
            NGINX_PROXY_CONTAINER: "reverse-proxy"
            DEFAULT_EMAIL: "email@domain.com"
        restart: "unless-stopped"
        depends_on:
            - "reverse-proxy"
        networks:
            - "net"
    ignition-home:
        image: "kcollins/ignition:latest"
        container_name: "ignition-home"
        stop_grace_period: "30s"
        secrets:
           - "gateway-password"
        volumes:
           - "gateway-data:/var/lib/ignition/data"
           - "/home/ubuntu/ignition/Modules:/modules"
           - "/home/ubuntu/ignition/JDBC:/jdbc"
        logging:
            driver: "json-file"
            options:
               max-size: "200k"
               max-file: "10"
        environment:
            ACCEPT_IGNITION_EULA: "Y"
            GATEWAY_SYSTEM_NAME: "ignition-home"
            IGNITION_EDITION: "maker"
            TZ: "America/Sao_Paulo"
            IGNITION_LICENSE_KEY: "LICENSE"
            IGNITION_ACTIVATION_TOKEN: "ACTIVATION"
            GATEWAY_ADMIN_USERNAME: "ADMIN"
            GATEWAY_ADMIN_PASSWORD_FILE: "/run/secrets/gateway-password"
            GATEWAY_HTTP_PORT: "8088"
            GATEWAY_HTTPS_PORT: "8043"
            GATEWAY_MODULES_ENABLED: "alarm-notification,allen-bradley-drivers,logix-driver,modbus-driver-v2,omron-driver,opc-ua,perspective,reporting,serial-support-gateway,sfc,siemens-drivers,sql-bridge,tag-historian,udp-tcp-drivers,web-developer"
            GATEWAY_MODULE_RELINK: "true"
            GATEWAY_JDBC_RELINK: "true"
            GATEWAY_PUBLIC_ADDRESS: "localhost"
            GATEWAY_PUBLIC_HTTP_PORT: "9088"
            GATEWAY_PUBLIC_HTTPS_PORT: "9043"
            GATEWAY_MAX_MEMORY: "4096"
            GATEWAY_SKIP_COMMISSIONING: "0"
            VIRTUAL_HOST: "domain.com"
            LETSENCRYPT_HOST: "domain.com"
            LETSENCRYPT_EMAIL: "email@domain.com"
            VIRTUAL_PORT: "8088"
        restart: "unless-stopped"
        depends_on:
             - "reverse-proxy"
        networks:
             - "net"
        command: >
           -- gateway.resolveHostNames=false gateway.useProxyForwardedHeader=true
        ports:
            - "1521:1521"

    db:
         image: mysql:latest
         container_name: "ignition-db"
         volumes:
             - "db_data:/var/lib/mysql"
         logging:
             driver: "json-file"
             options:
                max-size: "200k"
                max-file: "10"
         secrets:
             - "mysql-root-password"
             - "mysql-password"
         environment:
             MYSQL_ROOT_PASSWORD_FILE: "/run/secrets/mysql-root-password"
             MYSQL_DATABASE: "ignition"
             MYSQL_USER: "ignition"
             MYSQL_PASSWORD_FILE: "/run/secrets/mysql-password"
         networks:
             - "net"
secrets:
   mysql-root-password:
      file: ./secrets/MYSQL_ROOT_PASSWORD
   mysql-password:
      file: ./secrets/MYSQL_PASSWORD
   gateway-password:
      file: ./secrets/GATEWAY_PASSWORD

volumes:
  certs:
  html:
  vhost:
  dhparam:
  acme:
  gateway-data:
  db_data:
networks:
  net:
    external: true

```

May help this image from jrcs/letsencrypt-nginx-proxy-companion like you can create a certificate for the gateway and need some maybe bash script to take the files from the lets script and build a new ssl.pfx file for ignition

---

<div class="post-metadata">

**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:** [August 4, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/10 "2025-08-04T21:12:34Z")

</div>

I'm going to debug and investigate this further--I'm seeing the very same on my local stack which is very much the same (Docker, Traefik, and step-ca sidecar that Traefik uses TLS-ALPN-01 challenges to request local certs from). Applying TLS at the gateway as well is a workaround but shouldn't be required. I'll report back findings.

EDIT: I've confirmed the issue and wrote up ticket IGN-13832 on our side. Thank you @Marco_Keller and @AGDC04 for taking the time to report this!

---

<div class="post-metadata">

**Author:** ![Marco\_Keller](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Marco\_Keller](https://forum.inductiveautomation.com/u/Marco_Keller)\
**Post date:** [August 8, 2025, 7:11am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/11 "2025-08-08T07:11:21Z")

</div>

Thank you @kcollins!  
In that context an ENV Variable for “Force Secure Redirect\*“ would be verry valueble as well.

It’s not possible to set it when HTTPS is handled outside Ignition so no redirection happens when opening Ignition with http.

But there is a workaround, I can set the redirection on traefik as well.

---

<div class="post-metadata">

**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:** [August 15, 2025, 9:10pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/12 "2025-08-15T21:10:58Z")

</div>

This has been resolved and will be in `8.3.0-beta4` next week. Also, @Marco_Keller , the force secure redirect setting can now be applied even when https is not configured in Ignition, though it requires being driven externally via a gateway argument `gateway.forceSecureRedirect=true`, applied like shown in the example [here](https://docs.inductiveautomation.com/docs/8.3/platform/docker-image/docker-image-examples#customizing-jvmwrappergateway-arguments-on-container-launch):

 ![SCR-20250815-ofzl](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/1/9161c3425c35bd501de3461fae143e40e11bcffb.png)

---

<div class="post-metadata">

**Author:** ![Marco\_Keller](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Marco\_Keller](https://forum.inductiveautomation.com/u/Marco_Keller)\
**Post date:** [August 18, 2025, 7:06am UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/13 "2025-08-18T07:06:21Z")

</div>

Wow, that was a quick fix. Thank you verry much!

---

<div class="post-metadata">

**Author:** ![Matthew\_Boyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew_boyers/32/59236_2.png) [@Matthew\_Boyers](https://forum.inductiveautomation.com/u/Matthew_Boyers)\
**Post date:** [December 2, 2025, 7:12pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/14 "2025-12-02T19:12:46Z")

</div>

Was this issue corrected with 8.3.1? We are having this same issue when we deploy a 8.3.1 dockerfile to our cloud environment.

---

<div class="post-metadata">

**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 3, 2025, 5:46pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/15 "2025-12-03T17:46:21Z")

</div>

This was fixed with the 8.3.0 final release. I just double-checked w/ 8.3.1 and it seems to be working correctly with a TLS-terminating ingress forwarding to http/8088 on the backend.

---

<div class="post-metadata">

**Author:** ![Matthew\_Boyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew_boyers/32/59236_2.png) [@Matthew\_Boyers](https://forum.inductiveautomation.com/u/Matthew_Boyers)\
**Post date:** [December 3, 2025, 7:40pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/16 "2025-12-03T19:40:57Z")

</div>

In our configuration, we have Force Secure Redirect AND Use Proxy Forwarded Headers checked. If I uncheck Force Secure Redirect and leave Use Proxy Forwarded Headers checked we get this error. If I uncheck both, we can see the projects. However we need Use Proxy Forwarded Headers checked for our IDP SSO configuration.

---

<div class="post-metadata">

**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, 3:01pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/17 "2025-12-04T15:01:15Z")

</div>

@Matthew_Boyers, I did some further digging and it looks like there is another scenario where this error can occur. The scenarios above were failures in resolving the secure port **with** public address settings defined.

I tried testing with public address settings **in auto-detect** and was able to reproduce this same error. I'll write up a separate ticket to investigate fixing this.

In the meantime, can you try applying public address settings? That should prevent this error at the moment.

---

<div class="post-metadata">

**Author:** ![Matthew\_Boyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew_boyers/32/59236_2.png) [@Matthew\_Boyers](https://forum.inductiveautomation.com/u/Matthew_Boyers)\
**Post date:** [December 4, 2025, 3:38pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/18 "2025-12-04T15:38:59Z")

</div>

@kcollins I created a ticket for this, #169433, where I have uploaded some information. When we were having this error, I had the “Auto Detect HTTP Address” checked. I unchecked it, supplied the public address, HTTP, and HTTPS ports, and now it shows the perspective projects in the launch web page.

---

<div class="post-metadata">

**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\
**Post date:** [July 7, 2026, 3:52pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/19 "2026-07-07T15:52:24Z")

</div>

Experienced the same in 8.3.7 now, did you get anything from your ticket?

Thanks

---

<div class="post-metadata">

**Author:** ![allen.miller1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/allen.miller1/32/85567_2.png) [@allen.miller1](https://forum.inductiveautomation.com/u/allen.miller1)\
**Post date:** [July 7, 2026, 4:52pm UTC](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168/20 "2026-07-07T16:52:48Z")

</div>

Issues when `Auto Detect HTTP Address` is enabled behind a TLS-terminating reverse proxy are being tracked in IGN-15058 - that ticket has not yet been resolved.

The current workaround remains to disable `Auto Detect HTTP Address` and manually set the Public Address, HTTP Port, and HTTPS port settings.

As @kcollins highlighted, if you happen to be using the Helm chart you'll get that config out of the box. If you aren't, there are a few ways to set those:

1. Directly on the Gateway Webserver config page  
 ![Screenshot 2026-07-07 at 09-47-13](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0adb69478266ff88475d14b68fa65a33e7dd8b63.png)
2. Using the [container runtime options](https://www.docs.inductiveautomation.com/docs/8.3/platform/docker-image#runtime-arguments) `-a`, `-h`, and `-s` (note you must use all three). EG:

```sh
-a ignition.k8s.localtest.me -h 80 -s 443

```

[Next page](https://forum.inductiveautomation.com/t/ign-13832-ignition-docker-image-at-kubernetes-with-error-to-show-the-projects/109168.md?page=2)