Best answer

Connection Issues with Magento 2.4

  • 22 June 2024
  • 5 replies

The last time there was a conversation about this was 2 years ago. 

I am using Magento 2.4.3 p2. 

When i try to connect using  or, throw up this error.

and when I used, it gives me: 

There was never a pop up, i can confirm that my credientials are valid as i can login to my Magento account and my account definitely has the proper permissions. 

I also did not enter anything in the store code field. 


Please advise, it would be a huge help if i am able to connect to Magento


Best answer by ken.a 25 June 2024, 08:49

View original

5 replies

Hi sigmacreed,

It sounds like you're experiencing connectivity issues with Magento 2.4.3 p2 when accessing specific URLs. Here are a few steps you can take to troubleshoot:

  1. Check URL Configuration: Ensure that the URLs you're using to connect to Magento are correctly configured in your store settings. Verify if HTTPS and the correct path are set up in Magento's configuration.

  2. Clear Cache: Clear Magento cache and browser cache to rule out any caching issues that might be causing the error.

  3. Verify Permissions: Double-check permissions for your Magento account to ensure they're correctly configured for accessing the necessary URLs and functionalities.

Regarding our expertise, just as resolving configuration issues is crucial for Magento connectivity, optimizing workflows in software like Lightroom for Android Mod Apk ensures smoother editing experiences. is essential for photographers.

I checked the url in the backend and it matches what i keyed in. I cleared and flushed all caches in Magento and my browser. 
it still comes out with the error “Request doesn’t match any route”

Userlevel 7
Badge +6

Hi there @sigmacreed,

Before we dig deeper into this, have you recently enabled 2FA for your account in Magento?

I'll be keeping an eye out for your response!

Hi @ken.a ! 

There's no 2FA in my account

Userlevel 7
Badge +6

Thanks for the update @sigmacreed.

I did some digging into this, and it seems like the issue you’re running into is a known bug with Magento 2.X. Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

I appreciate your patience and understanding.