• 18 Posts
  • 130 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle
  • Because every time I’m reminded the underlying OS exists it’s always something negative.

    On windows: Forced restarts and updates that take over 5x as long as my Linux (or FreeBSD build), ui that constantly undoes what I customized, ads and preinstalled malware essentially like candy crush even on builds from Microsoft directly, worse performance with a much higher number of crashes under load on my current box, and no auto login/name any simple customization without screwing around with registry editor to name just the simple things. More advanced problems include no hypervisor built in to the home version, everything is pay to unlock features my Linux install does for free, no zfs software raid for storage safekeeping, most fixes when I do have errors involve googleing cryptic hex codes and being told to run fsck/chdsk as the only solution for often times hours of searching before finally finding the actual answer - not to mention most other fixes being to download a library/binary of the sketchiest sounding website ever that i can’t verify isn’t a virus.

    On linux or even FreeBSD which took a bit to get installed to my liking i may have put work in up front but its like 3 hours at most of my time for 6+ years of stability and proper functioning to avoid all of the above plus no microsoft telemetry etc. I switched when i first tried Vista and even today every time i have to use Microsoft’s horrific excuse for an OS it is heartburn inducing.
















  • 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.


  • You would be given a safety risk warning page by your browser if you did the self 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: http://192.168.50.30:80 Certificate: https://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?


  • 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.