Connection can't get past POST/command on MacOS 10.15
Closed this issue · 0 comments
Originally: ckdo#8
@jdtsmith commented Oct 2, 2020
On MacOS I had to add -n en0 to get it running, but otherwise seems to start fine. Endpoint appears in Airplay List from iPhone, but when attempting to join, it doesn't seem to get past the POST /command section. So authentication apparently works (!), but then the RTSP stream has a TEARDOWN, and the connection is rejected. airplay2-receiver keeps running after this, but doing nothing, and CPU usage spikes. A further attempt to connect while still running doesn't get as far (to ----- ENCRYPTED CHANNEL -----), and CPU usage spikes even more.
You can see the output here. Thanks for working on this.
https://pastebin.com/raw/p4jcRZgY
@danielhelmstedt commented Oct 9, 2020
yep, same here
@jdtsmith commented Dec 13, 2020
One conjecture from ckdo is this relates to the Airplay version the sending device attempts to use. I tried (iPhone iOS 14.2):
User-Agent: AirPlay/525.38.2
which fails, but he has tested primarily with older senders. In fact with an older MacOS running iTunes (User-Agent: AirPlay/387.2), I can connect and playback works! Newer versions of the MacOS Music app running AirPlay/425.1 also fail to connect.
He thinks perhaps a PTP check is made that does not get a response from the server.
@PaulWieland commented Mar 17, 2021
@jdtsmith Try again with the latest version. I believe this is fixed and can be closed.
@jdtsmith commented Mar 18, 2021
Yep been fixed for a while, thanks for the reminder.