Getting 403 Forbidden webpage after latest F-Secure update

Lawrence

I get a 403 Forbidden webpage (on all web browsers) when trying to navigate to:

http://sm.tradetoolsfx.com/smfxdemo/desktop.html

 

This happened immediately after my upgrade 10 mins ago.

 

How can i get my F-secure (TalkTalk Super Safe Boost) to allow this site?

Simon

I'm getting a "Harmful website blocked" warning from FS when I try the link, but it does give me the option to allow it (which I haven't).  I guess it could be a false positive, in which case you can Submit the URL to the labs, and they will reassess it, or could it be that the site does actually contain something nasty?

Lawrence

the site is a webtrading site i have used before which FS didnt have an issue with prior to the update.

 

I read here:

https://community.f-secure.com/t5/F-Secure-SAFE/Bug-w-IS2016-causes-403-error/m-p/78971

 

that someone else was having the 403 issue but this is reported to have been resolved.

 

I only mention this because i get a 403 error yet you correctly get a FS warning and option to unblock.

If it wasnt for this I wouldnt have an issue.

 

So maybe the real question is why am i still getting a 403 msg if the above link says the issue is fixed??

Simon

I'm actually using the beta FS Protection: https://beta.f-secure.com/welcome/  This will be a later version that the current SAFE builds, so that may explain why I'm receiving the block page instead of the 403, but that's just a guess.

 

If no one responds here fairly soon, I can only suggest that you send in a Support Ticket, or Submit the URL as mentioned before, for what might be a quicker fix.  Alternatively, you may wish to consider joining the Beta program, upon which you will receive the latest build, with free licensing for as long as you remain an active tester. 

Simon

I've tried about 10 times to get the link to the Beta to work, so trying again in a separate post:

 

https://beta.f-secure.com/welcome/

Ukko

Hello,

 

Sorry for my reply.

If you are sure about "safe status" of this page (and not able to get result from F-Secure SAS about reasons or re-rate action; this is can to take hour or some hours.. or some days with my experience).

Maybe you have two workarounds/steps:

 

--> You get forbidden webpage.. maybe just about certain pages (like "something.html").

How I can to understand.. main domain is marked as "harmful" (on current day) too.

Do you able to open just main domain-page? Maybe you get "Block-page" with allow-to-visit option.

 

--> Or just from first: Open main UI of F-Secure installation.

Goes to "Browsing Protection" module settings. Open there settings.

And get "place", which called like "List of deny/allow webpages" (Exclusions for webpages). And add THIS URL under Allow-tab.

Save result. And probably you will be able to use page.

 

 

And about "why you do not get fix"... maybe based on TalkTalk (which do not release this fixed build to customers). This is may be.

 

Sorry for my reply.

 

Thanks.

Lawrence

thanks, a temporary solution is to allow it in Browser Protection. I have also submitted the URL so will wait to hear from them why they consider it unsafe

Lawrence

Thx Simon. I would like to join the beta test group but not sure if it would include my other PCs. The membership with Talktalk allows for 10 pcs.

Is the beta on an individual pc basis? Or can I still manage say 10 pcs in a group?

Simon

Hi Lawrence,

 

The short answer is, I don't know.

 

What I would suggest is that you post the question in the Beta Forum, and hopefully someone from the team will see it and respond.  Alternatively, you could just apply on the Beta Site, explaining your situation, and see what happens.  You do get the opportunity to test on multiple devices under your own subscription, but I'm not sure if that would extend to ten machines.  Talk to them, and I'm sure they will be helpful. 

 

Bear in mind, though, that with beta products, there can be the occasional drama, so you may want to consider whether you want to install a beta version on a 'mission critical' device.  That said, I've been a beta tester for about three years now, or maybe more, and I've not had that many major problems.