Issues caused by 3rd party mods/addons are not an ArmA3 Feedback Tracker matter.
Check both server side and client side the correct ACRE installation. It works just fine on my clan's server (which i am main admin of) with latest DEV build and ACRE mod enabled.

You may want to check your RPT file(s) (both server and client side) for errors

//EDIT:
I see you have both @CBA_A3 and @UOCBA_A3.. something tells me that they conflict each other.. ACRE works fine with @UOCBA_A3 only

//EDIT2:
After checking your RPT file turns out:

ERROR (may be caused by 2 CBA working together)
Exception code: C0000005 ACCESS_VIOLATION at 00C57881
Allocator: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\dll\tbb4malloc_bi.dll

From the very first lines of the addons list
Addons:

cba_ai in x\cba\addons\ai\, cba_network in x\cba\addons\network\
cba_ui in x\cba\addons\ui\

I've tried with either CBA_A3 or UOCBA_A3 none of them seem to work or make any difference

I doubt they are any of the aforementioned, as I mentioned, testing acre on other public acre servers shows that it's working as intended but only on the clan server I'm playing on I'm experiencing these issues. Which RPT file should I look into there's many?

It has something to do with the steam error null issue and the patch all together, because like I said, using either CBA_A3 or UOCBA_A3 makes no difference I still can't connect properly to server, I'm still going to receive endless data because something has messed it up.

This same thing happens to me. We're both on the same server. We both have the same mods as everyone else.

I'm only able to spawn in on the start of a game (sometimes) if I do get in my ACRE is not working.

I encounter this issue on public servers as well without mods installed on latest Alpha version.

And for all of you who thinks this is a mod issue IT'S NOT, the MODS are working on any other server BESIDES the one I'm trying to join with issues.

2 WEEKS AGO IT WAS WORKING JUST FINE

Have the same issue, only JIP, no mods.

possibly a duplicate of 0008328

0008328

says its fixed, today's stable didn't fix it.

Definitely needs better error handling and understandable end user error message.

Issue closed as obsolete. If you encounter this problem again, please create another ticket. Thank you.