Hi @edesz
A few things from the error logs.
For your bokeh app you state, …
If this is what results in the error log, that is expected behavior given the current configuration of the app. Specifically, see the lines
This line is letting you know that you get a blank page because a client is attempting to access the bokeh server app directly presumably by putting its URL in a web browser’s address bar. However, the app is configured so that only connections from the user-facing Heroku app are allowed.
That is exactly the use-case in my Heroku setup. The lower-level bokeh server that handles calculations and renders graphics for a bokeh document. The only thing that is allowed to access it is the separately running flask app, which pulls it in. (In my setup this model is used for conditionally accessing the document in a broader Flask app that has user registration and login capabilities as well as loading large datasets that can get passed to the bokeh app for analysis of data of interest to a specific user.)
So, if you need to access the bokeh app directly – say for testing purposes – you can allow other origins. Then, if you want to restrict things in a final deployment revert to the settings as you currently have.
Regarding the Flask app, I’m not sure what exactly is going on there. However, the Flask app logs show issues with the URLs being used, e.g. the {self.url} path-not-valid error in this snippet.
Are you using that syntax anywhere in your flask app? Generally in my Flask apps I use its url_for( ) syntax if I need to refer to a route in a redirect, etc.