Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receiver visible on iPhone's list but cannot connect #80

Open
raftutak opened this issue Nov 6, 2022 · 1 comment
Open

Receiver visible on iPhone's list but cannot connect #80

raftutak opened this issue Nov 6, 2022 · 1 comment

Comments

@raftutak
Copy link

raftutak commented Nov 6, 2022

The problem

Hi. I set up a receiver using docker compose. The receiver is visible then on my iPhone and MacBook, however I'm unable to connect. Before it started to be visible on the list I whitelisted required ports in ufw but as I mentioned I cannot connect.

Am I still missing something?

Below are the logs:

me@wyse-5070:~/airplay2-receiver$ sudo docker compose -f docker/docker-compose.yaml up
[+] Running 1/0
 ⠿ Container docker-ap2-1  Created                                                                                                     0.0s
Attaching to docker-ap2-1
docker-ap2-1  | Starting Avahi mDNS/DNS-SD Daemon: avahi-daemonProcess 13 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
docker-ap2-1  | .
docker-ap2-1  | [Receiver]: Name: Airplay2
docker-ap2-1  | [Receiver]: Enabled features: 0001c300405f4200
docker-ap2-1  | [Receiver]: FeatureFlags.Ft48TransientPairing|Ft47PeerManagement|Ft46HomeKitPairing|Ft41_PTPClock|Ft40BufferedAudio|Ft30UnifiedAdvertisingInfo|Ft22AudioUnencrypted|Ft20ReceiveAudioAAC_LC|Ft19ReceiveAudioALAC|Ft18ReceiveAudioPCM|Ft17AudioMetaTxtDAAP|Ft16AudioMetaProgress|Ft14MFiSoft_FairPlay|Ft09AirPlayAudio
docker-ap2-1  | [Receiver]: Interface: enp1s0
docker-ap2-1  | [Receiver]: IPv4: 192.168.0.6
docker-ap2-1  | [Receiver]: IPv6: fe80::e654:e8ff:fe3c:6881
docker-ap2-1  | [Receiver]: 
docker-ap2-1  | [asyncio]: Using selector: EpollSelector
docker-ap2-1  | [Receiver]: mDNS: service registered
docker-ap2-1  | [Receiver]: Starting RTSP server, press Ctrl-C to exit...
docker-ap2-1  | [Receiver]: serving on 192.168.0.6:7000
docker-ap2-1  | [AP2Server: 192.168.0.6:7000]: Opened connection from 192.168.0.118:49984
docker-ap2-1  | [AP2Handler: 192.168.0.6:7000<=>192.168.0.118:49984; Thread-2]: {'qualifier': ['txtAirPlay']}
docker-ap2-1  | [AP2Handler: 192.168.0.6:7000<=>192.168.0.118:49984; Thread-2]: Sending our device info
docker-ap2-1  | [AP2Server: 192.168.0.6:7000]: Thread-2: Opened HAPSocket from 192.168.0.118:49984
docker-ap2-1  | [AP2Handler: 192.168.0.6:7000<=>192.168.0.118:49984; Thread-2]: SETUP: rtsp://192.168.0.6/13447777975926408032
docker-ap2-1  | [AP2Handler: 192.168.0.6:7000<=>192.168.0.118:49984; Thread-2]: 

What commit exhibits the issue?

6f3c1ce

Was there a last known working commit?

No response

What type of installation are you running?

Docker

With which python3 version do you run Receiver?

3.8.10

OS the receiver runs on

Ubuntu 20.04.5 LTS

OS the sender runs

iOS 16.1, macOS Ventura 13.0

Which sender client was used

iOS Spotify, macOS settings

Command invocation

sudo docker compose -f docker/docker-compose.yaml up

Please include --debug output which helps to illustrate the problem

No response

Additional information

No response

@raftutak raftutak changed the title Receiver visible in iPhone's list but cannot connect Receiver visible on iPhone's list but cannot connect Nov 6, 2022
@systemcrash
Copy link
Member

My best suggestion would be to disable the firewall, and work backwards from there. ControlPort and DataPort which the are advertised need to be accessible - but those are usually assigned in the non-root port range. So leaving those UDP ports open is a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants