3CX DLL-Sideloading attack: What you need to know
Hi, since a few days I'm not able to open firewallsizing.sophos.com as a partner. Sometimes it works, sometimes it don't. I couldn't figure out what the issue is - I tried Firefox and Edge, both are reporting the same error:
Anyone else having this issue?
Thank you for contacting the Sophos Community and bringing this to our attention.
We have reported this internally to the pertinent team.
it's still not working - any update on this?
If you’re accessing the URL directly it won't work and probably you’ll get the error of the redirects.
You need to access it via the Partner Portal >> Sales >> Firewall Sizing Tool
Can you confirm if you’re accessing this way?
Hi Emmanuel, this would make no difference because the site is referring to https://firewallsizing.sophos.com
It does because the Site is only for Partners, so accessing directly without authenticating before won't allow you to connect.
I just tested again and it is working as expected, working when accessing from the Partner Portal not working when accessing directly.
There is currently a ongoing investigation with Sophos IT about this facility. This issue seems to be occurring during load times. Sometimes it works fine.
Hey Emmanuel, I am a partner and I am logged in. Still no access. I noticed that when I hit the hyperlink, i get redirected to localhost:5000 ? I have tested this in several browsers, I have tested it at home while I was logged into partner portal and my colleagues having the same issue.
ah, thanks for clarification.
I still have the same observation, when logged in as partner, the link immediately goes to "localhost:5000" which obviously cannot be resolved properly.
Mit freundlichem Gruß, best regards from Germany,
New Vision GmbH, GermanySophos Silver-Partner
If a post solves your question please use the 'Verify Answer' button.
Still not working!
Thank you for the update, apologies for the delay, our team continues to actively work on resolving this issue.
Our team has pushed a fix that has reduced the frequency of the error, and a permanent one is in the works to be released by the end of the week beginning of the next one.
Just as an update, fix has been released and tested and should be working now.