Hi everybody!
New to the OMV world, and I've been following TechnoDadLife's video series on getting OMV and Nextcloud running on a Raspberry pi 4.
I had previously used a NextcloudPi setup, which worked straight away, but now I am getting some trouble with connecting remotely to my Nextcloud instance.
I am able to get OMV 4 running on my Raspberry Pi 4, and it is set up just like in the TechnoDadLife video for now. I am also able to get MariaDB and Nextcloud working in Docker, with the lsioarmhf docker images. And using ip:444 I can log in and access my nextcloud in my local network just like I was able to previously.
I run into trouble when I start configuring letsencrypt and duckDNS. Once I input "docker logs -f letsencrypt" in terminal, while "letsencrypt" is my running container's name, it first runs for a very long time (as the message in the prompt warns), but then it ends up spitting out an error message reading:
"ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container"
Following is the latest, complete error message with personal information redacted:
Here are my duckdns and letsencrypt container configurations, as well as the port forwarding menu in my router.
The only things I did differently versus the TDL videos are that I am running on OSX El Capitan, so I ssh in via terminal instead of shellinabox, that I use lsioarmhf images, and that instead of adding my-net into the "Extra arguments" section of the container config window, I connected the duckdns and letsencrypt containers to my-net in the configurations tab in docker window.
I tried both the "Securely Login to Nextcloud Remotely on Openmediavault", and the "Free SSL Certificates with Letsencrypt on Openmediavault : Updated" videos instructions, which seemed to differ only as much as how the SUBDOMAINS environment variable is managed in the letsencrypt container. I now followed the more recent video, and simply used "cloud" as a subdomain for my "xxx.duckdns.org" domain that I have configured, as I figured it was pretty arbitrary, but I may be wrong.
I used this tool and nmap in terminal to check my ports and set it to "Use Current IP", and found that port 80 is open, and port 443 is not. I am very new to any of this business with port forwarding or router configuration, so I am not sure if this is useful information or not. But I have gone through a multitude of threads here with similar issues and a common thread seems to be issues in port forwarding / port opening with the different routers people have at home, so I wonder if that's where my issue lies? If so, please advise on how to troubleshoot the issues.
I have completely re-etched my OMV iso into the microsd on my Pi multiple times, and am now running a version in which the configuration steps are as 1:1 with the TDL videos as possible, with small variations pertaining to my Raspberry Pi and other (I think) simple differences.
Sorry if it's a bit of a wall of text, but I wanted to try and provide as much info to be able to troubleshoot this issue concisely, and thanks in advance for the help, crawling through these forums has shown a really amazing community and amount of support to users starting out with their own NAS systems!
