ESP32 Snapclient connects but Snapserver reports bad method

[ivansv3108]

Hello,

I am trying to use the snapclient fork for ESP32 with a Snapserver v0.27.0 running on an Orange Pi Zero 3.

The problem I am facing is that my ESP32 successfully connects to the server over TCP, but Snapserver logs show

ControlSessionHttp::on_read error: bad method, and no audio is received on the ESP32.

Here are the details of my setup:

Hardware:

Server: Orange Pi Zero 3, connected via LAN

Audio source: Audio from my phone via Bluetooth A2DP to the server

Snapserver version: v0.27.0

Client: ESP32 DevKit V1

DAC connected via I2S PCM5102

Pins: I2S_LRCK=GPIO25, I2S_BCLK=GPIO26, I2S_DATA=GPIO22

Connected to the same Wi-Fi network as the server

Software / Configuration:

Snapserver running and listening on port 1780

ESP32 snapclient compiled and flashed with ESP-IDF 5.3.1

Logs on ESP32 show:

SC: try connecting to static configuration 192.168.1.75:1780
SC: netconn connected
SC: netconn sent hello message

Snapserver logs show:

ControlServer::NewConnection: 192.168.1.77
Removing 1 inactive session(s), active sessions: 1
ControlSessionHttp::on_read error: bad method

What I’ve confirmed:

Network connectivity is fine; ping works from server to ESP32

TCP connection is established; the “hello message” is sent

The issue seems related to the handshake/protocol, as the server interprets the message as HTTP (bad method)

I would appreciate any guidance on:

Whether this fork is compatible with Snapserver v0.27.0

Any known issues causing bad method errors with ESP32 clients

Suggestions for debugging or adjusting the ESP32 client to be recognized by Snapserver

Thank you in advance for your help!

[CarlosDerSeher]

Which branch did you compile?

My server is running snapserver v0.32.3 and plays audio just fine. Although I have to say I did not look at the logs of it for quite a long time