# Ignition Gateway Stuck on Loading Screen After SSL Implementation **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 21, 2025, 10:17pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038 "2025-03-21T22:17:53Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![mosesogbonna68](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mosesogbonna68](https://forum.inductiveautomation.com/u/mosesogbonna68)\ **Post date:** [March 21, 2025, 10:17pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/1 "2025-03-21T22:17:53Z")
I've recently set up Ignition on my server (running on port 8088), and it was working properly over HTTP. However, after implementing SSL with a subdomain, I'm experiencing issues. ![Screenshot (17)](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/1/41085626007843058102d176e849846a500cd914.png) ![Screenshot (17)](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/1/41085626007843058102d176e849846a500cd914.png) **Current Setup:** - Ignition Gateway running on port 8088 (HTTP) - Successfully obtained and installed SSL certificate - Created subdomain pointing to my server IP address - SSL is now enforced **Issue:** When I try to access the Ignition gateway through my subdomain with HTTPS, the interface gets stuck on the loading screen (screenshot attached). The browser just shows the loading animation indefinitely. **What I've Tried:** - The certificate is properly installed - The subdomain correctly resolves to my IP address - Regular HTTP access on port 8088 still works without SSL I'm new to configuring Ignition with SSL and suspect I might be missing a configuration step between Nginx (handling SSL) and Ignition. Does Ignition require additional configuration to work with a reverse proxy for SSL termination? Any guidance on properly configuring Ignition to work with an SSL proxy would be greatly appreciated. Thank you! ---
**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:** [March 21, 2025, 10:20pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/2 "2025-03-21T22:20:19Z")
You usually have to tell the gateway to **not** auto-detect URLs, and tell it to always use the complete domain name that matches the certificate. ---
**Author:** ![mosesogbonna68](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mosesogbonna68](https://forum.inductiveautomation.com/u/mosesogbonna68)\ **Post date:** [March 22, 2025, 11:54am UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/3 "2025-03-22T11:54:46Z")
Thank for the response, Please can you throw more light on this, with direction, are you referring to the gateway.xml file should i go there and specify my subdomain Like this sub domain ---
**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:** [March 22, 2025, 1:39pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/4 "2025-03-22T13:39:14Z")
No, here, at Config =\> Networking =\> Web Server: ![Config-Networking-WebServer-Public](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/8/883df20914c434cf1495f4b295e1c69777336b40.png) Turn off auto-detect. Fill in the other fields. The "Public Address" would be your complete domain name (matching the certificate). Make sure all clients use the domain name when force redirect is turned on. ---
**Author:** ![mosesogbonna68](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mosesogbonna68](https://forum.inductiveautomation.com/u/mosesogbonna68)\ **Post date:** [March 22, 2025, 3:21pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/5 "2025-03-22T15:21:55Z")
thank you sir, but after doing the above you asked we are still stuck on thesame screen i can access the gateway but i cant access the project stuck on connecting... thing ---
**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:** [March 22, 2025, 3:23pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/6 "2025-03-22T15:23:18Z")
> [@mosesogbonna68](#): > > can access the gateway Ok. That helps. Are you sure you have your proxy configured to permit websockets? (Your gateway logs probably have clues to this.) ---
**Author:** ![mosesogbonna68](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mosesogbonna68](https://forum.inductiveautomation.com/u/mosesogbonna68)\ **Post date:** [March 22, 2025, 3:33pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/7 "2025-03-22T15:33:36Z")
I have not done any proxy configuration to permit websockets how can do that sir , with guide ---
**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:** [March 22, 2025, 3:39pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/8 "2025-03-22T15:39:40Z")
I don't use nginx. In apache, you enable the `proxy_wstunnel` module and it Just Works™. Perhaps this helps you: > **[WebSocket proxying](https://nginx.org/en/docs/http/websocket.html)** ---
**Author:** ![mosesogbonna68](https://avatars.discourse-cdn.com/v4/letter/m/9e8a1a/32.png) [@mosesogbonna68](https://forum.inductiveautomation.com/u/mosesogbonna68)\ **Post date:** [March 22, 2025, 4:25pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/9 "2025-03-22T16:25:46Z")
I dont have any of this nginx or apache server set on my instance in aws, just my domain pointing to my ip. is there any thing i can do from here ---
**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:** [March 22, 2025, 4:27pm UTC](https://forum.inductiveautomation.com/t/ignition-gateway-stuck-on-loading-screen-after-ssl-implementation/104038/10 "2025-03-22T16:27:29Z")
I don't know anything about AWS. Your OP says you are using nginx for your SSL. 🤷‍♂️ Have you looked at your wrapper log file for websocket errors? Perhaps it is time to open a support ticket.