Ce n’est pas ce que vous cherchez ?

Nouvelle publication
Bungie Answered

Constant Paprika and Basil Errors (5+ attempts to login, 5+ attempts to deploy into a run)

Both errors are super frustrating to just sit wait and try again, more so when there is a full lobby of three people that have to constantly ready up again and having to deploy again.

To be clear I am not experiencing disconnections in game. This is only when attempting to sign into the menu/deploying for a run.

In game no issues at all. 

 

Platform: PC 

Port forwarded per the advanced guide (Don't see a way in game to validate NAT?)

Geographical Region: South East Us across states

ISP: ATT Fiber

 

Error: paprika

Additional code: W:8:00002EF1

 

Error: basil

Additional code: W:8:00002EF1

4

Commentaires

9 commentaires
  • Commentaire officiel

    Hello there,

    Thank you for reaching out.

    If you’re encountering the PAPRIKA and BASIL Error Codes, please try logging out of the game and back in to see if it resolves the issue.

    If that doesn’t help and there is no scheduled maintenance, please refer to our Network Troubleshooting Guide to explore potential solutions to the problem.

  • having this same problem

    1
  • Same happens to me. First time I try to log in to main menu I get error. Every first time I try to match make I get basil error. I can get in if I immediately try entering again. After I play a round the same thing occurs.

    1
  • Update: When playing with Console friends using cross play, they get the error alongside me but they report that when it's a console only crew this error does not appear so seems to be PC Specific.

    1
  • Hey thanks for reaching out. Obviously I am getting the same error. My symptoms are just like yours. Its no the end all be all, but it is very irritating having to hold teammates up

    1
  • @bungie support.

    I’ve followed your network troubleshooting section and even have the ports required and suggested forwarded (though I don’t see anywhere in game to check NAT status)
    Networking wise no other game or service has these disconnects.
    Also the error persists across logouts/logins across multiple days. And as you can see it isn’t just 1 user that is getting these errors. I’m happy to help how I can by provide wireshark capture files etc.

    1
  • Update: Error Persists After 1.0.0.4 update

    1
  • @Thread
    Here is a template on what information you can provide to make your report as impactful as possible for Bungie.

    • Bungie Account Name - Atlas#7076,
    • Platform - Steam
    • Description of Issue - Takes multiple times to login to the game/ deploy into a run. 
    • Rough Date and Time of issue - 3/12/2026 @ 11:59am EST
    • Repro steps - Attempt to login into game at any time of day, attempt to deploy into run at any time of of day.
    • More Info:

      Port forwarded per the advanced guide (Don't see a way in game to validate NAT?)

      Geographical Region: South East Us across states

      ISP: ATT Fiber

      Error: paprika

      Additional code: W:8:00002EF1

      Error: basil

      Additional code: W:8:00002EF1

    1
  • update 

    im on starlink and using a VPN to do port forwarding fixed my issue

    0

Vous devez vous connecter pour laisser un commentaire.