# WebSocket connection failed - embedded Ignition website

**URL:** <https://forum.inductiveautomation.com/t/websocket-connection-failed-embedded-ignition-website/105468>\
**Category:** Ignition\
**Tags:** ignition80, perspective, ignition81\
**Created:** [April 23, 2025, 2:07pm UTC](https://forum.inductiveautomation.com/t/websocket-connection-failed-embedded-ignition-website/105468 "2025-04-23T14:07:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elena.tornero](https://avatars.discourse-cdn.com/v4/letter/e/c89c15/32.png) [@elena.tornero](https://forum.inductiveautomation.com/u/elena.tornero)\
**Post date:** [April 23, 2025, 2:07pm UTC](https://forum.inductiveautomation.com/t/websocket-connection-failed-embedded-ignition-website/105468/1 "2025-04-23T14:07:02Z")

</div>

We have already managed to start the embedded Ignition website on another website, it no longer gives us that error.

The problem is that now we get another connection error ('WebSocket connection failed'). The embedded ingnition website stays in 'initializing' all the time and gives me the following error every time it tries to initialize and authenticate:

 ![1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/5/8522aaf39ad110b9dcfce6bedf4d0b374d014028.png)

As you can see, the website stays all the time initializing:

 ![2](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/0/d0c68a2991ba0e6fe2722155ec3acc27ac81194e.png)

We believe that it may be a matter of CORS policy, but we are not entirely sure how to tackle it and solve it, could you help us?

Thank you all!

---

<div class="post-metadata">

**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:** [April 23, 2025, 2:41pm UTC](https://forum.inductiveautomation.com/t/websocket-connection-failed-embedded-ignition-website/105468/2 "2025-04-23T14:41:17Z")

</div>

That usually means there's a firewall or reverse proxy along the path from client browser to Ignition gateway that is interfering. Can the client browsers connect to Ignition outside an IFrame? Make sure that works first, before you can expect an IFrame to work.