Ok, I have been looking around the Forum and there seems to be an ongoing issue which has plagued a number of people but there doesn’t actually seem to be an answer.
In fact in trying to find an answer to my question it was pointed out that the documentation is severely lacking and I would have to agree. It also seems to differ between the Centos and the Ubuntu documentation
Do we have an answer to no private ip detected for binding?
Is this a warning message.
What format would it be looking for a private IP?
What does it mean when it says private IP? I think most people on here take it to mean the loopback address. If it doesn’t mean that then can someone please define what it does men
I have managed to get the server to operate on what I would take to be my external address
There seems to be no ability for this to operate on anything other than 8080
I have tried Multiple combinations of the external url. The most logical one is to pick the option of
Then pick map port 80 to 443 in the next section of the installer
Then when you try and connect to the URL, it gives me the error of
http://my-long-domain.name.org <- no response from server
https://my-long-domain.name.org:8080 -< the application is not served from 8080
The private address is internally used for the nats service that handles registry and communication for the various microservices: not having an internal private network for communication between microservices will lead to security issues.
About your network configuration you have to understand what happens:
The internal address defines 2 things:
<IP or FQDN>:<PORT>
- the application will only consider requests for this IP or FQDN
- the port where the application listen
For instance, if cells’ internal address is:
example.com is registered to point toward IP
- browsing to
- browsing to
220.127.116.11:8888 returns this application is not served on this interface
the external address is the public address. Typically, the one you send by email to your end-users
- if you are directly internet facing, it should be the same as the internal address prefixed with
https depending on your TLS settings
- if you are behind a reverse proxy, it is the one that is registered in your proxy.
Redirection from 80 to “declared TLS port” (usually 443) is there as a convenience for people that are directly internet facing: with this option set, someone that browse
http://example.com is automatically redirected to
If the above is not clear enough, feel free to precise your questions.
Otherwise, TL;DR a vanilla setup could be:
and you have to execute the setcap command on your binary.
If your port 443 is already used, you then have to configure a reverse proxy. We have many examples in our knowledge base.