I couldn’t apply the patch. I guess I am going to wait for this error to be fixed (looks like today it being pulled into the main trunk). Appreciate the help. This error is annoying for older users of Zeppelin on AWS.
Cheers! > On Aug 19, 2015, at 6:03 PM, Corneau Damien <cornead...@gmail.com> wrote: > > This is a known issue, and I think it is being handled here: > https://issues.apache.org/jira/browse/ZEPPELIN-231 > <https://issues.apache.org/jira/browse/ZEPPELIN-231> > On Aug 20, 2015 9:09 AM, "Chad Timmins" <ctimm...@trulia.com > <mailto:ctimm...@trulia.com>> wrote: > Hi, > > I had the same thing happen to me this morning and get the same exact error. > Did you figure this out? > > From: Jitender Aswani <jiten...@sparklinedata.com > <mailto:jiten...@sparklinedata.com>> > Reply-To: "users@zeppelin.incubator.apache.org > <mailto:users@zeppelin.incubator.apache.org>" > <users@zeppelin.incubator.apache.org > <mailto:users@zeppelin.incubator.apache.org>> > Date: Wednesday, August 19, 2015 at 2:02 PM > To: "users@zeppelin.incubator.apache.org > <mailto:users@zeppelin.incubator.apache.org>" > <users@zeppelin.incubator.apache.org > <mailto:users@zeppelin.incubator.apache.org>> > Subject: Re: Did new build and web sockets are not working anymore > > 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 >> <mailto: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' >> <> failed: Error during WebSocket handshake: Unexpected response code: 403 >> >> Checked for ports using netstat: >> >> tcp 0 0 0.0.0.0:80 <http://0.0.0.0/> 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 >> >
