502 bad gateway is the generic error the front-end fires whenever an add on like that can’t be loaded through ingress. (Add on didn’t start or isn’t displaying properly)
It just means both addons aren’t started - and doesn’t necessarily indicate a common cause. Troubleshoot each - what do your logs say.
Are you trying to connect to the same coordinator you did with ZHA with zigbee2mqtt? If so, you need to disable / uninstall ZHA first - only one can open the port at a time… did you disable it?
I never enabled it. I did uninstall zigbee2mqtt then configured the sonoff in the webui which I assume enabled ZHA? then a temp sensor popped up in < 1second after I pressed the pair button on it.
Whether YOU enabled ZHA or not - it’s enabled if its working (HA detects and configures if for you - that’s probably where it came from.)
It’s also the issue if you’re trying to install Zigbee2mqtt to use that Sonoff. Which I assume you are, because that log you noted above - a failed start for Zigbee2mqtt. This is expected if you have ZHA operating and try to open the same coordinator - Z2M will fail to start and - you will get a 502 error attempting to open its console.
You can have one or the other - not both, unless you get a second zigbee coordinator stick.
You can disable any integration (which ZHA is) by going to System > Devices and Services, locate your integration, then select the vertical elipsis (three dot) menu (blue arrow) and then disable (red arrow) in the popup: