# Websocket connection interrupted **URL:** \ **Category:** Get Help\ **Tags:** awx\ **Created:** [April 18, 2024, 12:13pm UTC](https://forum.ansible.com/t/websocket-connection-interrupted/5019 "2024-04-18T12:13:45Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\ **Post date:** [April 22, 2024, 7:23pm UTC](https://forum.ansible.com/t/websocket-connection-interrupted/5019/7 "2024-04-22T19:23:52Z")
So, unless they’ve made changes since I posted this a few months ago: > [@AWX operator installation on Openshift](http://forum.ansible.com/t/awx-operator-installation-on-openshift/3314/2): > > AWX actually doesn’t natively support running on Openshift out of the box. OpenShift runs pods as random UID’s, but the AWX container is expecting UID 1000. So you will need to build your own AWX image for OpenShift to use by using the same Dockerfile but with the USER 1000 line commented out. You will run into various permissions issues until you take care of this. As for your certificate error, it’s hard to troubleshoot that without any idea of what your yaml looks like; It would be helpful i… AWX doesn’t really support OCP out of the box due to the random UID’s that each namespace runs under. My solution was to build my own AWX images, but I think you can change the SCC to allow AWX pods/ServiceAccounts to `runAsUser: type: RunAsAny` For me, the latter wasn’t approved by management, so building from scratch was the only option. > **[A Guide to OpenShift and UIDs](https://www.redhat.com/en/blog/a-guide-to-openshift-and-uids)** > > A deep dive into how OpenShift handles User ID and Namespaces Anyways, I can’t say for certain that this will fix your Web Socket issue specifically, but it may fix other weird bugs/quirks or otherwise wonky behavior. --- _[View the full topic](https://forum.ansible.com/t/websocket-connection-interrupted/5019)._