[BUG] Couldn't contact PlayStation over established connection, likely unsupported network

[Leosdream]

When trying to connect to chiaki via PSN I get the message "Couldn't contact PlayStation over established connection, likely unsupported network" and the app closes

[2024-06-13 04:39:16:788788] [I] Logging to file /home/deck/.var/app/io.github.streetpea.Chiaki4deck/data/Chiaki/Chiaki/log/chiaki_session_2024-06-13_04-39-16-786786.log
[2024-06-13 04:39:16:788788] [I] Chiaki Version 1.7.2
[2024-06-13 04:39:20:821821] [I] >> Created session
[2024-06-13 04:39:20:821821] [I] ChiakiOpusEncoder initialized
[2024-06-13 04:39:20:825825] [I] Connected Steam Deck ... gyro online

[2024-06-13 04:39:20:825825] [I] Controller 0 opened: "Microsoft X-Box 360 pad 0 (030079f6de280000ff11000001000000)"
[2024-06-13 04:39:20:835835] [I] Duid: 00000007000a00c000010287001500003af3e51a2488d0935072e4224585ff75
[2024-06-13 04:39:22:378378] [I] >> Started session
[2024-06-13 04:39:36:912912] [I] Failed to find UPnP-capable devices on network: err=0
[2024-06-13 04:39:38:797797] [E] remote/stun.h: Failed to receive STUN response, error was Resource temporarily unavailable
[2024-06-13 04:39:38:797797] [W] Failed to get external address from stun.ukh.de:3478, retrying with another STUN server...
[2024-06-13 04:39:39:295295] [I] Calculating packet allocation based on 4 responses with the same address
[2024-06-13 04:39:39:295295] [W] Got different allocation increment calculations from different ports.
Increment 0: 63624, Increment 1: 20089, Increment 2: 58722
[2024-06-13 04:39:39:295295] [E] remote/stun.h: Failed to send STUN request, error was Network is unreachable
[2024-06-13 04:39:39:295295] [W] Failed to get external address from 2001:4860:4864:5:8000::1:19302, retrying with another STUN server...
[2024-06-13 04:39:39:295295] [E] get_client_addr_remote_stun: Failed to get external address
[2024-06-13 04:39:39:295295] [W] IPV6 NOT supported by device. Couldn't get IPV6 STUN address.
[2024-06-13 04:39:41:348348] [I] check_candidate: Resending requests to all candidates TRY 1... waiting for 1st response
[2024-06-13 04:39:41:850850] [I] check_candidate: Resending requests to all candidates TRY 2... waiting for 1st response
[2024-06-13 04:39:42:352352] [I] check_candidate: Resending requests to all candidates TRY 3... waiting for 1st response
[2024-06-13 04:39:42:853853] [I] check_candidate: Resending requests to all candidates TRY 4... waiting for 1st response
[2024-06-13 04:39:43:354354] [I] check_candidate: Resending requests to all candidates TRY 5... waiting for 1st response
[2024-06-13 04:39:43:855855] [I] check_candidate: Resending requests to all candidates TRY 6... waiting for 1st response
[2024-06-13 04:39:44:356356] [I] check_candidate: Resending requests to all candidates TRY 7... waiting for 1st response
[2024-06-13 04:39:44:858858] [I] check_candidate: Resending requests to all candidates TRY 8... waiting for 1st response
[2024-06-13 04:39:45:359359] [I] check_candidate: Resending requests to all candidates TRY 9... waiting for 1st response
[2024-06-13 04:39:45:861861] [I] check_candidate: Resending requests to all candidates TRY 10... waiting for 1st response
[2024-06-13 04:39:46:362362] [I] check_candidate: Resending requests to all candidates TRY 11... waiting for 1st response
[2024-06-13 04:39:46:863863] [I] check_candidate: Resending requests to all candidates TRY 12... waiting for 1st response
[2024-06-13 04:39:47:364364] [I] check_candidate: Resending requests to all candidates TRY 13... waiting for 1st response
[2024-06-13 04:39:47:865865] [I] check_candidate: Resending requests to all candidates TRY 14... waiting for 1st response
[2024-06-13 04:39:48:366366] [I] check_candidate: Resending requests to all candidates TRY 15... waiting for 1st response
[2024-06-13 04:39:48:867867] [I] check_candidate: Resending requests to all candidates TRY 16... waiting for 1st response
[2024-06-13 04:39:49:369369] [I] check_candidate: Resending requests to all candidates TRY 17... waiting for 1st response
[2024-06-13 04:39:49:870870] [I] check_candidate: Resending requests to all candidates TRY 18... waiting for 1st response
[2024-06-13 04:39:50:371371] [I] check_candidate: Resending requests to all candidates TRY 19... waiting for 1st response
[2024-06-13 04:39:50:872872] [I] check_candidate: Resending requests to all candidates TRY 20... waiting for 1st response
[2024-06-13 04:39:51:374374] [E] check_candidate: Select timed out
[2024-06-13 04:39:51:377377] [E] chiaki_holepunch_session_punch_holes: Failed to find reachable candidate for control connection.
[2024-06-13 04:39:51:377377] [E] !! Failed to punch hole for control connection.
[2024-06-13 04:39:52:093093] [I] chiaki_holepunch_session_fini: Holepunch session deleted.
[2024-06-13 04:39:52:093093] [E] websocket_thread_func: Select canceled.

• OS: SteamOS
• Device Steam Deck
• Chiaki4deck Version 1.7.2

[streetpea]

@Leosdream It seems your network type is unsupported. Not all network types can be supported. Have you tried the official remote play app using the same network on your pc?

[Leosdream]

@streetpea Yes the official remote play app works no problem

[streetpea]

@Leosdream it would be extremely helpful if you could use this hotspot or whatever remote network you’re trying with a pc and the official remote play app and use the free trial of this app https://www.httpdebugger.com/ to capture a session of the http traffic when using remote play via the cellular network as well as a wireshark capture of the same session https://www.wireshark.org/ and email these to me at streetpea@proton.me This will enable me to reverse engineer what the official app is doing to make sure there isn’t something more I could do to improve connection success with your network type.

follow these steps

Before running remote play
Wireshark:

1. Open it
2. double click wifi from the Home Screen when the app opens
3. Leave it open

Http debugger

1. Open it
2. leave it open

Start the official remote play app on windows using the same WiFi/cellular connection that you’re using for Chiaki4deck for the remote connection via psn and connect remotely. Once the stream begins, (you see the ps home menu or game for example) close the remote play application.

Then go to wireshark

1. Click capture (in the top menu bar) and then select stop.
2. Go to File (in the top menu bar) and then select save
3. Save to location of your choosing
4. Close wireshark

Then go to http debugger
1.click file then save session
2. Save to location of your choosing

Then upload both saved files (one .pcap from wireshark and one .xml from http debugger) to me at streetpea@proton.me

[mokeyadri]

Has anyone been able to fix it or make it work in any way?

[streetpea]

@mokeyadri it means your router nat isn’t compatible. If you are able to connect with the official remote play client on windows with the same network that is failing for Chiaki4deck please follow the steps in my comment above and email me with results.

[github-actions]

This issue is stale because it has been open for 90 days with no activity.