Closed dconway closed 1 month ago
I figured it out. I added the tag that Google Search Console told me to as instructed in this file.
/usr/share/unifi-core/app/node_modules/@ubnt/unifi-portal/dist/local/index.html
I ran the verify in the Google search console and I worked. Hopefully it survives reboot and OS upgrade but at least now I know.
I'm pretty confused here, you're exposing your router's login page to the internet and also indexing it in Google Search tools? I would highly recommend you not do that.
Thank you that's really good feedback. Ultimate goal is to have a DDNS VPN target for devices to connect back to my router without me having a static IP (I also have dual WAN) . After connecting from a browser I also wanted to get rid of the big red browser warning which (I think) meant using search console. Worrying about the warning might be unnecessary if the VPN traffic will come through the wireguard port.
Anyway, now I've also added the tag: \ to the file \/usr/share/unifi-core/app/node_modules/@ubnt/unifi-portal/dist/local/index.html
so it shouldn't show up in search results.
Title. But basically the domain (using duckdns.org) now points brilliantly to the login page for my UDM router and the certificate is valid. Well done! Problem is Google Search Console now wants me to verify that the domain is mine to remove the big red warning screen. Is there an obvious place in the UDM's file system where I should upload the HTML file Google Search Console gives me to prove to google's web crawler (and chrome) that the site is not dangerous? Thank you for a great script.