I have one computer where I can't access SicEm365 from. I always get 403 Forbidden Microsoft-Azure-Application-Gateway/v2 error page in Chrome.

I've cleared every history, cookie, cache, etc. imaginable but nothing works. I've disabled my VPN.

I have another computer I use just as much in Chrome with the same settings and it works fine. I can access the site perfectly from my phone. It's just this one machine and SicEm is the only site in the world it affects.

Please help!

You might give this a try

1. Check the Hosts File: Sometimes, the website may be blocked by entries in the Hosts file. You can check and edit the Hosts file to ensure that there are no entries blocking access to SicEm365.

2. Check Firewall or Antivirus Settings: Your firewall or antivirus software may be blocking access to the website. Temporarily disable your firewall or antivirus software and try accessing the website again to see if the issue persists.

3. Flush DNS Cache: Flushing the DNS cache on your computer can sometimes resolve connectivity issues. Open Command Prompt as an administrator and type the command "ipconfig /flushdns" to clear the DNS cache.

4. Try a Different Browser: If you are using Chrome, try accessing the website using a different browser (such as Firefox or Edge) on the problematic computer to see if the issue is browser-specific.

5. Check Proxy Settings: Ensure that there are no proxy settings configured on the problematic computer that may be affecting access to the website.

I had an issue accessing a website, but in my case, it was a payment gateway service I was using through DashDevs Payment Gateway Services.
Situation:
I also encountered a 403 Forbidden error, but the problem was limited to one device; everything worked fine on others. It happened in Chrome, but other browsers didn't solve the issue either.
What I Tried:
Checking the Hosts File: Everything was clean in my case.
Antivirus and Firewall: The issue was with my antivirus settings. As soon as I added the website to the exceptions, it worked perfectly.
DNS Cache: Running the
ipconfig /flushdns
command in the Windows console really helped speed up the reconnection to the site.
Different Browsers: Firefox helped temporarily, but the issue in Chrome was resolved only after updating it to the latest version.
Proxy: I discovered that a manually set proxy in my system settings was no longer working. Once I removed it, everything worked fine.
From my experience with https://dashdevs.com/payment-gateway-services/, I've learned that sometimes the issue is not just on the user's side but also in the service's infrastructure settings. If something similar happens, it's always helpful to contact technical support.

That does sound frustrating, especially since you've already ruled out the usual suspects like cache, cookies, and VPN. Sometimes a stubborn 403 on a single machine points to something deeper at the network or configuration level for instance, a corrupted profile in Chrome or a local security policy interfering with Azure's gateway checks. You're right to compare across devices because it highlights that the issue isn't with the site itself but how that one system is handling requests. Innovation and Competitive Advantage Having developers on your team allows you to create unique features, services, or platforms that differentiate you from competitors. In fact, businesses dealing with similar one-off technical hurdles often discover the long-term solution lies in expanding technical capabilities. That's why many decide to hire full stack developers who can not only troubleshoot situations like this but also design resilient systems that prevent them in the first place.