# Receptor.log : Backend Receiving error remote error: tls : bad certificate **URL:** \ **Category:** Get Help\ **Tags:** awx-operator, awx\ **Created:** [August 9, 2024, 12:59pm UTC](https://forum.ansible.com/t/receptor-log-backend-receiving-error-remote-error-tls-bad-certificate/7759 "2024-08-09T12:59:41Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![prateektl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/prateektl/32/8985_2.png) [@prateektl](https://forum.ansible.com/u/prateektl)\ **Post date:** [August 9, 2024, 12:59pm UTC](https://forum.ansible.com/t/receptor-log-backend-receiving-error-remote-error-tls-bad-certificate/7759/1 "2024-08-09T12:59:41Z")
We have recently setup a new AWX, using below structure: 2 ec2 instance where we have installed minikube and provisioned the UI components like, operator, task and web (pods) for both of the instances. 1 ec2 instance where the postgres db is configured. Now we have successfully configured the UI and DB and the setup is up and running. (This new setup is a migration from old one, where we had our AWX on an ec2 instance within minikube. The DB for the old setup was on a container) Now on the new AWX setup, we were able to attach the execution node and the status of the execution node is success. But when we trigger a job template using the execution node it throws below error: **Instance [testserver.example.com](http://testserver.example.com) is not in the receptor mesh** When we checked the receptor.log on the execution node, it throws : **Backend Receiving error remote error: tls : bad certificate** any suggestion where we are going wrong? ---
**Author:** ![prateektl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/prateektl/32/8985_2.png) [@prateektl](https://forum.ansible.com/u/prateektl)\ **Post date:** [August 13, 2024, 8:56am UTC](https://forum.ansible.com/t/receptor-log-backend-receiving-error-remote-error-tls-bad-certificate/7759/2 "2024-08-13T08:56:31Z")
By referring the document: [Custom Receptor CA - Ansible AWX Operator Documentation](https://ansible.readthedocs.io/projects/awx-operator/en/latest/user-guide/advanced-configuration/custom-receptor-certs.html) i was able to provision AWX UI components (Operator, AWX Web and AWX Task) pods on the 2 ec2 instance, by providing custom receptor certs. I was able to attach the execution node to the AWX as well. But when i run a health check, i get an intermittent issue with below error: ![image](https://us1.discourse-cdn.com/ansible/original/2X/8/859c8e29502bdedbff51396f2d452d20f03ce766.png) If i run the health check again, the instance status will be ready: ![image](https://us1.discourse-cdn.com/ansible/original/2X/0/05b4b0fd03988f4701ffadeb01fe0493db6d7bc6.png) In the receptor.log of the execution node, i see this logs: ![image](https://us1.discourse-cdn.com/ansible/original/2X/b/bfa36c9656491d3c64288164154b52d3acf93088.png) Its behaving like an intermittent issue. I was not able to find more details in AWX web pod or AWX Task pods. Any suggestion or help would be appricated. Regards, Prateek T L