I can no longer connect outside house

[Spunjz]

Hello, I recently updated from v1.7 to 1.9 and now I can no longer connect outside my home wifi. It was working perfectly fine before. I'm on the steamdeck and when I click play on my console, it tries to establish a connection and then just completely closes Chiaki4deck back to my steam library. Any ideas?

EDIT: I don't see this anywhere, but do you need to re-add your console after an update? Because it did make me generate a new token for my PSN Login.

[streetpea]

Please attach a log with verbose logging enabled

[Spunjz]

I enabled and launched. How/where do I find the log? EDIT: found it. will post shortly

[Spunjz]

chiaki_session_2024-09-26_12-10-39-485485.log

[streetpea]

@Spunjz are you using a different internet provider to connect from? It shouldn't crash but not all networks work due to limitations with the Sony's console (PlayStation) side implementation of the code to connect remotely without port forwarding. Here is a new build to try, it should hopefully fix the crash but you may get the network is unsupported though based on your earlier logs. https://github.com/streetpea/chiaki-ng/actions/runs/11062213094/artifacts/1985212799

You can first unzip it to your downloads folder and then make it executable with:

chmod +x ~/Downloads/chiaki-ng.Appimage

and then open it with:

~/Downloads/chiaki-ng.Appimage

Then, close it and you can copy settings from the flatpak with

cp ~/.var/app/io.github.streetpea.Chiaki4deck/config/Chiaki/Chiaki.conf ~/.config/Chiaki/Chiaki.conf

and then you can reopen the appimage and use it to test it out.

[Spunjz]

@streetpea I am doing absolutely nothing different. The only 2 networks I would play on were my local wifi, which has not changed, and my works wifi, which has not changed either. I have never had to port forward before either. I'll will attempt the new build.

[Spunjz]

So I think it's working now. I tested by turning the wifi off on my phone, turning on hotspot, connecting to it on steamdeck. Showed no local connections and only remote and I was able to connect. I will let you know if it still works tomorrow when I get in the office.
EDIT: I took a drive down to my dad's house and used his wifi as a test as well and I connected just fine. If all is working tomorrow, I'll gladly close this issue out 🫡

[streetpea]

@Spunjz it’s likely your work network changed to symmetric NAT (this is a per router setting so it’s even possible you are just connecting to a different router in the same work network if there are multiple routers involved). Other networks that are not symmetric NAT will work. Either way it shouldn’t crash. Hopefully, at least that is fixed with the update. If not I’ll give you instructions to produce a crash report to debug it.

[Spunjz]

@streetpea So it seems whatever you did with the new AppImage has fixed the issue. I was able to connect first try now. Thanks for all your help!

[streetpea]

@Spunjz can you post a new verbose log on the network that was failing before? I just want to check something

[Spunjz]

@streetpea chiaki_session_2024-09-27_11-46-12-330330.log

[streetpea]

@Spunjz awesome. Your home network is compatible with all external network types so remote connection should work for you regardless of external network type given your home network router stays the same. The fix did indeed fix your problem.

[Spunjz]

Yea and again, thanks for all the help!