EDIT: restarting my router fixed the issue. I've also had successful feedback from another person who changed their MTU setting to 1397 and it worked for them. Try those two things. It might also be worth noting that after restoring licences, I had to re-verify my email address through Settings > PSN > Account Settings. I also changed my password for PSN. These things didn't fix the issue, but perhaps in combination with the restarting for the router, they helped resolve the issue.
"You have lost connection to Destiny servers. Your permissions to access online multiplayer gameplay may have changed or your profile may have been signed in elsewhere."
I can sign in to the character select screen, but once I select my character and it attempts to load the game, I get the above error. I can access PSN. Browsed the store ok. Even added some PS Plus games to my library. My subscription is current. Destiny was working perfectly last night. I tried restoring my licences through PSN settings. Power-cycled my PS4. No dice.
I have recently had lots of baboon errors and decided that it was due to the PS4 being connected via wireless. Few errors before this since Day 1 launch day. Maybe three in all the months I've been playing. Anyway, I decided to run an Ethernet cable to PS4. Worked fine. So today, I decided to change the channel that my Wi-Fi was running. No other changes. Just the channel. Reconfigured PS4 and connected to wireless and PSN ok. Then I try to sign in to Destiny and get the previously mentioned error in the first paragraph above.
So I switched back to LAN cable thinking it was the wireless again. Nope. Still can't sign in.
Someone from Bungie tell me what to do. I'm lost here.
-
I believe the issue is related to psn , if you got to network and choose the option , "view status of PlayStation network services" it shows that gaming and social is experiencing issues....it's a bummer , I was in the middle of getting thumus 😭
-
6 RepliesIm having this issue on my ps4 with Destiny 2. Its day 2 and i cant even log in and play. Tried all stated above no dice. Please fix Bungie or if any info on ones who have had sucess with other fixes please let me know. Thanks.
-
Why can't I play bungie? I checked the licenses, checked in the only PS4 active. And just brought 3 months today and activated it all properly working and I can not play. I am pissed
-
i have been having the same issues i have tried every MTU that was posted in this tread still not lettign me play good job bungie
-
2 Replies[quote]EDIT: restarting my router fixed the issue. I've also had successful feedback from another person who changed their MTU setting to 1397 and it worked for them. Try those two things. It might also be worth noting that after restoring licences, I had to re-verify my email address through Settings > PSN > Account Settings. I also changed my password for PSN. These things didn't fix the issue, but perhaps in combination with the restarting for the router, they helped resolve the issue. "You have lost connection to Destiny servers. Your permissions to access online multiplayer gameplay may have changed or your profile may have been signed in elsewhere." I can sign in to the character select screen, but once I select my character and it attempts to load the game, I get the above error. I can access PSN. Browsed the store ok. Even added some PS Plus games to my library. My subscription is current. Destiny was working perfectly last night. I tried restoring my licences through PSN settings. Power-cycled my PS4. No dice. I have recently had lots of baboon errors and decided that it was due to the PS4 being connected via wireless. Few errors before this since Day 1 launch day. Maybe three in all the months I've been playing. Anyway, I decided to run an Ethernet cable to PS4. Worked fine. So today, I decided to change the channel that my Wi-Fi was running. No other changes. Just the channel. Reconfigured PS4 and connected to wireless and PSN ok. Then I try to sign in to Destiny and get the previously mentioned error in the first paragraph above. So I switched back to LAN cable thinking it was the wireless again. Nope. Still can't sign in. Someone from Bungie tell me what to do. I'm lost here.[/quote] Same for me. I just bought psp yesterday and I turned off auto-renew. One day later this won't stop coming. Anyone help? I'm too lazy to figure it out on my own.
-
I got this same problem when I left a crucible game to go to another fire team. I brought one person over with me to the new fire team and it kicked both of us to the title screen. The game was showing that I was still in the new fire team even though I was in the tittle screen. The only way I got it to work was by deleting destiny and redownloading it. Hope this helps
-
2 RepliesI just had this issue when trying to change character, I restarted my console an that never worked, I restored my license agreement and that seemed to fix the issue
-
It worked thanks alot.😧
-
I am also having this issue as well. I have changed my MTU settings to the two that were listed below by any commenters. This is absolutely annoying.
-
3 Repliesmen thanks you soo much!!! i have this problem with destiny and list fried i changed MTU 1500 to 1397 and now is all working good, really thanks ;)
-
Same problem. All other games work fine, but not destiny. So basically, I paid for a game, played it for a year, then got pooped on when I decided I didn't want to pay for year 2, and now can't even play year one anymore. So thanks a lot for the horrible service, and let's not forget how full of problems year one was. I will never buy another Bungie game again. Ever. And I want my friggin' year one money back, since I can't access the content anymore. Screw you bungie.
-
3 RepliesJust change the MTU settings from 1500 to 1397 and it will work. Go to settings --> Network --> "adapt" internt settings --> and then at some point you will see MTU
-
2 RepliesSame here in Denmark/Europe for 3 days now..Bungie shits on their players and don't tell us ANYTHING or compensate for anything! And the best part of it....We let them do it to us again and again and again...
-
A lot of people reported the same error since last thursday. I had it myself, changed the MTU value to 1473 and it worked. But since then I'm having some NAT issues with the party chat. I never had them before. Bungie somehow messed with the comunication between their servers and PSN. No moderator showed up in any of the threads created to communicate an oficial position from Bungie. Try the MTU and good luck.
-
2 RepliesI had the same error (Germany, since Friday). I always waited for Xur and m first exotic). Now he got one I want and cant log in! Damn :(
-
1 ReplyEdited by philiphrz: 3/15/2015 9:13:34 AMSame here in Germany can't log in for 3 das now and I missen Xur...bullshit. And the Not eventuell have a real Support I mean you can't write an E-Mail to them or something like that!!!
-
2 RepliesSame here, Ive been getting the error code marionberry since the beginning of spring break down here in TX. Its very frustrating, Ive done what bungies help page advises but still nothing. Im pretty sure bungies servers simply cant handle everyone attempting to play and they just dont want to admit to their inadequacy to support its players.
-
1 Replymy 3rd day the same, network settings does not help
-
1 Replyi have the exact same problem since yesterday. the day before i played two pvp games after like 1-2 month break and cannot play with the same error when selecting character and waiting like 30 sec in the loading screen. i tried everything, deleting and reinstalling; restoring licenses; deleting my own profile. when i select my second account it works, only my main psn account isn't working for whatever reason.
-
2 Replies4th day already, and still the same problem. I'm convinced something happened at bungie servers to some people's profiles. Or psn servers... The point is, it's affecting a lot of people, and no one either at bungie or PSN is saying anything about it. At least a twitter post aknowledging =(
-
6 RepliesI'm having the same issue, I was on this morning then this afternoon I keep getting this error.