Thanks for your answer. I am indeed getting no warning on my browser, just “Unable to connect” on LibreWolf and “This site can’t be reached” on Chromium. I tried the same format (https://192.168.50.30:80) with ports 80, 8080 and 443. The only difference is it was always https:// (since I think my browsers are configured to force https everywhere).
The out put of docker container ls
looks like this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
95a71b3ce4f6 nextcloud:apache "/entrypoint.sh apac…" 24 hours ago Restarting (1) 30 seconds ago nextcloud-app-1
590b07333fa1 nextcloud:apache "/cron.sh" 24 hours ago Restarting (1) Less than a second ago nextcloud-cron-1
337fd48a72e8 nextcloud-proxy "/app/docker-entrypo…" 24 hours ago Restarting (1) 17 seconds ago nextcloud-proxy-1
401d57a50ec8 mariadb:10.6 "docker-entrypoint.s…" 24 hours ago Restarting (1) 57 seconds ago nextcloud-db-1
c6093edc9f71 redis:alpine "docker-entrypoint.s…" 24 hours ago Restarting (1) 9 seconds ago nextcloud-redis-1
I notice that the “PORTS” column is empty. I am running Raspbian GNU/Linux 11 (bullseye) on my Raspberry Pi, yes.
Thank you for this new tip, I think we found the problem: ports 80 and 443 are not open. After I installed nmap (which was surprisingly not present in my Raspbian installation), the output of
nmap localhost
reads:I guess I did something wrong when following the tutorial (or the tutorial had some mistake, but I’d me more inclined to think the mistake was mine). I will try to clear this installation on docker and start all over again, then I will check
nmap localhost
again to see if it works fine then.Thank you very much for your support. I still feel quite lost, but I finally found out why this is not working and I can repeat the steps and pay special attention… or look for a different method (someone here suggested using Nextcloud All-In-One).