The Dead by Daylight team would like your feedback in a Player Satisfaction survey! https://dbd.game/4dbgMEM

FAILED TO JOIN THE GAME - COMMUNITY CASES

135

Comments

  • karaagepan
    karaagepan Member Posts: 2
    Player ID: b28e4dc3-73f3-430f-98a7-682e680e64eb
    Exact time the game client started to fail to join games:22:41(Japan Time)
    The exact times you tried to join a game again:22:42(Japan Time)
  • smm
    smm Member Posts: 1
    edited October 2018

    ID:d3069db8-2d50-4777-80ad-5cea100d1780

    Exact time :  September 24〜All time(Japan Time)

    Hello. I have continued this bug since the BP2 event end even after the update.

    (PS4 Download.no disc)


    Post edited by smm on
  • aoiyusa
    aoiyusa Member Posts: 1
    ・Player Cloud ID:73d583dd-9f6d-4200-8c5d-9e864f0fd54f
    ・From the day after the previous event ends.(Japan Time. )
    ・The exact times you tried to join a game again:23:06(Japan Time.)
  • psychoboi
    psychoboi Member Posts: 1

    Player id:a74c969e-2c49-4aa1-of79-85f39d07da9b like other people said it happens after every game and lasts around 4 minutes every time

  • skgc4785
    skgc4785 Member Posts: 1
    7e256490-519b-11e7-9173-f7c6ea856d63
    24:00（japan time）
    24:00（japan time）
  • akzwttfm
    akzwttfm Member Posts: 4

    Player ID:ab113724-8adc-418a-a7c9-c6f59b67a4a5
    2.3.0 Patch came, but this issue has not been resolved.

  • suzukiti
    suzukiti Member Posts: 1

    ・Player ID: 6163916f-ac17-4a41-80ff-ba8a0c42297e
    This problem started happening about 3weeks ago.
    It happens after every game and doesn't load for 3-5 minutes.
    The last time it happened was today at 0:33am(JST)
    Playing on PS4

  • sch
    sch Member Posts: 1

    Player ID:fb37f2cd-58c4-4d4d-adaf-a4b7b2522744
    It’s been happening after equinox bloodhunt event in Japan.
    It happens after every game,killer and survivor,and I always wait for a few minutes.It looks like loading the game. Even it is solved, I cannot sometimes invite my friends in the game until I restart the app.

  • miya38gou
    miya38gou Member Posts: 1

    Player Cloud ID :  3fbfe3fc-ed39-4ee9-a4fc-74dd840c61c3

    Exact time(Japan Time) :  Everytime I finish a match, white circle show up in a lobby and I cannot do anything for 2or3 minutes. After a white circle is gone, I can start pressing a button. So, could you please fix this problem? It happenes after Yamaoka update. My PS ID is MIYA38GOU. Thank you.

  • nujipon
    nujipon Member Posts: 1

    Player ID (under in-game SETTINGS)　5f3b50f8-3b53-427e-8f44-e6f74e2324cd

    its been happening for about 3 weeks

    The exact times you tried to join a game again 1:01（Japan Time）

  • Khalednazari
    Khalednazari Member Posts: 1,433
    This thread just blew up with Japanese players reporting the issue. Seems like it has affected more players than initially thought. 
  • CheeKiller95
    CheeKiller95 Member Posts: 15
    edited October 2018
    -
    Player-ID: f15bc58e-2450-4250-a945-6e44c0b50d2c
    having this issue since like september probably when the update came out and it happens after every game and i have to wait 3 minutes until i can Search a lobby again
  • Bing_bong
    Bing_bong Member Posts: 3
    Can you tell me the date of the next double bloodpoints?
  • Bing_bong
    Bing_bong Member Posts: 3
    And can you fix the glitch i experienced where you buy a perk in the shrine of secrets e.g. bond then you lose connection. You lose the shards but you don't get it teachable
  • Wahara
    Wahara Member Posts: 237

    Player CLOUD ID: 40343018-52d8-4017-8513-e26f158278df

    Time: Exact time unknown. It was roughly three days ago, it started shortly after I had purchased the spirit with iridescent shards.

    Time I retried: Right away. I was just locked out of every game. I tried for hours each day and as a survivor, all I would get is an infinite "waiting" icon. I couldn't even join a lobby. As killer, I could create a lobby but not a single person could join. When I would cancel the join lobby function for survivor, it wouldn't let me back out to the home screen right away. It would take awhile of pressing the back button but then finally would say "Host unreachable"

    This continued for two straight days with no sign of letting up despite hooking up anethernet cable, reinstalling the app, closing the application, testing internet connection, resetting router and restarting the PS4. I contacted my ISP to see if anything was up, and nothing has changed, I have no data cap.

    It has been only recently that I can occasionally play a game, but only as killer, and I'm lucky to get 1 after several hours of trying, cycling back and forth between testing internet connection before a game and restarting the PS4.

    There's a problem and it ain't me.

  • Luckystrike2778
    Luckystrike2778 Member Posts: 63

    So obviously no fix for this yet. PS4

  • Sorara
    Sorara Member Posts: 1

    Player ID : 3b014ffd-7363-40b4-8a3c-6e086b7dff638
    its been happening for about 2-3 weeks
    Exact times: it happens after every game and doesn’t load for about 2 - 3 minutes or until I restart the game

  • hum
    hum Member Posts: 2

    Player Cloud ID
    b8b572b0-a026-11e7-8614-21c435d16bf1

    Exact time 18th October 13:34(Japan Time)

    The exact times you tried to join a game again 18th October 13:34(Japan Time)

  • IbiLeZombie
    IbiLeZombie Member Posts: 1
    Player ID : 919e68f7-25be-449f-9116-123b3452f875 (PS4)
    Exact time it started : roughly three weeks ago
    Exact times I tried to join a game : every single game I played since, the latest ones being today 18th of October at 11.38 AM and 11.53 PM (GMT+1)
  • vb37kt
    vb37kt Member Posts: 1
    ・playerID e02c18c1-6f90-4aef-9ebc-94f5efa9eb07
    ・Exact time:18th oct,Thursday（Japan Time）
    ・18th oct, Thursday 9:47pm
  • mcfcuki
    mcfcuki Member Posts: 1

    Player ID d7e0bf82-188c-4c5d-8c4c-cdb7738b9bc4
    From about 3 weeks ago
    Waiting time is 2-3 minutes

  • afj0902
    afj0902 Member Posts: 1
    Player ID: a77be148-db14-4c0a-91a1-610bc0c96
    Exact time: 12th October 22:56 JPN
    fail to join the game  after finishing a game.



  • ricky_sanfi
    ricky_sanfi Member Posts: 1
    Player id: 7ee030f7-0970-43f2-8913-1f9dc18b171d
    I hate this bug... i can't play whit this.
  • tomoking
    tomoking Member Posts: 1

    Player ID : 389bea22-2b4a-42b3-ba76-c615769b7d51
    its been happening for about 2-3 weeks
    Exact times: it happens after every game and I must wait for 3 minutes until i can Search a lobby again

  • aximov
    aximov Member Posts: 4
    edited October 2018

    Player ID: 2a6ddb2a-b85b-499c-978f-86a5177f2313
    Exact time the game client started to fail to join games: I bought DbD at 22:50 JST (UTC+9) Oct 18, finished downloading around 23:20 JST Oct 18, and I'm experiencing this since my second game (I got disconnected from the host in the first game). So the exact time seems 23:40 JST Oct 18.
    The exact times you tried to join a game again: Every game excluding the first one.

  • clover9608
    clover9608 Member Posts: 5

    ID:3c622a45-599b-43aa-aed9-c0247669a2d7


    I reviewed and improved the method of connecting the Internet to PS4.

    Improvement by changing connection method to PPPoE. If the problem is not solved even now, please try it.

  • chanti_072
    chanti_072 Member Posts: 2
    Player ID: 95b93f6a-7777-4a21-a931-211b7d881d6f
    problem begun exactly one hour after the shattered bloodline dlc!! 
    i tried to get a game last sunday
    until now i didn't 


  • Timmy_c
    Timmy_c Member Posts: 1

    Player ID : 0bc23a90-a762-412b-8408-038f403e2941

    Exact time : The end of September ～ Every time after the match(Japan time)

  • rebelhunter316
    rebelhunter316 Member Posts: 102
    People from Japan are having this issue seems this bug is becoming more of a hassle than anything.  It's kind of sad developers can't even recreate the problem.  I hope they're using the information to players are giving them to recreate the problem.
  • Rcsordas
    Rcsordas Member Posts: 2
    edited October 2018
    Player ID b2728722-0c40-4db0-9f5c-4b615e47d69f
    Exact time: 22:47 GMT -2 (Brazil).
    Tried to join again 20 times whenever the error comes. 

    I realized this error started when I downloaded The Lullaby for the Dark Chapter from the PSN store for free.
    I had no expansion before that.
    It's the only expansion I have.
    Hope this can help the team simulate the error.
  • raquelambersantiago
    raquelambersantiago Member Posts: 373

    I didn't get this specific issue what I have been getting is forever load screens so when I control alt delete to check on status I see that DBD is Suspended during the load screen

  • micha
    micha Member Posts: 1

    Nice to meet you
    I am allowed to play on the PS4 version on the Japanese server.
    I was also in trouble because it took me some time to re-match.
    Thank you enough for improvement.
    Player ID:8632e6b7-5025-4a76-a000-32b2b14e64f
    Date and time:
    Every time I play from around 1 month ago

    I am sorry in English I understand but thank you.

  • Entità
    Entità Member Posts: 1,583
    Set PS4 port to NAT1: it fixed that unpleasant bug in my game experience.
  • nemeios
    nemeios Member Posts: 36

    This bugs happens always after every game, it happens for around 1-2 min and on both sides (survivor or killer)

    please fix this!!
    here is my id.

  • Entità
    Entità Member Posts: 1,583
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

  • Khalednazari
    Khalednazari Member Posts: 1,433
    Entità said:
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

    Hmm. I have a wired connection. I still don't have NAT type 1.
  • Khalednazari
    Khalednazari Member Posts: 1,433
    Entità said:
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

    @not_Queen if this can help. 
  • Entità
    Entità Member Posts: 1,583
    edited October 2018
    Khalednazari said:
    Entità said:
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

    Hmm. I have a wired connection. I still don't have NAT type 1.
    I use the LAN connection, my friend a wireless: both we have set NAT1 port.

    Go to Connection Settings of your PS4 and follow che custom procedure: choose wired o wireless, select PPPoE, insert the proper username and password (they depend on your provider), then set 8.8.8.8 and 8.8.4.4 as primary and secondary DNS, then select "Manual" and digit 1500 (optic fiber) or 1492 (ADSL2+) in the MTU form and lastly set "No proxy": when you verify your connection, you'll see if NAT type has changed or not.

    @not_Queen I read (and used succesfully) this procedure in an Italian forum about PS4, but I hope it will fix the bug everywhere.
    Post edited by Entità on
  • Dwightfrfld
    Dwightfrfld Member Posts: 5
    Player id: 199fb260-11e7-9998-31e55fdbfd64
    Exact time: 3:16
    Amount of times that I tried joining a game after this: about 5 times
  • Entità
    Entità Member Posts: 1,583
    Dwightfrfld said:
    Player id: 199fb260-11e7-9998-31e55fdbfd64
    Exact time: 3:16
    Amount of times that I tried joining a game after this: about 5 times
    Where are you from? Have you tried to set NAT1 on the PS4, as described before? It could fix the bug...
  • momiji
    momiji Member Posts: 2
    ID:1d863147-75ff-469a-8e14-22dfcaf152ef
    2.October
     Exact time:2-4minutes
  • rebelhunter316
    rebelhunter316 Member Posts: 102
    Entità said:
    Khalednazari said:
    Entità said:
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

    Hmm. I have a wired connection. I still don't have NAT type 1.
    I use the LAN connection, my friend a wireless: both we have set NAT1 port.

    Go to Connection Settings of your PS4 and follow che custom procedure: choose wired o wireless, select PPPoE, insert the proper username and password (they depend on your provider), then set 8.8.8.8 and 8.8.4.4 as primary and secondary DNS, then select "Manual" and digit 1500 (optic fiber) or 1492 (ADSL2+) in the MTU form and lastly set "No proxy": when you verify your connection, you'll see if NAT type has changed or not.

    @not_Queen I read (and used succesfully) this procedure in an Italian forum about PS4, but I hope it will fix the bug everywhere.
    Does this work for Wi-Fi?
  • rebelhunter316
    rebelhunter316 Member Posts: 102
    Entità said:
    Khalednazari said:
    Entità said:
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

    Hmm. I have a wired connection. I still don't have NAT type 1.
    I use the LAN connection, my friend a wireless: both we have set NAT1 port.

    Go to Connection Settings of your PS4 and follow che custom procedure: choose wired o wireless, select PPPoE, insert the proper username and password (they depend on your provider), then set 8.8.8.8 and 8.8.4.4 as primary and secondary DNS, then select "Manual" and digit 1500 (optic fiber) or 1492 (ADSL2+) in the MTU form and lastly set "No proxy": when you verify your connection, you'll see if NAT type has changed or not.

    @not_Queen I read (and used succesfully) this procedure in an Italian forum about PS4, but I hope it will fix the bug everywhere.
    Does this work for Wi-Fi?
  • coolurjets
    coolurjets Member Posts: 2
    User ID 1906ab90-98f0-11e7-ae46-8188dfd61556

    cant remember the first time, it’s been about a month. 

    Playing right now and it’s still happening 
  • Entità
    Entità Member Posts: 1,583
    rebelhunter316 said:
    Entità said:
    Khalednazari said:
    Entità said:
    I fixed that bug by setting my PS4 port to NAT1 in the Connection Settings. On the Net there are many tutorials about the correct procedure, which depends on the provider.

    Hmm. I have a wired connection. I still don't have NAT type 1.
    I use the LAN connection, my friend a wireless: both we have set NAT1 port.

    Go to Connection Settings of your PS4 and follow che custom procedure: choose wired o wireless, select PPPoE, insert the proper username and password (they depend on your provider), then set 8.8.8.8 and 8.8.4.4 as primary and secondary DNS, then select "Manual" and digit 1500 (optic fiber) or 1492 (ADSL2+) in the MTU form and lastly set "No proxy": when you verify your connection, you'll see if NAT type has changed or not.

    @not_Queen I read (and used succesfully) this procedure in an Italian forum about PS4, but I hope it will fix the bug everywhere.
    Does this work for Wi-Fi?
    I think yes. NAT1 is useful in any case: it should increase the speed, reducing the lag.
  • Condorloco_26
    Condorloco_26 Member Posts: 1,714

    Any news on this? We're still getting it after every match ends.

  • akzwttfm
    akzwttfm Member Posts: 4

    Player ID:ab113724-8adc-418a-a7c9-c6f59b67a4a5
    In my PS4 this problem no longer occurs from yesterday.

  • Bancho
    Bancho Member Posts: 3

    As soon as The Hallowed Blight Event began, this event ceased to occur.
    Changes in NAT that are raised in the forum are not implemented.

  • Entità
    Entità Member Posts: 1,583
    edited October 2018
    Bancho said:

    As soon as The Hallowed Blight Event began, this event ceased to occur.
    Changes in NAT that are raised in the forum are not implemented.

    Changes in NAT are a personal fix of a common bug: they don't affect the game programming, of course, but prevent the problem to occur in your own game experience.

    If devs solved it generally, what a great info!

  • Khalednazari
    Khalednazari Member Posts: 1,433
    It didn't get solved for me yet.