What is error code 4:8:0?

[Ninesto]

I get this when after the game loads and start to sign in.

Vault-tec engineers are hard at work getting the servers back online!
(login queue) provide this code to Fallout 76 support for more information. 4:8:0

[Kurdt]

Same

[m_train1]

Google it.

[Kurdt]

Letting the process lsass connect to the internet fixed it. "Local security authority process"

[steventirey]

When I get a message like that, I just try again and it goes through without a problem. I assume its just the server hamsters running on their little wheels getting tired from working overtime, due to the new players who found Fallout 76 because of the show.

[mP3+Z]

The other companies usually offer a queue system when server is full and automatic login when there's free spot.
And Bethesda be like: Nah, I don't have time for this, just send them some error massage.

[DigiAngel]

Same here...after update, this message.

[Ninesto]

@kurdt - thanks but even with that process 100% active, still the same thing.

[trailofsevens]

Also getting this - I contacted support with the error code 4:8:0 and they closed my support ticket citing "duplicate support ticket" even though it was the first one I sent..
So I've now sent it again and it's gone unanswered for about 12 hours.

So far I've been trying to test everything that support might suggest, I've tried:
Restarting steam, the PC, the router
Verifying the steam files
Disabling firewall filtering for outbound
Disabling Antivirus
Updated GPU drivers
Reinstalling the whole game

No change, same error every time. The specific code on Google doesn't really give any solutions either and it's not covered in their own Bethesda support database either.

[Busy]

I cannot login today getting 4:8:0 all the time. They must have changed something that affects "a small percentage of players".

[Ninesto]

peeps, Kurdt actually nailed this. I looked further into the LSASS process, and my firewall was indeed blocking it. I unblocked it, and then when I fired up Fallout 76, the first thing the game asked for was access to LSASS and asked if I would allow it, I said yes, and I am back in game! So this worked.

Many thanks to Kurdt, because we all know Bethesda will not be answering our tickets.

[Ninesto]

the larger question is, why does Bethesda need access to this process, with outgoing communication, when this process typically has nothing to do with games, and no other online game I have played needs it.

[Funreaver]

I allowed the process and still no dice, glad it works for some.

[trailofsevens]

Originally posted by Ninesto:

peeps, Kurdt actually nailed this. I looked further into the LSASS process, and my firewall was indeed blocking it. I unblocked it, and then when I fired up Fallout 76, the first thing the game asked for was access to LSASS and asked if I would allow it, I said yes, and I am back in game! So this worked.

Many thanks to Kurdt, because we all know Bethesda will not be answering our tickets.

Good to hear it's working for you! I tried allowing it via my firewall when I first read that earlier and then kept trying it for a few hours, nothing worked, same error.
Then I've just booted the game up now hours later (no other changes) and it seems to have logged in.

So I can't confirm if it's lsass.exe or not really, since it didn't fix it when I initially made the firewall rule? Either way it's working at the moment so fingers crossed it'll stay that way.

[Lorrinar]

3rd day 4:8:0. Allowing lsass connect to the internet doesn't help.

[Ninesto]

Originally posted by trailofsevens:

Originally posted by Ninesto:

peeps, Kurdt actually nailed this. I looked further into the LSASS process, and my firewall was indeed blocking it. I unblocked it, and then when I fired up Fallout 76, the first thing the game asked for was access to LSASS and asked if I would allow it, I said yes, and I am back in game! So this worked.

Many thanks to Kurdt, because we all know Bethesda will not be answering our tickets.

Good to hear it's working for you! I tried allowing it via my firewall when I first read that earlier and then kept trying it for a few hours, nothing worked, same error.
Then I've just booted the game up now hours later (no other changes) and it seems to have logged in.

So I can't confirm if it's lsass.exe or not really, since it didn't fix it when I initially made the firewall rule? Either way it's working at the moment so fingers crossed it'll stay that way.

It is definitely LSASS, I experienced the same thing as you at first, simply allowing it did nothing until I rebooted, at which point the only thing the firewall asked for was LSASS. As a test, i reblocked LSASS, and the 4:8:0 error came up again.

I would have never thought this process could have been the issue, not sure how Kurdt even thought to look at this, but grateful he did!