-
There should be no difference between opening a connection from different clients. Can you compare the HTTP output in both the working and non-working cases?
When using -u, HTTP connections must be authenticated using basic authentication. If you are connecting from a browser, this will result in a small popup window asking for a user name and password. If you are using a non-browser client, you must make sure to pass the “Authorization” header correctly. This also applies to JavaScript and kdb+ clients – if you didn’t take care of passing the header, those should not be working either. (Although in the JavaScript case, if the JavaScript code is served by the same server as the one you are trying to connect to, you will have to have entered the user/password to fetch the JS so the credentials from there could get reused for the websocket connection).