hi team,
has anyone accessing the dataminer, instead of dataminer server public ip, accessing it from load balancer?
we are running dataminer in a server, it was running perfectly fine, we are accessing from server public ip, Now we want access it from loadbalancer(AWS), but issue is in target port which port we have to give for accessing the dataminer root page?.
thanks,
s.j.v.praveen
Load balancing may not work out as expected, because authentication is done against a specific SLNet service, so any time a request is forwarded to a different backend, it will be considered unauthenticated and fail.
If there is no real “load balancing” to multiple backends, it is more acting as a reverse proxy to one specific backend. In that case it should be enough to proxy HTTPS on port 443 for webapps and Cube gRPC connections, and additionally port 8004 for Cube legacy Remoting connections. Forwarding to HTTP on port 80 will not work to establish a gRPC connection.
Hi,
To be able to access the DataMiner web pages, you’ll need TCP port 443 (HTTPS) or 80 (HTTP).
If you need to connect through the DataMiner cube interface, you might also need to open port 8004 (.net remoting), if you are still running an older DataMiner version that doesn’t support gRPC yet.
For the sake of completeness, an overview of all used ports in a dataminer system can be found here (including those used in the back-end, which are not applicable here).
hi ive,
dataminer version is 10.3 we are running.
loadbalancer listener given http port 80, in target group target port toward server given 80 and 8004 but not able to access health check was failing, dataminer is running fine able to access from public ip, problem to access from loadbalancer.
For the web apps, the load balancer should be configured to send the requests to the same backend server within the same session (session affinity, or “sticky sessions” in AWS).