"Bad gateway." error, unable to connect to voice

Summary

All voice channels in a specific community are non-functional. Attempting to join any voice channel results in an indefinite "Connecting..." state on the client. The channel settings page displays a "Bad gateway." error directly under the Channel Name field, indicating the community has been assigned a broken or unreachable voice gateway.

Steps to reproduce

1. Open the BOHICA community (1474936787102216298)
2. Attempt to join any voice channel
3. Client hangs on "Connecting..." indefinitely and never establishes a voice connection
4. Navigate to any voice channel's General settings page — observe "Bad gateway." error displayed under Channel Name

Environment (optional)

Expected Behavior Voice channels connect normally, consistent with behavior observed on other communities on the same Fluxer instance. Actual Behavior

• Client displays "Connecting..." indefinitely when joining any voice channel
• Voice channel General settings page shows "Bad gateway." error
• Changing the Voice Region (tested: Automatic → US East) does not resolve the issue
• Voice works correctly on other Fluxer communities under the same account

Logs or screenshots (optional)

image image image

• Browser Console (VoiceConnectionManager):

`[VoiceConnectionManager] [Warn] Voice server timeout { guildId: '1474936787102216298', channelId: '<channel_id>' }` Stack trace: scheduleVoiceServerTimeout → startConnection → connectToVoiceChannel The client initiates a voice connection but receives no response from the voice server within the timeout window. No Web Socket connection is ever established — the Network tab shows zero Web Socket activity during the voice join attempt, confirming the voice server never responds. Additional Notes

• The issue is isolated to this specific community — other communities on the same account connect to voice without issue, confirming this is not a client-side or network problem
• The "Bad gateway." error visible in channel settings suggests the community has been assigned a voice gateway that is unreachable or misconfigured at the infrastructure level
• Deleting and recreating affected voice channels does not resolve the issue
• Reassigning the community to a healthy voice gateway should resolve the issue

-