We have noticed that wrong server port as well, @fancy-queen-20734. Also, @full-kilobyte-93429 I am testing 3003 internally today…we were a couple releases behind so I had to port our codebase up to HEAD.