# Multi Relay HTTP request not working anymore?

**URL:** <https://wled.discourse.group/t/multi-relay-http-request-not-working-anymore/11531>\
**Category:** Usermods\
**Created:** [April 5, 2024, 10:59am UTC](https://wled.discourse.group/t/multi-relay-http-request-not-working-anymore/11531 "2024-04-05T10:59:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pixelwave](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pixelwave](https://wled.discourse.group/u/pixelwave)\
**Post date:** [April 5, 2024, 10:59am UTC](https://wled.discourse.group/t/multi-relay-http-request-not-working-anymore/11531/1 "2024-04-05T10:59:35Z")

</div>

I have **two ESP32**.

**First** is connected to a 4 port relay, runs WLED (0.14), controls LED lights, opens Wireless-AP and runs **multi-relay mod**.

**Second** is connecting to first ESP32 Wireless-AP and remotely controls the relays and LED lights via HTTP requests.

Now all of the sudden somehow the HTTP command to toggle the relays does not work somehow anymore? I can still connect to the Wireless-AP and toggle the relays via the GUI.

But the command I use in my remote ESP32 controller “[http://4.3.2.1/relays?toggle=1,0,1,1](http://4.3.2.1/relays?toggle=1,0,1,1)” does not work anymore and throws an error (404 not found).

Any ideas what could be the issue? The manual says those commands should work … and they did in the past.

Other HTTP commands do work (like “[http://4.3.2.1/win&A=255](http://4.3.2.1/win&A=255)”).

 ![Screenshot 2024-04-05 at 12.36.38](https://global.discourse-cdn.com/free1/uploads/wled/original/2X/3/3a8ea6ef6e79acacb2697b3fdb610bb913c43886.png)

---

<div class="post-metadata">

**Author:** ![pixelwave](https://avatars.discourse-cdn.com/v4/letter/p/0ea827/32.png) [@pixelwave](https://wled.discourse.group/u/pixelwave)\
**Post date:** [April 5, 2024, 12:55pm UTC](https://wled.discourse.group/t/multi-relay-http-request-not-working-anymore/11531/2 "2024-04-05T12:55:18Z")

</div>

Ok I figured something out … if I connect the WLED ESP32 to a Wifi Network and then try “ **192.168.178.59/relays?toggle=1,0,1,0** ” it works!

But it does not seem to work if the WLED ESP32 is in “AP-Mode” ( **4.3.2.1/relays?toggle=1,0,1,0** ).

Is there any workaround? For my final deployment I have the WLED ESP32 not connected to any Wifi network just acting as its own AP.

It seems to be an issue with the “multi-relay” usermod implementation. Because the standard HTTP commands from WLED (like “4.3.2.1/win&A=255”, etc…) work when connected to a Wifi Network as well as in “single AP-Mode”.