I am guessing that web sockets don’t run on a separate port anymore. I took out nginx and now directly connecting to zeppelin which is running fine on port 8001. I see this error in the chrome browser -
WebSocket connection to 'ws://ec2-197.compute-1.amazonaws.com:8001/ws' failed: Error during WebSocket handshake: Unexpected response code: 403 Any clues anyone? Best, Jitender > On Aug 19, 2015, at 1:16 PM, Jitender Aswani <jiten...@sparklinedata.com> > wrote: > > Hello guys, need some help from you. > > Did a new build (0.5 branch) this afternoon and started zeppelin on port 8001 > using export ZEPPELIN_PORT=8001 in zeppelin-env.sh file. > Web-socket server should have started on 8002 but it didn't. Chrome browser > is displaying following error in console. > > WebSocket connection to 'ws://ec2-52-4-253-197.compute-1.amazonaws.com/ws' > <ws://ec2-52-4-253-197.compute-1.amazonaws.com/ws'> failed: Error during > WebSocket handshake: Unexpected response code: 403 > > Checked for ports using netstat: > > tcp 0 0 0.0.0.0:80 0.0.0.0:* > LISTEN > tcp 0 0 :::8080 :::* > LISTEN > tcp 0 0 :::8081 :::* > LISTEN > tcp 0 0 :::8082 :::* > LISTEN > tcp 0 0 :::8083 :::* > LISTEN > tcp 0 0 :::8001 :::* > LISTEN > > I don’t see port 8002 here. No help from the logs. > > No issues with the previous version of zeppelin. Port 8002 was active and > listening. > tcp 0 0 :::8080 :::* > LISTEN > tcp 0 0 :::8081 :::* > LISTEN > tcp 0 0 :::8082 :::* > LISTEN > tcp 0 0 :::8083 :::* > LISTEN > tcp 0 0 :::8001 :::* > LISTEN > tcp 0 0 :::8002 :::* > LISTEN >
