Comment

Comment on Beginner needs help with setting NextCloud without a domain

Thank you, the ip a command helped me get the IP clear, however I am still not sure about the port. I tried with :80, :8080 and :443 (because 80 and 443 are the ones mentioned in the compose.yaml file, and I saw online that 8080 is also a common one?) but none of them worked :(.

I think I will try zerotier, but first I need to be able to access NextCloud from my home network via the IP, which I’m currently unable to do. The tutorial I followed says

The other option is to use a self-signed certificate. This certificate is signed by your own server and won’t be verifiable by any web browser unless you manually install the certificate. However, it doesn’t explain where that certificate will be stored nor how I can manually install it in the browser I want to use to access NextCloud. Could that help with my issue?

source

Sort:hotnew top

rambos@lemm.ee ⁨3⁩ ⁨months⁩ ago
You have to use https, so something like 192.168.100.40:443 or without port like 192.168.100.40

I use LSIO docker containers Nextcloud and MariaDB, but I’ve seen most recommendations for Nextcloud AIO

source
socphoenix@midwest.social ⁨3⁩ ⁨months⁩ ago
You would be given a safety risk warning page by your browser if you did the sec signed certificate that you’d need to tell it to connect anyway, so that likely isn’t the issue. Looking at ports, how are you trying to connect to the server? If you did not assign a certificate at all, you would want to use port 80, port 443 if you did install a certificate.

For instance, my Nextcloud is on ip 192.168.50.30 With that in mind I would be using:

No certificate: 192.168.50.30:80 Certificate: 192.168.50.30:443

Does this look like what you are typing in?

As two additional questions, what is the output of “docker container ls” typed into the terminal? And what operating system did you install on the pi, was it raspbian?

source
- nshibj@lemmy.world ⁨3⁩ ⁨months⁩ ago
  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 (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.
  
  source
  - socphoenix@midwest.social ⁨3⁩ ⁨months⁩ ago
    If you are on the raspberry pi with a physical screen/keyboard and mouse you can also try accessing with the ip address “localhost:80” and see if there’s a connection that way as well.
    
    source
  - socphoenix@midwest.social ⁨3⁩ ⁨months⁩ ago
    We can get the port list another way. From the terminal on the raspberry pi run the command “nmap localhost”. Let us know what that shows, but I would expect to see either 80, 443, or both.
    
    As a side note, if you did not give the nextcloud container a certificate when you made it, you cannot use https:// on the browser, as it has no way to talk using that security mechanism. It is only capable in that case of using http:// and port 80. You will need to disable forced https to access the site (this is fine on the local network if every device is trusted, and only encrypted vpn service in like zerotier is used imo). This might be your problem here, especially if you are seeing both ports listed as open on the pi.
    
    source
    nshibj@lemmy.world ⁨3⁩ ⁨months⁩ ago
    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:
    
    Not shown: 997 closed ports PORT STATE SERVICE 22/tcp open ssh 53/tcp open domain 631/tcp open ipp
    
    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).
    
    source
    -> View More Comments