[BUG] Session closes after a few minutes when using remote connection via psn #342
Comments
|
Hello @streetpea, I will post here the full log: [2024-05-24 23:55:21:982982] [I] Logging to file /home/deck/.var/app/io.github.streetpea.Chiaki4deck/data/Chiaki/Chiaki/log/chiaki_session_2024-05-24_23-55-21-982982.log [2024-05-24 23:55:22:001001] [I] Controller 0 opened: "Microsoft X-Box 360 pad 0 (030079f6de280000ff11000001000000)" If you need any info, please let me know. |
|
Was there anything happening that could have been turning off your ps5 (I.e., tv with hdmi cec was turned off causing ps5 to turn off)? When you use data you were playing for the same amount of time (or more) with no issues? |
I'm right now at my brother's house, my PS5 is wired connected at home. As I remember, I turned off HDMI CEC on my TV. Do you want me to test a few minutes with my data and post a log here? Do you think it's something at my side (PS5)? |
|
Log of almost 20 minutes playing on mobile data, no errors: [2024-05-25 12:06:31:282282] [I] Logging to file /home/deck/.var/app/io.github.streetpea.Chiaki4deck/data/Chiaki/Chiaki/log/chiaki_session_2024-05-25_12-06-31-282282.log [2024-05-25 12:06:31:333333] [I] Controller 0 opened: "Microsoft X-Box 360 pad 0 (030079f6de280000ff11000001000000)" |
|
[2024-05-25 12:19:34:282282] [E] Takion dropping data with seq num 0x3d4cad55 |
|
Looking at the logs, I don't see anything that would be causing the stream connection to close on the ps side from Chiaki4deck. Honestly, the connection seems much better than the cellular one. If it is reproducible can you please post a log with verbose logging enabled. You can email it to me if you don't want to post it on here as well at streetpea@proton.me |
Sure, I can send to your mail. Thanks |
|
Just a verbose log with the wifi remote connection that fails after 5 minutes. |
Mail sent |
|
@SolidEdgard Can you see if the session still closes after 5 minutes with this build: https://github.com/streetpea/chiaki4deck/actions/runs/9236997438/artifacts/1537657086 and if it still does send a new verbose log? |
Hi, same issue :( Should I update or install a different build? |
|
From the log you sent it doesn’t like you are using the updated build. Download this build https://github.com/streetpea/chiaki4deck/actions/runs/9239468265/artifacts/1538003029 and use it to get the updated log … it will be in a new location (you can open the folder from the general tab of the settings page) instructions for build:
|
I'm using the version from the store. Checked for updates, but no one was found. Sorry for the confusion, a bit new to Steam OS |
|
@SolidEdgard see my comment above with instructions for build provided here: https://github.com/streetpea/chiaki4deck/actions/runs/9239468265/artifacts/1538003029 |
Great, downloaded. As I am not at home, will test it later. |
|
Follow the above comment (#342 (comment)) to load the settings also i updated the link so make sure to use the latest one specifically, |
Did that, opened this updated version, but now I can't even connect |
|
Can you try this build should fix the issue with the previous build https://github.com/streetpea/chiaki4deck/actions/runs/9240536324/artifacts/1538170169 |
|
|
tried the new version but no success. Do you have any ideas of what may be the issue? Thanks |
|
honestly I am puzzled as to what's causing this |
Hello Street, one update: On my router I opened the ports you mentioned on the setup guide AND put the PS5's IP on DMZ. Do you think this may be the cause of the conflict? |
|
@SolidEdgard I would take your ps5 out of the DMZ and unforward the ports if you are using remote connection via psn. |
the ports use is only with the manual connection procedure (external)? to use via psn connection (this new method) is not necessary to foward ports (as default)? I'm thinking in doing a test later: remove the PS5 from DMZ but keep the ports fowarded. And then, I'll test on this (external) router with and without steam deck on DMZ. Did almost 1hour of use right now, and no issues. Way better than using 4G data, it connected on the first attempt, with 4g I had to try at least 3~4 times. |
|
@SolidEdgard it is likely that what is happening on your 4G is it's falling to the case of port prediction behind symmetric NAT which can work but is not successful 100% of the time. I made a new build that should improve the port prediction (by opening the port immediately after prediction). Can you try this build: https://github.com/streetpea/chiaki4deck/actions/runs/9324541221/artifacts/1557693565 and post a log if it is still unsuccessful. This will be helpful to me even if you aren’t planning on using the mobile connection as your main way of connecting. You can replace the current appimage you have with this new one and it should just work … just download the file .. unzip and replace the old appimage and then run Note: you can disregard error messages that say try again as this just means the ps console was not ready for the connection yet and has nothing to do with Chiaki4deck. Usually this happens when you start a connection quickly after closing one so the ps doesn’t have time to properly terminate the previous session. |
|
@SolidEdgard yes, port forwarding is only required for manual connection. |
Sure, I'll do this test later and report |
|
@SolidEdgard did you make any progress with this issue on your end? |
Hi streetpea, it was 'solved by itself' but now it's bad again: Don't remember wich version was, but after one app update, this 'new' version worked fine with on my brothers internet. Searched about this error, and someone mentioned that rebuild database+clear cache resolved, but on my PS5 it was not resolved. I did a few tests: I don't know what's going, as I have the same ISP at home and the same company on mobile, can this be some change made by ISP at low level, something I can't check? I attached two logs: one that connected (can't remember if PS5+note was connected on the same hotspot 4G or home wifi) and one that failed; sorry for the long time with no update, if you need some test, feel free to ask Thanks |
Thank you sir! |
|
Hello Streetpea, I tried this new version, but after the "establishing connection with console over over psn" (ps5 turn on on this), there's the "cant establish connection" screen. This is from my notebook, but from my Steamdeck I got the same error. |
|
Just an update, did a second test, to test if the problem is my ISP, but no success, I really don't know what to do PS5 > connected to my smartphone internet Can you see at the logs what' the issue? |
|
@streetpea if you need any test, please let me know, thanks! |
|
@SolidEdgard try this build: https://github.com/streetpea/chiaki-ng/actions/runs/10976456043/artifacts/1962282232 ... it should be fixed, it looks like the timeout increase never got into main .. it's there now. |
Thank you! |
|
@SolidEdgard lmk if it fixes the problem when you get a chance to test it. |
|
chiaki_session_2024-09-23_14-21-39-284284.log
Now the error is I don I appreciate all the help, but I think I`ll give up :( no need to spend more your time Anyway, thank you for your time! |
|
@SolidEdgard can you post a verbose log? It seems it should work based on your log |
|
@SolidEdgard it makes sense that it’s slow as hell because you’re running into timeouts with the other requests to begin with … I’m thinking it might be related to increasing the timeout maybe it’s not getting to the next phase until too late… |
|
unsuported connection
Sorry if I didn't make myself clear, I meant that using the official remote play on 4g it's too slow (your app when I could use it remotelly, was much better). |
here: The strange note is that it can turn on the console (from standby\rest) but no connection afterwards. |
|
Turning on from standby is a connection via psn which is opened by the console … what we are establishing that isn’t working is a direct connection between the console and client (i.e., Steam deck). Have you tried pairing to your smartphone again? |
|
@SolidEdgard it’s possible your WiFi connection (on either side) changed to cgnat while your 4G isn’t cgnat so that’s why the official app is working there. The problem I fixed in the latest build should fix the error you were getting on your cellular network so please try that network again and see if it gets farther. The error on your home network was different I think (possibly the cgnat issue) |
Yes, Steamdeck is connected on my 4g and PS5, home network. I don't know if they cant turn off cgnat for me, but this is now, the 'only' way to work outside home, right? |
|
@SolidEdgard can you try with the official app connected to your phone from a pc (either windows or Mac) and make sure it still works? It’s possible your phone is using a different network for its connection vs the hotspot connection |
Sure, will download the official app on my notebook |
|
Bad news: No matter how many times I input the ID from PS5 remote connection, only when I connected the notebook on the same network it worked. Then, after it was configured and the PS5 was in rest mode, I changed the network back to my 4G and opened the software, but: I turned on the PS5, and error 8801330f So the issue is my network, as I told you that I tried with other 4g\carrier and the wifi from a different house. What piss me off is that it worked before, so, this company made some change (to what was working properly), don't know why. The strange thing is that official app on smartphone works ok, but not on the notebook (as it's the same app\same 4g network) maybe some ports I needed to open? (PS remote on firewall is open). I'm really out of ideas, and appreciate all the help from you. |
|
@SolidEdgard have you tried with the other networks with the new build? The thing is it was actually running into a different problem before that should be fixed. This new problem has to do with your wifi but could be your 4G network specifically |
No sir, I'll can a do another test with a different carrier (PS5 home wifi \ Steamdeck new 4g). So we can check if the issue is specifically my 4g. One moment. |
|
"connection over psn failed" |
|
@SolidEdgard yes that’s a different error … some stun servers are giving invalid transaction ids |
And this stun servers are my networks\4g carrier issues? |
|
Well the stun servers don't have anything to do with your carrier. However, I tried the same STUN servers and I got a response fine so I think it may be an error with your network causing you to get invalid responses. However, try again and see if it still giving you problems. |
I did this to build, is it right, right? |
|
If you are using this build https://github.com/streetpea/chiaki-ng/actions/runs/10976456043/artifacts/1962282232 then that is correct |
yes, is this one. But I think I discovered the problem: my 4g! I was all this time thinking that the issue was my ISP, but i'm now at work, asked for my colleague to open her smartphone's 4g so I can connect this notebook. So the problem is that not every internet connection will support this (my brother's home internet and my carrier for ex. is a no-no). I'm relieved, as nothing in home is blocking the software. What's strange is that my 4g with official app works, but that's ok. Thank you for all the help! Log below (successful): |
|
I thought when you connected with a laptop to your 4G the official app didn’t work either @SolidEdgard? So the issue is when you are using a hotspot with your phone’s 4G it doesn’t work. Is your phone connected to a wifi network other than its 4G? I’m wondering bc if it is then it could be using network A which works but the hotspot will always use the 4G which doesn’t work. That’s why I recommended you try the official with a pc connected to your hotspot bc it is a like for like comparison. And if I understood correctly, when you did that the official app failed as well. |
Just to clarify, my testes were: 1 test (tried this at home): Yesterday's test (tried at work): When I share my 4g internet, it automatically turn off wifi and share only the 4g data from carrier. |
Describe the bug
Connection drops after a few minutes after connecting successfully.
Debug Log
Please attach a log with verbose logging enabled. Awaiting log from user
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Stream continues without closing
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Waiting for user to provide
The text was updated successfully, but these errors were encountered: