eds

Problem solved. Had to manually pass a nic to the vm by editing the xml of the CentOS vm. It all sounds very confusing, fortunately someone created a video. Once I passed through the nic, the install was simple.

What a life saver. This video is must watch if trying to figure out why CentOS will not install with networking configured. I came from the Qnap world and all of this done for you. With this amazing video was finally able to install CentOS!

Any idea where I should start looking? I have an asus RT-AC68W router running Merlin. What configurations should I have (note the same domain name is being used as dnns in the router)?

Yes.

Another machine.

If you mean run the command nslookup then it comes up with default server and address. If I run nslookup <mydomainname.com> then I get dns request timed out. Can't find address for server....

Yes

I did, but putting nextcloud aside for a moment, from NPM, I am still unable to resolve my domain name or any of the subdomains. Shouldn't I be able to wget: https://mydomainname.com or wget https://mydomain.domainname.com from the npm console? When I try I get: bad address 'mydomainname.com'

Not getting the error although the original issue stands. Can't connect to the domain name from the docker.

I'm not seeing the error right now so it appears to be exclusive to whatever issue I am having with the subdomain assigned to nextcloud.

This is what I have: resolver 1.1.1.1 1.0.0.1 192.168.0.1 ;

I am running into a brand new problem starting today. I am running nextcloud with ngnix proxy manager. I updated to nextcloud 16 and things were going fine for a day. Today I try to open the docker and I get the following error in chrome: This site can’t provide a secure connection Mydomain.domain.com uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH In Firefox it looks like: Secure Connection Failed The connection to mydomain.domain.com was interrupted while the page was loading. The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Is anyone else experienced this issue?

Ok, well I do see the ip of the dns server in the resolv.conf file. What is curious is I am seeing errors that look like this in the npm log: nginx: [emerg] host not found in resolver "<mydomainname.com>" in /etc/nginx/conf.d/include/resolvers.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed How to fix?

OK, so I added the domain name to the resolv.conf manually. Unraid can resolve the url, but nextcloud still cannot. Clearly the issue is with the nextcloud docker. Will try to use a static ip and see if that works. Thanks.

Brilliant. That did it. It was hit or miss for a while but finally I got it up and running and my camera is visible. Many thanks.

Interesting. Are you saying I should I see the domain name here?

Not sure what you mean by the docker not having the 443 conflict. I tried this. Zoneminder looks for port 443 (even when the config clearly maps to 8443) when on everything except bridge mode. Is that not to be expected?

Unfortunately it doesn't. Seems even with the port set to 8443, Zoneminder wants to run on 443 in host mode, but that port is being take up by nextcloud.

Curious to know how folks are finding their cameras. I'm using a Deecam D200 which has onvif and rstp support and the onvif network scan function is not finding my camera (although my browser and smartphone can).

Yes, which is what I find so weird. It won't even resolve nextcloud.mydomainname.com. I get the error: wget bad address https://nextcloud.mydomainname.com. Not sure what that even means. Also, I should state, if I take the docker out of bridge mode (and give the docker its own ip), I can resolve the domain names, even nextcloud.mydomainname.com.

With respect to the nextcloud container - From Unraid to nextcloud: yes. From the nextcloud container to any subdomain on the proxy manager: no.

Thanks for the feedback Djoss. Can you help with an issue I have, because I cannot figure out where the problem is? I have nextcloud and onlyoffice running and configured using Ngnix Proxy Manager using my own domain name. They appear to be running fine remotely. But nextcloud cannot access the onlyoffice docker using cURL. I get cURL6 could not resolve the host. I am not sure why. How should this be configured? Are there setting that need to be added to the advanced page on Nginx Proxy Manager?

Is it true that for this to work your dockers must be in bridge mode and that, like for nextcloud, you cannot use your own ip?

Ok, appears I've come full circle on this issue. It looks like with nextcloud container you cannot ping (in my case wget) any other bridged dockers on unraid when in bridge mode. So trying to ping any of the dockers served via NginxProxy Manager using the console throws the bad address error. Sucks.

Wondering if anyone can help me. Trying to get onlyoffice to run with nextcloud, but I'm getting a cURL error 6 with the subdomain I am using (via NginxProxy Manager docker and my own subdomain) for onlyoffice. Decided to log into the docker and wget the subdomain for onlyoffice. This throws an error 'bad address domain.mydomain.com'. I have no problem with connecting to other websites. Is there anyway to fix this?