Comment on Beginner needs help with setting NextCloud without a domain
socphoenix@midwest.social 3 months ago
At a glance your first issue is finding the correct ip address, you should only have one local ip address to access it with (inside your home network).
To find your local ip, type “ip a” into the terminal, and look for the address under “eth0“ for a wired connection, or “wlan0” for wireless. This will allow you to connect using the ip and port while on your home network to test the connection and make sure it works right.
After that, I highly recommend the vpn option, it will simplify connecting to it while not at home without creating security issues like setting it up with a domain. I personally use zerotier, that guide will help you get it set up on the raspberry pi. Not the last bit about a “managed ip.” That will be the address to tell your phone to connect too once you have the vpn set up on the phone as well.
nshibj@lemmy.world 3 months ago
Thank you, the
ip acommand 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
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
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?
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 lslooks like this:I notice that the “PORTS” column is empty. I am running Raspbian GNU/Linux 11 (bullseye) on my Raspberry Pi, yes.
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.
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.