Re: Re: Re :Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-23 Thread J K via nginx
To: J K via nginx > Cc: J K > Subject: Re: Re :Re: Re:Reverse-proxying: Flask app with Bokeh server > on Nginx > Message-ID: <20170516164907.ge10...@daoine.org> > Content-Type: text/plain; charset=utf-8 > > On Mon, May 15, 2017 at 11:59:27AM +0200, J K via nginx wr

Re: Re: Re :Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-17 Thread Francis Daly
On Wed, May 17, 2017 at 12:34:17PM +0200, J K via nginx wrote: Hi there, > Initially, without https, everything was running well. Yes. > I was deploying a > Bokeh server with the 'company_abc' app, and used a Flask app to render the > website and handle login/redirecting/etc. Yes. > Everythin

Re: Re: Re :Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-17 Thread J K via nginx
ny_abc/",session_id= session.id,url=url_https) The Bokeh log file says that a WebSocket is opened and a ServerConnection is created: 2017-05-17 10:21:09,915 WebSocket connection opened 2017-05-17 10:21:10,769 ServerConnection created What does the new error mean? Why is a WebSocket opened

Re: Re :Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-16 Thread Francis Daly
On Mon, May 15, 2017 at 11:59:27AM +0200, J K via nginx wrote: Hi there, To recap: you had installed a "flask" web server and a "bokeh" web server. You put the "flask" one behind nginx, so that clients would talk to nginx and to bokeh. And the clients were happy to talk http to nginx and http t

Re :Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-15 Thread J K via nginx
> > Message: 4 > Date: Fri, 12 May 2017 18:26:39 +0300 > From: "Reinis Rozitis" > To: > Subject: Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx > Message-ID: <437D05EFD1A24D9292CCE7BE45B2127C@Neiroze> > Content-Type: text/plain; format=flowe

Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-12 Thread Reinis Rozitis
What I forgot to add you need to change the 'url' (note the domain part) to: url='https://yourdomain/bokeh/' by looking at your error messages it seems that the 'url' is also directly used for client requests (probably placed in the html templated) - which means you can't use plain IP because

Re: Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-12 Thread Reinis Rozitis
3. in the Flask app, I changed the URL to:url='https://138.197.132.46:5006/bokeh/' Now, when I open the app in the browser I get a 502 Bad Gateway, and the Flask log file says the following: raise IOError("Cannot pull session document because we failed to connect to the server (to start the ser

Re:Reverse-proxying: Flask app with Bokeh server on Nginx

2017-05-12 Thread J K via nginx
> > Message: 2 > Date: Fri, 12 May 2017 13:33:16 +0300 > From: "Reinis Rozitis" > To: > Subject: Re: Reverse-proxying: Flask app with Bokeh server on Nginx > Message-ID: > Content-Type: text/plain; format=flowed; charset="UTF-8"; > reply-type=original > > > I understand that I might have