It’s basically a dedicated post to deal with the last comments on: [image] URL doesn`t open during Cells installation process Pydio Cells I’m experiencing the very same behavior on the same (and most normal configuration). First, the URL not reachable: If internalUrl (= …

About internal URL I also found this thread which is about the very same issue & question: [image] Cells require 2 networks, documentation? Pydio Cells @ginawu45 @c12simple I agree, it is strange. If it’s for security reasons why not 127.0.0.1? Why force aliases? Let me…

If pydio cells is running in a docker container and is reverse proxied via another docker container, binding the server to localhost or 127.0.0.1 will prevent the reverse proxy container from accessing it. Binding to 0.0.0.0 will on the other hand allow that connection. External url is the reverse…

Thank you @aptalca . This loopback vs non-routable IP now makes perfect sense in the context of containers. Still, Pydio cells is provided with a built-in webserver. If using it, is there any drawbacks in binding on the public/routable IP address (as the warning suggests), as long as I’m behind a CF …

I guess. I can’t think of any potential issues with that.

`./cells install --bind` on VPS, LetsEncrypt and reverse-proxy

Pydio Cells

drzraf February 24, 2020, 5:11pm 2

About internal URL I also found this thread which is about the very same issue & question:

Topic		Replies	Views
Warning: no private IP detected for binding broker. Will bind to XXX, which may give public access to the broker Pydio Cells	3	1438	February 24, 2021
URL doesn`t open during Cells installation process Pydio Cells install	11	1421	February 19, 2020
Pydio cells docker-compose example does not work Pydio Cells	24	4672	May 16, 2023
Running Cells in addition to Apache on Debian Buster Pydio Cells install	11	1100	August 24, 2021
Cells running behind an HTTP proxy Pydio Cells install , s3 , docker	3	1430	October 14, 2020

`./cells install --bind` on VPS, LetsEncrypt and reverse-proxy

Related topics