same issue here with client 3.5, by just using a custom port, nasty bug !
no issue if I use client 3.4
