So I have run into a bit of a weird problem with my next cloud instance. I have a NextCloud instance hosted at let’s say “nextcloud.mydomain.com” and it’s pointing to my public IP. I can pop this into a browser and my mobile app and it works fine with no issues coming up with the proper cert and is secure. I wanted to add a local A record so it points to the local address while at home rather than leaving and coming back figured it would be better for performance. I use PIhole as my DNS server. I went into Local DNS> DNS records in the PIhole web GUI and added an A record where the domain is let’s say nextcloud.mydomain.com again and the IP is let’s say 192.168.3.10. Now that the record is in place I went to test it out. I pulled open a browser on a device on my LAN VLAN at IP let’s say 192.168.1.10 and navigated to the website and works great and is secure. When I pull it open on a device on my WIFI VLAN at IP lets say 192.168.2.10 it gives me a connection is not private error giving me the error code “err cert auth invalid”. This usually happens when using a self-signed cert or whatever but my domain does have a working SSL cert attached to it as it clearly worked in other scenarios. Thoughts? Any ideas why this maybe?
You must log in or register to comment.
Check that the certificate store of your device is up-to-date. Ensure it is also set to the correct date. If all is ok, check that your device resolves your domain to the right IP. If it’s correct, check that the certificate fingerprint you get from your device is the same as what you get from your working devices.
If all looks good, maybe you can provide the exact error by attaching the output of
curl -voropenssl verify.
