>From the screenshot it looks as though only /nifi is getting through the proxy. Even requests for resources under /nifi don't seem to get through. I see from your configuration that it looks like you've mapped the root context path so everything should get through (not just /nifi). NiFi is comprised of a number of web applications (UI, API, docs, Custom UIs, etc) so mapping from the root context path is required.
Is there any additionally logging at the proxy that might provide more insight regarding the requests. Matt On Tue, Mar 15, 2016 at 7:56 AM, michail salichos < [email protected]> wrote: > Hello, > > Please find attached a screenshot. > > As you might see, it loads the page but missing all subsequent requests. > > To answer your question I am still far from reaching the canvas! > > Regards, > Michail > > On Tue, Mar 15, 2016 at 12:43 PM, Matt Gilman <[email protected]> > wrote: > >> Just to clarify, the NiFi UI loads however subsequent requests fail? Like >> moving a processor on the canvas. >> >> Matt >> >> Sent from my iPhone >> >> On Mar 15, 2016, at 3:30 AM, michail salichos <[email protected]> >> wrote: >> >> Hello, >> >> Just tried "proxy_pass_header Server;" but still no luck, subsequent >> requests are being issued but I keep getting 404. >> >> Regards, >> Michail >> >> On Mon, Mar 14, 2016 at 5:35 PM, James Wing <[email protected]> wrote: >> >>> You may also need to pass the Server header, I believe some server-side >>> UI code uses this to format client-side resource locations. >>> >>> proxy_pass_header Server; >>> >>> >>> >>> On Mon, Mar 14, 2016 at 8:54 AM, michail salichos < >>> [email protected]> wrote: >>> >>>> Hello, >>>> >>>> I tried adding ssl param but still no luck. As I said with plan http >>>> location block works just fine, but when I move the location block to https >>>> it issues the first get http request for NIFI main page (it downloads >>>> unformatted - without css, js, etc) and all subsequent http requests are >>>> failing with 404 not found. >>>> >>>> Thanks again, >>>> Michail >>>> >>>> On Mon, Mar 14, 2016 at 4:01 PM, Aldrin Piri <[email protected]> >>>> wrote: >>>> >>>>> Michail, >>>>> >>>>> Looks like you are missing your "ssl" parameter on your listen >>>>> statement. [1] Not sure if that is the issue, but the rest looks okay >>>>> from >>>>> inspection. >>>>> >>>>> >>>>> [1] http://nginx.org/en/docs/http/configuring_https_servers.html >>>>> >>>>> On Mon, Mar 14, 2016 at 10:56 AM, michail salichos < >>>>> [email protected]> wrote: >>>>> >>>>>> I forgot to mention, since you asked, for zeppelin, elasticsearch, >>>>>> kibana and others services ssl termination and reverse forwarding works >>>>>> just fine, only NIFI is giving me troubles. >>>>>> >>>>>> Regards, >>>>>> Michail >>>>>> >>>>>> On Mon, Mar 14, 2016 at 3:47 PM, Aldrin Piri <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Michall, >>>>>>> >>>>>>> A bit outside of the NiFi realm, but I have done similar myself >>>>>>> previously. Do you have your server block (likely the one containing >>>>>>> this >>>>>>> location block) established with the appropriate certificates and a >>>>>>> listen >>>>>>> statement with ssl listed after the port? From memory, I do not believe >>>>>>> any >>>>>>> overwriting of the headers should be needed. >>>>>>> >>>>>>> Is the problem strictly with NiFi? Are there any other services >>>>>>> running where this is not an issue? >>>>>>> >>>>>>> On Mon, Mar 14, 2016 at 10:36 AM, michail salichos < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I followed the instructions here >>>>>>>> >>>>>>>> https://www.mail-archive.com/[email protected]/msg00566.html >>>>>>>> >>>>>>>> and managed to configure nginx as reverse proxy for HTTP, it works >>>>>>>> well. >>>>>>>> >>>>>>>> However, no matter what I tried I can't configure to terminate >>>>>>>> HTTPS on nginx and then use plain HTTP to communicate with NIFI. This >>>>>>>> is >>>>>>>> the config I am currently using for HTTP and it works >>>>>>>> >>>>>>>> location /nifi { >>>>>>>> proxy_pass http://nifi:8080; >>>>>>>> proxy_set_header X-ProxyScheme "http"; >>>>>>>> proxy_set_header X-ProxyHost $http_host; >>>>>>>> proxy_set_header X-ProxyPort 80; >>>>>>>> proxy_set_header X-ProxyContextPath ""; >>>>>>>> } >>>>>>>> >>>>>>>> I tried to change the scheme to HTTPS and port to 443 but no luck. >>>>>>>> >>>>>>>> Any tips or hints? >>>>>>>> >>>>>>>> >>>>>>>> Regards, >>>>>>>> Michail >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
