ok here it is
i dont understand the port rule of container.
-
- gelöst
- OMV 5.x
- leeeunchang
-
-
Now you have the problem, that you cannot start filebrowser. Correct?
Please post the docker-compose you are using for filebrowser
-
Filebrowser uses internally port 80. So you need a port mapping like this
Then you can reach filebrowser on port 8080
and owncloud on port 80
Edit: for image https://hub.docker.com/r/filebrowser/filebrowser
-
i deleted filebrowser container and did this
docker run -d \
--name filebrowser \
--user $(id -u):$(id -g) \
-p 8080:80 \
-v /srv:/data \
-v /filebrowser_config:/config \
-e FB_BASEURL=/filebrowser \
hurlenko/filebrowser
but i can't open with http://myip:8080.
ㅜㅜ i don't know what i am missing.
-
filebrowser logs.
2021/05/01 10:56:38 No config file used,
2021/05/01 10:56:38 Listening on [::]:8080
-
You are using a different image. Try
-
it works !!
my docker port settings
host container
owncloud 80 8080
filebrowser 8080 8080
and router port forwarding settings are
external port internal port
tcp 8080 80
tcp 80 8080
when i connect to http://serverdomain: 80 filebrowser opens
and http://serverdomain:8080 owncloud opens.
i don't get it how it works because they are both using same 8080 container port.
-
and router port forwarding settings are
external port internal port
tcp 8080 80
tcp 80 8080
exposing http to the internet is not a good idea
https://www.geeksforgeeks.org/why-http-is-not-secure/
https://www.google.com/search?q=why+http+is+not+secure
i don't get it how it works because they are both using same 8080 container port.
Did you have a look at the picture?
-
then how can i use https instead of http ?
-
Use letsencrypt / swag like in this guide/example
[How-To] Nextcloud with Letsencrypt using OMV and docker-compose
-
leeeunchang
Hat das Label gelöst hinzugefügt.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!