Does nifi use the http server on Linux or does it use it's own? I inherited a nifi server that has some nessus issues related to http. Http service is not running, only nifi. Tring to figure out how to resolve the issues.
NiFi executes within a JVM on a host operating system. The primary
components of NiFi on the JVM are as follows:
Web Server
The purpose of the web server is to host NiFi’s HTTP-based command and control API.
...
More info : https://nifi.apache.org/docs/nifi-docs/html/overview.html
Related
I have a Python gRPC server running on AWS Fargate (configured very similar to this AWS guide here), and another AWS Fargate task (call it the "client") that attempts to make a connection to my gRPC server (also using Python gRPC). However, the client is unable to make a call to my server, with the following error:
<_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"#1619057124.216955000","description":"Failed to pick subchannel",
"file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":5397,
"referenced_errors":[{"created":"#1619057124.216950000","description":"failed to connect to all addresses",
"file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc",
"file_line":398,"grpc_status":14}]}"
Based on my reading online, it seems like there are myriad situations in which this error is thrown, and I'm having trouble figuring out which one pertains to my case. Here is some additional information:
When running client and server locally, I am able to successfully connect by having the client connect to localhost:[PORT]
I have configured an application load balancer target group following the guide from AWS here that makes health check requests to the / route of my gRPC server, using the gRPC protocol, and expect gRPC response code 12 (UNIMPLEMENTED); these health check requests are coming back as expected, which I believe implies the load balancer is able to successfully communicate with the server (although I could be misunderstanding)
I configured a service discovery system (following this guide here) that should allow me to reach my gRPC server within my VPC via the name service-name.dev.co.local. I can confirm that the corresponding DNS record exists in Route 53, and when I SSH into my VPC, I am indeed able to ping service-name.dev.co.local successfully.
Anyone have any ideas? Would appreciate any and all advice, and I'm happy to answer any further questions.
Thank you for your help!
on your grpc server use 0.0.0.0:[port] and expose this port with TCP on your container.
We're using neo4j server 3.1.4
We want to deploy neo4j server behind nginx, and our environment just allow one port:80 for nginx.
But neo4j browser need HTTP port(default 7474), and bolt port(default 7687).
So we config nginx to access HTTP port, we failed to connect bolt port.
It reported WebSocket connection error, for we can't access another port.
We checked the neo4j.conf & documentation,and found no useful information.
So, Is there any way to access neo4j server with only one port(80)?
Can anyone help us with this situation?
screen errors
Neo4j browser is just a client for the database, and in a prod env, I never give access to it by the outside.
So in your case, I will just map the bolt port to the 80 one on nginx.
And if you want access to Neo4j with a browser, you should consider to use the Neo4j Desktop application, and configure a remote database.
I got 2 servers with two equal wcf services hosted on them and one client application server. I can connect to endpoints and send a requests to both services using test wcf client app (.NET Web Service Studio) from my local machine successfully. But when I am trying to connect from client application server using the same test wcf client app I successfully connected only to the one wcf service server, but I have got an error when connecting to another one:
System.Net.WebException: There was an error downloading 'https://XXX/XXX?wsdl'. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it XX.XXX.XX.XXX:443
I performed netstat -an | find "443" command in command prompt on the client server and on my local machine to find out the difference and here what I have got:
1. On my local machine:
2. On the client app server:
What I already tried to do on client application server is:
- turned off firewall;
- stopped windows firewall service
- uninstalled mcafee virusscan enterprise application.
(I tried to set "prevent mass mailing worms from send mail" first, but mcafee was in foreign language that I don't understand, so I just uninstalled it)
after running command netstat -aon | findstr "443" on client application server I have got this result:
but I still got an error.
Does anybody know how to solve this issue?
Could be the problem on the wcf service server side?
The solution was predictable simple one - firewall was blocking the port,
but it's important to notice that the issue was caused by firewall on the wcf service server side, but not on client application server, which is making the request to that service.
I asked the technical support of that server, and they made firewall changes.
After that error was disappeared.
I faced the same issue and tried different ways to fix this. Nothing works. Later i found the issue which is, the application i tried to run is https and in my IIS, https binding was not created. I created binding https with the website and it works.
My WebSphere ESB server runs behind corporate proxy server in our network.
When I try to access external web-service i get network exceptions (cannot access destination host).
Is there any way to set my proxy configuration in console, except server startup params?
-Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800
No.
Since WAS leverage JVM TCP/IP capabilities, the only way is what you found: configure the JVM through the VM Args.
Edit: Those particular options can be set as Additional Properties to the JVM
See http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/twbs_configwbsclient2webproxy.html
In WAS, options to the JVM are set in Application servers > server_name > Process definition > Java Virtual Machine.
See http://www-01.ibm.com/support/docview.wss?uid=swg21417365
I am using Apache HTTP server as a web server in front of WebLogic Application Server. I've integrated these two using mod_wl_22.so plug-in with some configuration in httpd.conf file - now I can access an application deployed on WebLogic Application Server using Apache HTTP Server URL, in other words, the actual URL (WebLogic Application Server URL) to access application localhost:7001/testproj/index.html can be accessed with localhost/testproj/index.html URL (Apache HTTP Server URL) also.
The requirement now is to configure a custom filter (or something), preferably in Java, in Apache HTTP Server so I can modify "form post data" before sending it to WebLogic Application Server. I didn't find any example/help regarding this as of now while googling.
Please let me know if anyone has done this before.
Thanks.
After googling I now have a feeling that Java is not supported in Apache HTTP Server hence I can't write filter (or servlet) in Java. Is this true?
I also found that mod_perl can help me with this problem.