Can't reach the Control Center from other than localhost:9021

21 views
Skip to first unread message

Elier Delgado

unread,
May 17, 2017, 4:15:34 PM5/17/17
to Confluent Platform
Hello, 

I have installed the Confluent Platform on Centos 7 server + Java 8 following this guide: 

The Control Center seems to be working from the server only. Check below the result of curl -v http://localhost:9021
- Can someone tell if all is okay just by looking and the index page?
- However, I cannot access using the server IP:9021. The firewall is down, everything is open. Can someone suggest any other reason why would not respond? Does the Control Center required any particular configuration or maybe license to be reachable from other than localhost?

Thank you!

* About to connect() to localhost port 9021 (#0)
*   Trying ::1...
* Connected to localhost (::1) port 9021 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: localhost:9021
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 17 May 2017 20:04:41 GMT
< X-Confluent-Control-Center-Version: 3.2.1
< Accept-Ranges: bytes
< Content-Type: text/html
< Last-Modified: Mon, 01 May 2017 23:05:06 GMT
< Vary: Accept-Encoding, User-Agent
< Content-Length: 597
< Server: Jetty(9.2.12.v20150709)
<
<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-type" content="text/html; charset=utf-8">
    <title>Control Center</title>
  <link rel="shortcut icon" href="/dist/favicon.ico"><link href="/dist/main-e67423ada760f585c4ce.css" rel="stylesheet"></head>
  <body>
    <div id="controlcenter" style="height: 100%"></div>
  <script type="text/javascript" src="/dist/manifest-33a27233e1e84c2f509f.js"></script><script type="text/javascript" src="/dist/vendor-313971a42f060c8be81e.js"></script><script type="text/javascript" src="/dist/main-87d2e4bb76abbf16f6ff.js"></script></body>
</html>
* Connection #0 to host localhost left intact



Elier Delgado

unread,
May 17, 2017, 4:24:22 PM5/17/17
to Confluent Platform
I would like to add, that it does not look like external access issues because I did setup apache and on the port 80 all was good. I was able to reach the server using the IP:80.

Ewen Cheslack-Postava

unread,
May 18, 2017, 6:25:08 PM5/18/17
to Confluent Platform
Did you modify the confluent.controlcenter.rest.listeners setting at all? By default it should be using 0.0.0.0 which will bind to all interfaces, so I would expect it to be externally accessible by default.

If there's nothing in the log indicating it is not listening on all ports, I'd use netstat to verify what the service is listening on. See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Security_Guide/s1-server-ports.html for an explanation of how to do this.

-Ewen

On Wed, May 17, 2017 at 1:24 PM, Elier Delgado <elier....@gmail.com> wrote:
I would like to add, that it does not look like external access issues because I did setup apache and on the port 80 all was good. I was able to reach the server using the IP:80.

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/6cb4d060-10d1-492b-a829-1ea3e986afc6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages