Can get to the login screen (past the launcher) just fine, but whenever I try to login with my account credentials, it eventually returns back with a red box above the input fields that say "Unable to connect to login servers". Compatibility settings have nothing checked -- which to me is kind've odd, because it's not listed anywhere (that I can recall) as having Linux native status. I also tried this using Heroic Game Launcher and installing the Epic games store version, and that also yields the same error. However using that launcher and looking at the logs, I see lots of errors stating the following (just a very VERY tiny snippet but the log is kind've flooded with the Failed to read DnsConfig lines):

[1026/132238.951:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132242.659:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. LogOnline: Warning: OSS: Async task has hit the limit of attempts [1/1], aborting! LogOnline: Warning: OSS: Async task 'FOnlineAsyncTaskLoginPlatform LocalUserNum: 0 bWasSuccessful: 0' failed in 3.101161 seconds LogHttp: Warning: 000000006ED4CBB0: request was cancelled LogS6Core: Warning: Malformed JWT: Did not contain 3 parts separated by periods [1026/132243.951:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132247.659:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132248.954:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132252.660:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132253.956:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132257.661:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132258.958:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. LogStreaming: Display: 0.001 ms for processing 2 objects in RemoveUnreachableObjects(Queued=0, Async=0). Removed 0 (21033->21033) packages and 0 (32943->32943) public exports. [1026/132302.662:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig. [1026/132303.960:WARNING:dns_config_service_win.cc(712)] Failed to read DnsConfig.

It could be a red-herring but I don't think it is given how many of those errors are present in the log, combined with the JWT error. I did try linking my Steam account (using the Steam version) with the account that my Epic version is using since the Steam version kept warning me that if I skip that step it won't let me do it later. So perhaps this is the issue? I'm pretty sure I have ran Palia before on Linux and perfectly. There was a recent large update, and then a small bug-fix (I think it was a bug-fix) patch like the day after; maybe that was it?

I've seen some places reference checking your DNS settings. I say these "things" because it wasn't clear to me, when reading the posts, whether it was a tool the OP was referring to or a game; I saw posts referencing the Unreal Engine (which I believe that's what Palia is using), but I also saw posts on Microsoft's site which didn't make a lot of sense to me -- unless the assertion yielding the bit: "dns_config_service_win.cc(712)" is referencing line 712 in either the game's source-code or the Unreal Engine. I had assumed the error was from Wine kicking that error out. However, maybe not and instead the reference was the game kicking the error back as a reference to its own source code (like an assertion) or it wsa coming from the Unreal engine?...

It should be noted, I'm using 8.8.8.8 (Google's DNS). As a result, I don't think it's a DNS setting, on my end, that's the issue. If I had to make a very VERY cursory guess (going based on so far what I've seen in the log), my guess would be the DNS error is the ripple affect of the JWT token failing for authentication. Perhaps upon successful authentication, the Palia login server returns back a hostname (as part a DnsConfig package) of the game server and because the authentication is failing, the game client tried to look up the hostname, but because the hostname is never replied back (due to the faulty authentication and never being sent a DnsConfig package), the code that attempts to open the returned data (that would then go on to resolve the hostname) fails and so the error is not necessarily in error (in that it IS true that it would have failed to read the package, but only because it doesn't exist because it was never sent because the auth failed) but it's not detailed enough. I'll probably look through my logs and do some deeper analysis since my friends play and I'd like to play with them but so far I don't have any other information.