I wanted to get the new free assets from this Tuesday, but I can’t access the FAB website.
I get the following message: “Sorry, we couldn’t find that page”.
As I said, I tried on several platforms with different operating systems and updated browsers, but I always get the same message “Sorry, we couldn’t find that page”. It’s not working and I don’t know what is happening.
Are you from Spain or your Account Location from Spain or any Spanish speaking Country?
Because if it is automatically appending /es-es then it might be Account or Location specific Problem.
Do you have any alternate Account through which you could try?
Since you mentioned that regardless of OS, Browser you are facing same error it might Indicate Location or Account specific Problem which only could be solved by contacting Fab Team through email support.
or maybe you could ask any of your Local Friend who would have Fab Account to see whether or not.
I would recommend sending email for Support to Fab Team.
I’m from Spain, and I also haven’t been able to log into my account. Every time I tried to log in using a browser or alternative device, I encountered this error. If I enter fab.com, it redirects to www.fab.com/es-es/es-es/, showing the message: “Sorry, we couldn’t find that page.” In this case, using https://www.fab.com/es-mx/ works and allows me to access Fab and my account.
Thank you everybody. I see I’m not the only one.
I asked friends of mine if they could try this too. Some of them had the same problem, some didn’t.
We are from Spain, indeed. I’m still having that problem.
I appreciate the link https://www.fab.com/es-mx/ . This link works, but it doesn’t let me see everything on FAB. I still sometimes see “Page not found” and the message “Sorry, we couldn’t find that page” when I go to the featured content on the FAB feed, at the top of the website, but at least I was able to get this week’s free assets thanks to the link.
Sorry about that. There’s a bug specifically with the Spanish (Spain) localized version of the site incorrectly redirecting to that duplicated .../es-es/es-es/... path. We’ll get it fixed ASAP, but indeed the only workaround for now is to manually navigate to one of the other locales, such as .../es-mx/