Recent content by Blokie

Thanks for the suggestion. I put a post on there yesterday afternoon and so far zero responses!

I've tried this and I can't save it as it gives me the same DNS error. I really hate Squarespace! (and Google for selling out!)

That's pinging correctly to the GCP - I assume that means that my Custom Records should just be called "teslamate" and "grafana" as opposed to the full domain name? Scratch that - just tried to modify the custom record to just teslamate and it gives me an error: Invalid DNS Records Invalid DNS...

Out of interest I've just tested my root domain which was correctly pinging against my GCP IP, but now that's reverted to a Squarespace 198 IP as well. FFS!!! This is what I have setup (from yesterday afternoon)......

Thanks all. teslamate.mydomain.com and grafana.mydomain.com are both still pinging to the Squarespace IP. When I've made the other A record changes it's taken the full 72 hours for them to switch over, so will have to wait and see.....

Thanks - I'd assumed (wrongly it seems!) that I could only have 1 A record and the others needed to be CNAME's, and it wouldn't let me put a CNAME the "correct" way around, hence trying it backwards! I've now removed that reverse one and added teslamate.mydomain.com and grafana.mydomain.com as...

Thanks for the reply. I've removed those 2 entries from the Nameserver Registration and tried to add to the Custom Records, but it will only let me add one...

Thanks for the response. Everything was working fine for over 3 years until my domain was (forcibly!) migrated from Google Domains to Squarespace. The DNS Check is showing 2 x A records - the 198 address is a cloudspace one and the 35 address is the "correct" address for my GCP server. Both...

Looking at the advanced installation instructions and my install, I'm prety sure I configured it with let's encrypt when I originally set it up. It definitely something weird with routing, as I've just setup a local instance of TM on one of my internal devices and restored a backup on my...

Turns out with Squarespace you have the use @ or it won't work. Finally got that sorted on Saturday and this afternoon the DNS is now correctly pointing to my GCP instance. The issue is that I'm just getting a "404 page not found" when accessing my domain. All of the services on the GCP seem...

Another quick q - for my A record, should I have the host of that as mydomain.com or should it just be @ ?

It's coming back with a 198.49.23.x IP which is a squarespace one. I think I may have to just wait a couple of days for the DNS propagations to go through everywhere and see what state it's in then? So much for Googles "seamless" transition! I believe I'm also going to need to setup an SSL...

Yes - that matches. The only thing that has changed is my domain having been migrated from Google Domains to Squarespace (as google domains are closing). Nothing has changed on the server itself, it has been running fine (connected to the same domain) for over 3 years until this forced migration.

Additonally, I've now changed the DNS settings in squarespace to wipe out the default CNAME entry and add one with host "www", type = CNAME and data="testamate.mydomain.com", and added Host="mydomain.com", type=A and Data=ipaddress (no quotes in the actual entries). This is at least now taking...

When I try to access it via https://ip I get a cert issue, and if I click proceed I then just get a page displaying "404 page not found".