"Can't join party" when searching for matches, & it shows that it's my party it's trying to join.

[Netduma Fraser]

I think that probably is an authentication server, there are likely quite a few in that same location, keep allowing them as you see them if they're not allowed and that should stop the issue happening. If you could then copy/paste all the IDs you find we can then get that updated

[BLT]

That is the only one that I've been seeing today, but I'll post any other IDs that show up doing the same thing. Do you know how long it takes to get them updated? Just curious when the one I posted might get updated so I can see if that server update has helped or not?

[Netduma Fraser]

That's good to hear! It really depends, I can't give an accurate time frame really, usually we build up a cloud update and push it when there are enough changes

[BLT]

Here's another one that's doing the same thing; the IP address before the domain name is just one number off of the other one, & the ID is the same other than the 7 & 2 being a 6 & 1 in the initial one:

[Netduma Fraser]

Great thank you!

[BLT]

Here's one that doesn't even have a domain name, just a period where a domain should be. Still has a Host Type & ID, though. It's popped up multiple times today, this was just the only time I could get a screenshot in time.

[Netduma Fraser]

No need to get a screenshot, just a copy/paste of the ID is all we need. A screenshot is more hassle for both of us

[BLT]

I've been trying to, but a lot of the time it only shows for a couple seconds & I'm not able to, so I just hit my screenshot button that takes a snapshot of that specific moment before it disappears, then crop it to just show the needed info. I can just type the info into the posts after getting the screenshots instead of sending the screenshots, though. I'll start doing that if it helps on your end!

[Netduma Fraser]

That would be helpful thanks! If you're clicking allow on them then you can go back and re-name/ping them later so you don't need to try to rush a screenshot

[BLT]

Clicking allow on them made the problem happen more often, so I deleted them from the list & they're neither blocked or allowed, although the error was less frequent when they were blocked, like I had originally done.

[Netduma Fraser]

1 hour ago, BLT said:

Clicking allow on them made the problem happen more often, so I deleted them from the list & they're neither blocked or allowed, although the error was less frequent when they were blocked, like I had originally done.

It might be a scenario where it gets worse before it gets better - we'd be allowing them so probably a good idea to try allowing them all and see if it stops the issue completely