Proxying nifi using nginxIn Nginx, how can I rewrite all http requests to https while maintaining sub-domain?Reverse proxying HTTPS from nginx to ApacheProxying webmin with nginxreverse proxying with NGINX to two back-end serversnginx doesn't check server_name and port on websocket proxyingnginx proxying requests to wrong backendNginx proxy_pass reverse proxying behind corporate firewallNGINX not proxying to the right server?Nginx tries to open static files instead of proxying themnginx redirects instead of proxying
Storing voxels for a voxel Engine in C++
How did the Allies achieve air superiority on Sicily?
To exponential digit growth and beyond!
Why A=2 and B=1 in the call signs for Spirit and Opportunity?
Why do testers need root cause analysis?
The disk image is 497GB smaller than the target device
Navigating a quick return to previous employer
Who wrote “A writer only begins a book. A reader finishes it.”
Why did it take so long for Germany to allow electric scooters / e-rollers on the roads?
How to remove new line added by readarray when using a delimiter?
Level capping of loot in Borderlands 2
How would a developer who mostly fixed bugs for years at a company call out their contributions in their CV?
How does the Earth's center produce heat?
How can I get a refund from a seller who only accepts Zelle?
Cisco 3750X Power Cable
Why'd a rational buyer offer to buy with no conditions precedent?
resolution bandwidth
Did significant numbers of Japanese officers escape prosecution during the Tokyo Trials?
Are PMR446 walkie-talkies legal in Switzerland?
Are there any German nonsense poems (Jabberwocky)?
Writing "hahaha" versus describing the laugh
If I arrive in the UK, and then head to mainland Europe, does my Schengen visa 90 day limit start when I arrived in the UK, or mainland Europe?
Why does the painters tape have to be blue?
Why is 'additive' EQ more difficult to use than 'subtractive'?
Proxying nifi using nginx
In Nginx, how can I rewrite all http requests to https while maintaining sub-domain?Reverse proxying HTTPS from nginx to ApacheProxying webmin with nginxreverse proxying with NGINX to two back-end serversnginx doesn't check server_name and port on websocket proxyingnginx proxying requests to wrong backendNginx proxy_pass reverse proxying behind corporate firewallNGINX not proxying to the right server?Nginx tries to open static files instead of proxying themnginx redirects instead of proxying
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I want to use an https nginx to proxy a non-secured nifi server running in the same box.
So far the closest I get is by using this configuration:
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969/nifi;
In nifi I get the exception:
2018-11-24 17:40:19,473 ERROR [NiFi Web Server-20] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []. Returning Internal Server Error response.
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []
at org.apache.nifi.web.util.WebUtils.verifyContextPath(WebUtils.java:152)
at org.apache.nifi.web.util.WebUtils.getResourcePath(WebUtils.java:125)
at org.apache.nifi.web.api.ApplicationResource.buildResourceUri(ApplicationResource.java:159)
at org.apache.nifi.web.api.ApplicationResource.generateResourceUri(ApplicationResource.java:141)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntityContent(ProcessorResource.java:107)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntitiesContent(ProcessorResource.java:95)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowStructure(FlowResource.java:200)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowContent(FlowResource.java:187)
at org.apache.nifi.web.api.FlowResource.getFlow(FlowResource.java:373)
Any hints?
nginx reverse-proxy nifi
asked Nov 24 '18 at 11:07
xainxain
3891821
add a comment |
I want to use an https nginx to proxy a non-secured nifi server running in the same box.
So far the closest I get is by using this configuration:
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969/nifi;
In nifi I get the exception:
2018-11-24 17:40:19,473 ERROR [NiFi Web Server-20] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []. Returning Internal Server Error response.
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []
at org.apache.nifi.web.util.WebUtils.verifyContextPath(WebUtils.java:152)
at org.apache.nifi.web.util.WebUtils.getResourcePath(WebUtils.java:125)
at org.apache.nifi.web.api.ApplicationResource.buildResourceUri(ApplicationResource.java:159)
at org.apache.nifi.web.api.ApplicationResource.generateResourceUri(ApplicationResource.java:141)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntityContent(ProcessorResource.java:107)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntitiesContent(ProcessorResource.java:95)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowStructure(FlowResource.java:200)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowContent(FlowResource.java:187)
at org.apache.nifi.web.api.FlowResource.getFlow(FlowResource.java:373)
Any hints?
nginx reverse-proxy nifi
asked Nov 24 '18 at 11:07
xainxain
3891821
Check your error logs.
– Michael Hampton♦
Nov 24 '18 at 15:44
add a comment |
I want to use an https nginx to proxy a non-secured nifi server running in the same box.
So far the closest I get is by using this configuration:
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969/nifi;
In nifi I get the exception:
2018-11-24 17:40:19,473 ERROR [NiFi Web Server-20] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []. Returning Internal Server Error response.
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []
at org.apache.nifi.web.util.WebUtils.verifyContextPath(WebUtils.java:152)
at org.apache.nifi.web.util.WebUtils.getResourcePath(WebUtils.java:125)
at org.apache.nifi.web.api.ApplicationResource.buildResourceUri(ApplicationResource.java:159)
at org.apache.nifi.web.api.ApplicationResource.generateResourceUri(ApplicationResource.java:141)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntityContent(ProcessorResource.java:107)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntitiesContent(ProcessorResource.java:95)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowStructure(FlowResource.java:200)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowContent(FlowResource.java:187)
at org.apache.nifi.web.api.FlowResource.getFlow(FlowResource.java:373)
Any hints?
nginx reverse-proxy nifi
asked Nov 24 '18 at 11:07
xainxain
3891821
I want to use an https nginx to proxy a non-secured nifi server running in the same box.
So far the closest I get is by using this configuration:
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969/nifi;
In nifi I get the exception:
2018-11-24 17:40:19,473 ERROR [NiFi Web Server-20] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []. Returning Internal Server Error response.
javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted []
at org.apache.nifi.web.util.WebUtils.verifyContextPath(WebUtils.java:152)
at org.apache.nifi.web.util.WebUtils.getResourcePath(WebUtils.java:125)
at org.apache.nifi.web.api.ApplicationResource.buildResourceUri(ApplicationResource.java:159)
at org.apache.nifi.web.api.ApplicationResource.generateResourceUri(ApplicationResource.java:141)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntityContent(ProcessorResource.java:107)
at org.apache.nifi.web.api.ProcessorResource.populateRemainingProcessorEntitiesContent(ProcessorResource.java:95)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowStructure(FlowResource.java:200)
at org.apache.nifi.web.api.FlowResource.populateRemainingFlowContent(FlowResource.java:187)
at org.apache.nifi.web.api.FlowResource.getFlow(FlowResource.java:373)
Any hints?
nginx reverse-proxy nifi
nginx reverse-proxy nifi
asked Nov 24 '18 at 11:07
xainxain
3891821
asked Nov 24 '18 at 11:07
xainxain
3891821
edited Nov 24 '18 at 20:48
xain
asked Nov 24 '18 at 11:07
xainxain
3891821
asked Nov 24 '18 at 11:07
xainxain
3891821
asked Nov 24 '18 at 11:07
xainxain
3891821
3891821
Check your error logs.
– Michael Hampton♦
Nov 24 '18 at 15:44
add a comment |
Check your error logs.
– Michael Hampton♦
Nov 24 '18 at 15:44
Check your error logs.
– Michael Hampton♦
Nov 24 '18 at 15:44
Check your error logs.
– Michael Hampton♦
Nov 24 '18 at 15:44
add a comment |
3 Answers
3
active
oldest
votes
Just update your proxy_pass to remove the nifi suffix.
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
nginx will append the entire $uri to the proxy_pass url, so nginx was forwarding to http://localhost:6969/nifi/nifi/... instead of http://localhost:6969/nifi/...
answered Nov 25 '18 at 0:51
2ps2ps
79937
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
add a comment |
Additional to the answer above, try adding the X-ProxyScheme header.
Also, if you are advertising your site for external access, modify the X-ProxyHost to your LAN accessible IP address or Internet accessible domain name. (i.e. mynifiwebaccess.com,10.51.102.9)
location ^~ /nifi
proxy_set_header X-ProxyScheme https;
proxy_set_header X-ProxyHost mynifiwebaccess.com;
proxy_set_header X-ProxyPort <externally_advertised_port_number>;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
I am not sure about your configuration but you could try making the port number for the externally_advertised_port on the code above different since NiFi might be running and using port 6969 already.
answered Feb 5 at 12:58
tdltdl
1
add a comment |
the error message: javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted [].
this is caused by nifi.web.proxy.context.path is not set properly.
check the doc:
https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.3.0/nifi-configuration-best-practices/content/proxy_configuration.html
answered May 9 at 5:18
echoecho
101
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f941438%2fproxying-nifi-using-nginx%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Just update your proxy_pass to remove the nifi suffix.
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
nginx will append the entire $uri to the proxy_pass url, so nginx was forwarding to http://localhost:6969/nifi/nifi/... instead of http://localhost:6969/nifi/...
answered Nov 25 '18 at 0:51
2ps2ps
79937
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
add a comment |
Just update your proxy_pass to remove the nifi suffix.
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
nginx will append the entire $uri to the proxy_pass url, so nginx was forwarding to http://localhost:6969/nifi/nifi/... instead of http://localhost:6969/nifi/...
answered Nov 25 '18 at 0:51
2ps2ps
79937
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
add a comment |
Just update your proxy_pass to remove the nifi suffix.
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
nginx will append the entire $uri to the proxy_pass url, so nginx was forwarding to http://localhost:6969/nifi/nifi/... instead of http://localhost:6969/nifi/...
answered Nov 25 '18 at 0:51
2ps2ps
79937
Just update your proxy_pass to remove the nifi suffix.
location ^~ /nifi
proxy_set_header X-ProxyHost localhost;
proxy_set_header X-ProxyPort 6969;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
nginx will append the entire $uri to the proxy_pass url, so nginx was forwarding to http://localhost:6969/nifi/nifi/... instead of http://localhost:6969/nifi/...
answered Nov 25 '18 at 0:51
2ps2ps
79937
answered Nov 25 '18 at 0:51
2ps2ps
79937
answered Nov 25 '18 at 0:51
2ps2ps
79937
answered Nov 25 '18 at 0:51
2ps2ps
79937
79937
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
add a comment |
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
Still the same error after correcting the proxy pass entry
– xain
Nov 25 '18 at 4:19
add a comment |
Additional to the answer above, try adding the X-ProxyScheme header.
Also, if you are advertising your site for external access, modify the X-ProxyHost to your LAN accessible IP address or Internet accessible domain name. (i.e. mynifiwebaccess.com,10.51.102.9)
location ^~ /nifi
proxy_set_header X-ProxyScheme https;
proxy_set_header X-ProxyHost mynifiwebaccess.com;
proxy_set_header X-ProxyPort <externally_advertised_port_number>;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
I am not sure about your configuration but you could try making the port number for the externally_advertised_port on the code above different since NiFi might be running and using port 6969 already.
answered Feb 5 at 12:58
tdltdl
1
add a comment |
Additional to the answer above, try adding the X-ProxyScheme header.
Also, if you are advertising your site for external access, modify the X-ProxyHost to your LAN accessible IP address or Internet accessible domain name. (i.e. mynifiwebaccess.com,10.51.102.9)
location ^~ /nifi
proxy_set_header X-ProxyScheme https;
proxy_set_header X-ProxyHost mynifiwebaccess.com;
proxy_set_header X-ProxyPort <externally_advertised_port_number>;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
I am not sure about your configuration but you could try making the port number for the externally_advertised_port on the code above different since NiFi might be running and using port 6969 already.
answered Feb 5 at 12:58
tdltdl
1
add a comment |
Additional to the answer above, try adding the X-ProxyScheme header.
Also, if you are advertising your site for external access, modify the X-ProxyHost to your LAN accessible IP address or Internet accessible domain name. (i.e. mynifiwebaccess.com,10.51.102.9)
location ^~ /nifi
proxy_set_header X-ProxyScheme https;
proxy_set_header X-ProxyHost mynifiwebaccess.com;
proxy_set_header X-ProxyPort <externally_advertised_port_number>;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
I am not sure about your configuration but you could try making the port number for the externally_advertised_port on the code above different since NiFi might be running and using port 6969 already.
answered Feb 5 at 12:58
tdltdl
1
Additional to the answer above, try adding the X-ProxyScheme header.
Also, if you are advertising your site for external access, modify the X-ProxyHost to your LAN accessible IP address or Internet accessible domain name. (i.e. mynifiwebaccess.com,10.51.102.9)
location ^~ /nifi
proxy_set_header X-ProxyScheme https;
proxy_set_header X-ProxyHost mynifiwebaccess.com;
proxy_set_header X-ProxyPort <externally_advertised_port_number>;
proxy_set_header X-ProxyContextPath /nifi;
proxy_pass http://localhost:6969;
I am not sure about your configuration but you could try making the port number for the externally_advertised_port on the code above different since NiFi might be running and using port 6969 already.
answered Feb 5 at 12:58
tdltdl
1
answered Feb 5 at 12:58
tdltdl
1
answered Feb 5 at 12:58
tdltdl
1
answered Feb 5 at 12:58
tdltdl
1
1
add a comment |
add a comment |
the error message: javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted [].
this is caused by nifi.web.proxy.context.path is not set properly.
check the doc:
https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.3.0/nifi-configuration-best-practices/content/proxy_configuration.html
answered May 9 at 5:18
echoecho
101
add a comment |
the error message: javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted [].
this is caused by nifi.web.proxy.context.path is not set properly.
check the doc:
https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.3.0/nifi-configuration-best-practices/content/proxy_configuration.html
answered May 9 at 5:18
echoecho
101
add a comment |
the error message: javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted [].
this is caused by nifi.web.proxy.context.path is not set properly.
check the doc:
https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.3.0/nifi-configuration-best-practices/content/proxy_configuration.html
answered May 9 at 5:18
echoecho
101
the error message: javax.ws.rs.core.UriBuilderException: The provided context path [/nifi] was not whitelisted [].
this is caused by nifi.web.proxy.context.path is not set properly.
check the doc:
https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.3.0/nifi-configuration-best-practices/content/proxy_configuration.html
answered May 9 at 5:18
echoecho
101
answered May 9 at 5:18
echoecho
101
answered May 9 at 5:18
echoecho
101
answered May 9 at 5:18
echoecho
101
101
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f941438%2fproxying-nifi-using-nginx%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Check your error logs.
– Michael Hampton♦
Nov 24 '18 at 15:44