As I was roaming aroud Folksy my Firefox put up a warning that the site was insecure. Is this something you need to look at, Folksy? I see from other posts that you may be having problems.
I 'm on Firefox and have never had any warning about Folksy, seems a bit odd x
Oh how strange as I have folksy open in firefox and IE and at the moment Iām typing this post in Firefox and Iāve never had that message.
I have if Iām looking at a listing and want to add them as a favourite seller I get that message everytime. Iām using chrome. I have to open their shop right up and then favourite from their front shop page. This does need to be sorted as it could put potential buyers off.
1 Like
Are you using an old link to get to your Folksy shop? Folksy has been out of beta mode for a while now. If you use the folksy.com or username.folksy.com url hopefully the warnings will stop. 
No, I definitely clicked on a link within Folksy. I have tried to replicate my searches this morning but so far I have been unable to find that link that gave me that beta-folksy address. Perhaps KernowClaire is right. I had been browsing and favouriting shops and items at the time.
Yes I still get the same thing about a security message and to leave the site straight away if I fave a shop as @kernowclaire has said. Itās been happening for months. I use IE. If I didnāt know Folksy I probably would leave the site and not come back!! @Folksyadmin
I think it might be to do with that āfollow this shopā button on the item pages which hasnāt worked for a while. I clicked it yesterday and after that get into some sort of a backwater with messages about beta folksy. I closed the browser and started agian and all was fine. Iām sure @dougfolksy has it on his radar.
No, it is the favourite shop button from an item rather than the shop front. Every time I click on it the address bar flashes up something with beta in it and then goes to a full screen message:
There is a problem with this websiteās security certificate.
The security certificate presented by this website was not issued by a trusted certificate authority.
Security certificate problems may indicate an attempt to trick you or intercept any data you send to the server.
We recommend that you close this webpage and do not continue to this website.
Recommended iconClick here to close this webpage.
Not recommended iconContinue to this website (not recommended).
Itās been doing it for months. If I go to the shop front and click favourite itās fine. Iām pretty sure this could put people off. From a previous thread there are a few of us itās happening to so must happen to some customers as well.
Yes, I just got this message when I tried to favourite a shop from within a listing, as mentioned by Julie above.
"Your connection is not secure
The owner of beta-ep.folksy.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.
Learn moreā¦"
1 Like
Iāve been able to favourite a shop from within a listing with no problem just now. Iām wondering if the shops people are trying to favourite are still on the beta site and are shops that have been on Folksy for a while and havenāt updated for some reason? Maybe people could look at the address bar of the shop they wish to favourite and check? They could then send the shop link to folksy [support@folksy.com] alerting them to the problem if not already done so.
Another thing to do is clear your browsers cache and try again to favourite it. (https://folksy.uservoice.com/knowledgebase/articles/100283-folksy-is-broken)
As an experiment Iāve just tried it with your shop @BigBirdLittleBird and the same thing. My lap top is only a few months old itās been happening from day one every single time I have tried! It doesnāt seem to happen to everyone but I canāt explain it!!! 
1 Like
ok Iāve just had a update in firefox and I tried favouriting one of your little birds Liz @BigBirdLittleBird and everything was fine no firefox warning and youāre url doesnāt have beta in it either.
1 Like
Have you cleared your browserās cache? Also Folksy say that IE8 is the best browser with problems with IE7 (although thatās just to do with how things look rather than operate).
https://folksy.uservoice.com/knowledgebase/articles/77012-i-m-having-problems-using-folksy-with-internet-exp
Iāve never had it either. Interesting that @DewDropCrafts had the same error with my page as I know that isnāt beta. Also that both @DewDropCrafts and @WoollyWoodlanders have the same problem but using different browsers.
Iāll tag @dougfolksy and @folksycontent again to see if they can shed any light.
Itās not favouriting the item itās favouriting the whole shop from an item. Favouriting the item is fine.
It occurs to me after reading the comments, that maybe a function is being called which is still in the beta site. I hate to think that potential customers are put off from staying on the Folksy site; and they may never want to return. I am sure that @dougfolksy is on the case!
2 Likes
As best I can think, this might be happening because people are on the wrong URL, which has ābeta-epā in it. This wouldnāt be recognised by the browser as belonging to our certificate, so would generate the warning you see.
As to how they are ending up on that URL, Iām not sure. It would be really good to figure that out!
Is this easily replicable by anyone? Does anyone here see this error every time they try to favourite a shop (or perform any particular action)?
I was intrigued by this as I havenāt had a problem ā¦ so far! So I did the sensible thing and tried to favourite a shop from an item listing. Yes ā¦ FOLKSY YOU HAVE A PROBLEM!
This could lose us sales - and as I have just had 1000 business cards printed with the Folksy details I donāt want to have to jump ship.
Please Folksy - sort this out. I have already lost a possible retail deal because the retailer claimed that they couldnāt find my shop on Folksy. This is not good news.
Hi ā please could you let us know which item listing you tried to favourite from?
And maybe which browser youāre using, on which operating system?
Iām struggling to replicate the issue.