Why am I receiving Deceptive Site warnings?

I haven't logged in to update in a while, so when I did, I was surprised to see this warning: 

Deceptive site ahead

Attackers on trinalynnconner.weebly.com may trick you into doing something dangerous like installing software or revealing your personal information (for example, passwords, phone numbers, or credit cards).

 

What do I need to do? 

5,606 Views
Message 1 of 23
Report
1 Solution

Solution

I was looking at the rest of the settings and realized my site was listed as an online store, but it's really more of a blog and information. I changed it to a blog, published it again, and the warning is gone as of now. 

View Solution >

5,564 Views
Message 4 of 23
Report
22 REPLIES 22
Square Champion


@BernadetteA wrote:

Hi @tlconner and @Minion 

 

Just wanted to jump onto this thread to assist. When I looked at the settings from the backend, the SSL was not enabled. Where were you checking for this @tlconner? It should be available under the Settings tab in the editor. 

 

I re-enabled it, and now I see the site is loading securely with a lock. 

 

 

 

Screenshot of the Settings tab: 

 


 

Since the site is used for only a blog, an SSL shouldn't be required though right @BernadetteA ?

 

With the SSL re- enabled, I am now seeing the warning on the blog section only of the website on my end as of 5;45 am ET

Dan
CoatingWorx
Square Super Seller
Check out Square support center for additional help.




484 Views
Message 22 of 23
Report
Alumni

Hey @Minion  👋

 

All websites, regardless of content or type, should be secured with SSL. Otherwise you risk the chance of of not even being able to connect to the server to view the site. This would be a "connection error" instead of the deceptive site warning you pointed out on the blog page. 

 

@tlconner I noticed you have some embedded content on your blog page. Do you recall everything you have added, and how did you add it? You may need to remove embedded code one by one while checking the live site in order to narrow down where the error is coming from.

 

On the same note, if you notice any of the embedded code referencing a URL that is "http" and not "https", the fix may be as simple as just adding the "s" into the URL. I can try to take another look into this today.

454 Views
Message 23 of 23
Report