Unable to Login: Could not fully initialize Epic Online Services

I

Imply5385

New member
Hello y'all!

I have been unable to run the game since yesterday as I get this error below.

The issue started today. I was playing with my friend yesterday, and today I am unable to connect to EOS.

Here are my troubleshooting steps:

  • Made sure I was online in Steam (I am running the game through Steam).
  • Made sure EOS was online.
  • Made sure Steam wasn't undergoing maintenance.
  • Validated my files.
  • Tried with and without EAC.
  • Flushed my DNS.
  • Updated my OS and rebooted.
  • Power-cycled my router.
  • made sure I had an IPv4 address.
  • There was no update to the game.
  • Tried to run the game from the Steam executable (I get a new error, unable to connect to Steam).
  • My friend is able to connect.



The only thing that changed since yesterday is I left a positive review on Steam. I did not restart my computer or Steam itself.

I use Fedora Linux 40 (kernel 6.11.4-201.fc40.x86_64).

Is anyone able to help?

EaVttih.png


 
This honestly could be Steam, but Epic is also known to do server maintenance on Tuesdays/Wendsdays so it could be either. 

 
Nope, the issue is still ongoing. Do you know where I can find the logs?

After a bit of digging, I have some more information.

 
Imply5385 said:
Nope, the issue is still ongoing. Do you know where I can find the logs?

After a bit of digging, I have some more information.

Click to expand...


Initial searching on that eos auth error shows it's an issue with a certificate, not entirely sure how to fix that for Linux on hand in this particular case, I'll have to ask around (unless someone here knows how).

You do have an unrelated file limit issue that has steps on how to fix in the log, which I do recommend doing

 
You're welcome. @SylenThunder may be able to correct me if I'm wrong, but this may resolve it (honestly not entirely sure how to do it on Linux, and all distros are different, unfortunately the couple of LInux distros I have "just work" so I've never had to do it). Cert name is r2m02.crl

Web searching has shown some users in other EOS games have simply installed a different browser than they have installed (Edge and Chrome were the two the users talked about) installed the certs. 




 
Last edited by a moderator:
This has not resolved the issue, but I tried to install and update the revocation certificate found below.

I used these commands:

Code: 
# Downloaded r2m02.crl from https://community.7daystodie.com/topic/3998-support-faq-information-and-common-solutions/
sudo cp $HOME/Downloads/r2m02.crl /etc/pki/ca-trust/source/anchors/
sudo chown root:root /etc/pki/ca-trust/source/anchors/r2m02.crl
sudo update-ca-trust
sudo reboot


 
My method may not have been the correct way of installing the cert, I am only vaguely familiar with the process.

I am using the Flatpak version of Steam, and the Gnome Flatpak Runtime may include its own certs. Let me see if I can't work some magic.

 
Imply5385 said:
Well, they deleted my post.
Click to expand...


Well then that's not fun. 

So, I've done some searching about, and have found out that freedesktop sdk flatpak can be really funny with certs. Stil not entirely sure how to get around that, but here are some things to try:

sudo update-ca-certificates
sudo trust extract-compat

If you're running the game under.. Flatpak or other form of contanierization for the game, try this

flatpak override --user --filesystem=/etc/ssl/certs <app-id> (replacee app-id with 7 days' id)




Also suggestions were to ensure the cert on your system itself is trusted (manually)

 
Jugginator said:
Well then that's not fun. 

So, I've done some searching about, and have found out that freedesktop sdk flatpak can be really funny with certs. Stil not entirely sure how to get around that, but here are some things to try:

sudo update-ca-certificates
sudo trust extract-compat

If you're running the game under.. Flatpak or other form of contanierization for the game, try this

flatpak override --user --filesystem=/etc/ssl/certs <app-id> (replacee app-id with 7 days' id)




Also suggestions were to ensure the cert on your system itself is trusted (manually)
Click to expand...
I still get the same issue after successfully running the commands. I'm going to try to run the game outside of the Steam Flatpak. Do you know where I can find my saved data in the Steam Flatpak?

 
Imply5385 said:
I still get the same issue after successfully running the commands. I'm going to try to run the game outside of the Steam Flatpak. Do you know where I can find my saved data in the Steam Flatpak?
Click to expand...


Honestly I've never used any Linux distro outside of Ubuntu/Mint to play a game (and only for testing), normally other complicated distros as such are just use for experimenting/IT work/servers. Looking at your log file... maybe here? /home/roland/.var/app/com.valvesoftware.Steam/.local/share/7DaysToDie/Saves/

 
Last edited by a moderator:
This fixed the issue!

I downloaded the Fedora package version of Steam instead of the Flatpak and symlinked those two directories:
 

ln -s $HOME/.var/app/com.valvesoftware.Steam/.steam/steam/steamapps/common/7\ Days\ To\ Die/ $HOME/.steam/steam/steamapps/common/
ln -s $HOME/.var/app/com.valvesoftware.Steam/.local/share/7DaysToDie $HOME/.local/share/




I can now run 7D2D from the non-Flatpak version, connect to EOS, and all my saves are there.

This seems to be an issue with Flatpak and how it handles certificates.

 
Imply5385 said:
This fixed the issue!

I downloaded the Fedora package version of Steam instead of the Flatpak and symlinked those two directories:
 

ln -s $HOME/.var/app/com.valvesoftware.Steam/.steam/steam/steamapps/common/7\ Days\ To\ Die/ $HOME/.steam/steam/steamapps/common/
ln -s $HOME/.var/app/com.valvesoftware.Steam/.local/share/7DaysToDie $HOME/.local/share/




I can now run 7D2D from the non-Flatpak version, connect to EOS, and all my saves are there.

This seems to be an issue with Flatpak and how it handles certificates.
Click to expand...


Nice! Glad you got it working. Thanks for sharing how you fixed it, maybe someone down the line will run the game like this too and need this for help.

 
Flatpak's often have issues like this. It isn't very uncommon. Flatpak's and Snaps are basically cutting-edge newest version, and often do not have fully functional configurations.

It is generally advised to avoid them under all circumstances except when performing knowledgeable testing, or if you absolutely have to have a package that isn't already a part of your distribution, and you are incapable of adding the required 3rd-Party repository for it.  Kind of like the Windows Insider Builds.

 
The Flatpak version is now working. I just waited a few days and restarted Steam. Maybe it had something to do with launching the game from the package version of Steam once. Strange.

 
You must log in or register to reply here.
Back
Top