1: No access to site. privacy issues
Posted by web.admin@winslowbowlsclub.org on 25/11/24 13:18

I'm in need of help, seems urgent.

Message received when opening our web page 'No access to site. privacy issues', I try again it's ok, then no access again.
Not just me but several other users too, on PC and android, and with different search engines.
It's intermittent, sometimes closing/restarting browser can help.
I've seenthat https is in red.
When working, website responds normally. I've not changed any settings.
 
Message reads 'winslowbowlsclub.org'  normally uses encryption to protect your information. When Chrome tried to connect to site this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be winslowbowlsclub.org, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit winslowbowlsclub.org right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later.'
 
Can you give some guidance please
John Thorogood
2: Web Privacy and access problems (response to 1)
Posted by web.admin@winslowbowlsclub.org on 26/11/24 16:22

Still searching a solution. 

 

I am advised that I should  either clear the HSTS settings or disable HSTS from my web browser.

What are the possible risks with this recommendation?.

Is there an altnative?

I have many website users that are experiencing this problem "Privacy error: Your connection is not private" It would be a massive task to clear the HSTS settings for all users.

Ideas welcome

Please advise

John Thorogood

3: Re: Web Privacy and access problems (response to 2)
Posted by Joe Oldak on 26/11/24 21:36

Hi John,

Currently www.winslowbowlsclub.org is pointing at squarespace, and winslowbowlsclub.org (without the www) is pointing to Voice and squarespace. I dare say this is the cause of the browser confusion!

I suggest if you sort out the DNS entries to point only to the service that you want to use then it'll all work rather more smoothly :-)

I think the HSTS is a symptom rather than the cause of the problem, and that disabling it or clearing the browser cache won't do you any good.

Thanks

Joe

4: Re: Web Privacy and access problems (response to 3)
Posted by web.admin@winslowbowlsclub.org on 27/11/24 09:24

Thank you for the advice

I cannot see a difference between the domain names, whether with or without the www prefix to winslowbowlsclub.org, and therefore unsure what to change or where.

The domain name on the winslowbowlsclub admin page is winslowbowlsclub.org

The domain name on my squarespace account is also winslowbowlsclub.org

Please give further guidance.

5: Re: Web Privacy and access problems (response to 4)
Posted by Joe Oldak on 28/11/24 21:50

The settings for your site domain on Voice are correct. The problem is with the DNS settings on the domain itself.

This is something that is managed at the registrar where you bought the domain. Looks like the domain is registered at squarespace so you'll need to use their DNS admin pages to set the appropriate A records. (and remove the inappropriate ones!)

Details of the records to set are in the custom domain instructions.

Thanks

Joe

6: Re: Web Privacy and access problems (response to 5)
Posted by web.admin@winslowbowlsclub.org on 08/12/24 16:46

I am advised by squarespace that I need to change the DNS record, and add a custom DNS record

I need to have the CNAME record to do this.
Please advise
Thank you
image.png
7: Re: Web Privacy and access problems (response to 6)
Posted by Joe Oldak on 08/12/24 17:01

Well if they're advising at as well as me then it must be true! :-)

If you want to use a CNAME then you can set it to e-voice.org.uk - since CNAME uses a domain name rather than IP address.

This will work fine with the www subdomain, however you shouldn't use a CNAME on the root domain (i.e., without www), so if you want this to work too then you'll have to use an A record.

For an A record the IP address is 83.136.248.56 - which is in the documentation page that I mentioned previously.

For consistency I'd use an A record for both www as well as the root domain, and then remove any other A records and CNAMEs in use.

Thanks

Joe

8: Re: Web Privacy and access problems (response to 7)
Posted by web.admin@winslowbowlsclub.org on 08/12/24 20:28

Thank you for your advice. I am a long way out of my comfort zone on this and appreciate your patience.

I have removed the sub domain, and focus on the root domain.

Therefore I will use the A record IP address in the domain IP address 83.136.248.56, and emove any other A records and CNAMEs in use.

Thank you for your support. I sincerely hope this will not cause additional problems but resolve the problem.

John Thorogood

 

9: Re: Web Privacy and access problems (response to 8)
Posted by Joe Oldak on 08/12/24 21:12

Yes - that should do it. Though I would keep an A record with 83.136.248.56 for the www subdomain, as that's pretty much standard and what people will expect to see.

Thanks

Joe