JavaScript is required to use Bungie.net

Help

Help us help you.

This thread is inspired by another: view original post

Edited by Blaubarschboy: 9/15/2014 1:31:55 PM
9

#Bee Error - Help Thread

I opened this Thread to collect all players with the #Bee error. Post your suggestions on how to fix it or what you think could Bungie do to fix it for us. I want to get the #Bee error out of my sight as soon as possible so let's help together! What i tried so far: - Static IP on my Xbox One - Portforwarding for this static IP of my Xbox One to all Bungie related ports and the Xbox Live ports - restarted the Console - restarted my router - NAT Type is "open" [u][b]Bungie tells us on their help site to open the following ports:[/b][/u] - 7500-17899 (TCP) - 30000-40399 (TCP) - 35000-35099 (UDP) - 3074 (UDP) [u][b]and the following for Xbox Live:[/b][/u] - 88 (UDP) - 3074 (UDP und TCP) - 53 (UDP und TCP) - 80 (TCP) - 500 (UDP) - 3544 (UDP) - 4500 (UDP) [u]And you should use a wired connection (LAN)[/u] For me it did not help so far... EDIT: i only get this error after playing crucible / pvp for about 5-10 minutes. I only was able to finish 2 games so far.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • I only get bee when I try to play a strike mission...haven't tried cruicible yet because I want to get to that once everything is fixed. Other than that I get other errors occasionally while playing story missions

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon