# Production Website Broken **URL:** \ **Category:** Ask us anything\ **Created:** [June 22, 2025, 7:24pm UTC](https://community.weweb.io/t/production-website-broken/18882 "2025-06-22T19:24:20Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![ovidysus](https://avatars.discourse-cdn.com/v4/letter/o/6f9a4e/32.png) [@ovidysus](https://community.weweb.io/u/ovidysus)\ **Post date:** [June 22, 2025, 7:24pm UTC](https://community.weweb.io/t/production-website-broken/18882/1 "2025-06-22T19:24:20Z")
I am having massive issues with weweb right now. For some reason, I am getting unable to read id on a production project. This has bricked our production site. Thank god it’s a sunday, but given that there is no clear evidence that any fixes will be made anytime soon, we are looking to download the project. But, the issue with that is we can’t find any clear or accurate guidance on how to download the project. When we finally found the download button, it was grayed out, even though we are on essential & grow, which says we can download. We upgraded to annual, and it is still grayed out. This is beyond frustrating and I cannot stress strongly enough that we web is NOT stable or safe for a production environment. ---
**Author:** ![BrancoDigital](https://avatars.discourse-cdn.com/v4/letter/b/7ba0ec/32.png) [@BrancoDigital](https://community.weweb.io/u/BrancoDigital)\ **Post date:** [June 22, 2025, 7:41pm UTC](https://community.weweb.io/t/production-website-broken/18882/2 "2025-06-22T19:41:48Z")
Hey ovidysus, check my reply in the other thread - hope this will help you! > [@URGENT -- Weweb can't load collections?](https://community.weweb.io/t/urgent-weweb-cant-load-collections/18876/9): > > My current solution: Supabase auth and tables started working after resetting to a previous editor state Disables “Proxy request server side (bypass CORS)” for REST API data collections, fixed most of my data collections this way For those that didn’t, such as custom [fly.io](http://fly.io) microservice calls, created Supabase Edge functions to call these APIs instead I was able to restore most of my platform’s functionality this way, hoping this won’t break again when weweb fixes the core issue! ---
**Author:** ![ovidysus](https://avatars.discourse-cdn.com/v4/letter/o/6f9a4e/32.png) [@ovidysus](https://community.weweb.io/u/ovidysus)\ **Post date:** [June 22, 2025, 9:17pm UTC](https://community.weweb.io/t/production-website-broken/18882/3 "2025-06-22T21:17:19Z")
Solid patch godsend thank you ---
**Author:** ![Raphael](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raphael/32/13247_2.png) [@Raphael](https://community.weweb.io/u/Raphael)\ **Post date:** [June 22, 2025, 10:52pm UTC](https://community.weweb.io/t/production-website-broken/18882/4 "2025-06-22T22:52:47Z")
We are looking into this, @BrancoDigital’s solution worked for users affected. Apologies for this issue, We will share a detailed post-mortem once we’ve identified the root cause - hopefully within the next 12 hours. ---
**Author:** ![pc\_strategyandops.co](https://avatars.discourse-cdn.com/v4/letter/p/f04885/32.png) [@pc\_strategyandops.co](https://community.weweb.io/u/pc_strategyandops.co)\ **Post date:** [June 23, 2025, 8:09am UTC](https://community.weweb.io/t/production-website-broken/18882/5 "2025-06-23T08:09:10Z")
Is there any update on this. Can’t make any outbound REST API calls. ---
**Author:** ![Raphael](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raphael/32/13247_2.png) [@Raphael](https://community.weweb.io/u/Raphael)\ **Post date:** [June 23, 2025, 8:18am UTC](https://community.weweb.io/t/production-website-broken/18882/6 "2025-06-23T08:18:22Z")
The team is on it, we hope the services will be back up by 6am EST. Keeping you all posted. The issue affects collections that rely on our servers to be fetched: Airtable plugin, REST API with CORS. ---
**Author:** ![Raphael](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raphael/32/13247_2.png) [@Raphael](https://community.weweb.io/u/Raphael)\ **Post date:** [June 23, 2025, 8:46am UTC](https://community.weweb.io/t/production-website-broken/18882/7 "2025-06-23T08:46:18Z")
The problem is fixed for every application **not using the SQL plugin**. We are now working on a fix for applications using this plugin. We’ll keep you updated. ---
**Author:** ![nocodecreative.io](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/nocodecreative.io/32/14235_2.png) [@nocodecreative.io](https://community.weweb.io/u/nocodecreative.io)\ **Post date:** [June 23, 2025, 9:58am UTC](https://community.weweb.io/t/production-website-broken/18882/8 "2025-06-23T09:58:52Z")
@Raphael I had planned to self-host my work using the code export. If collections rely on your servers, will this affect my ability to self-host the solution? Or would deploying the solution in a self-hosted production environment mitigate that risk? ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [June 23, 2025, 10:40am UTC](https://community.weweb.io/t/production-website-broken/18882/9 "2025-06-23T10:40:59Z")
Unless you route through WeWeb’s servers, you should be safe. Use Xano or Supabase, without WeWeb’s CORS routing and you should be fine. ---
**Author:** ![nocodecreative.io](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/nocodecreative.io/32/14235_2.png) [@nocodecreative.io](https://community.weweb.io/u/nocodecreative.io)\ **Post date:** [June 23, 2025, 10:42am UTC](https://community.weweb.io/t/production-website-broken/18882/10 "2025-06-23T10:42:22Z")
I don’t use Xano or Supabase, I have a custom Express backend which links to Postgres using Prisma, with custom auth, via REST with JWT ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [June 23, 2025, 10:49am UTC](https://community.weweb.io/t/production-website-broken/18882/11 "2025-06-23T10:49:44Z")
Unless you use the WeWeb’s servers to avoid CORS, you should be safe. ---
**Author:** ![Mark\_Pederson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/mark_pederson/32/14758_2.png) [@Mark\_Pederson](https://community.weweb.io/u/Mark_Pederson)\ **Post date:** [June 23, 2025, 10:55am UTC](https://community.weweb.io/t/production-website-broken/18882/12 "2025-06-23T10:55:36Z")
> [@Broberto](#): > > Use Xano or Supabase, without WeWeb’s CORS routing and you should be fine. By “without WeWeb’s CORS routing” I assume you mean setting `Proxy the request to bypass CORS issues` to OFF? I have seen some crazy CORS errors in the past - but nothing consistent. I wonder if I need to make sure all my requests have this setting off? (We ONLY call auth XANO endpoints from front end - no 3rd party APIs) ??? ---
**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\ **Post date:** [June 23, 2025, 10:57am UTC](https://community.weweb.io/t/production-website-broken/18882/13 "2025-06-23T10:57:01Z")
Yes. CORS need to be set up properly to allow your origin to call your API. ---
**Author:** ![Mark\_Pederson](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/mark_pederson/32/14758_2.png) [@Mark\_Pederson](https://community.weweb.io/u/Mark_Pederson)\ **Post date:** [June 23, 2025, 11:00am UTC](https://community.weweb.io/t/production-website-broken/18882/14 "2025-06-23T11:00:49Z")
So, in our case (only Xano auth’d calls from WeWeb) - we should have this setting to be OFF on all our requests so that we don’t ever use WeWeb proxy for any request, right? ---
**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\ **Post date:** [June 24, 2025, 7:30am UTC](https://community.weweb.io/t/production-website-broken/18882/15 "2025-06-24T07:30:56Z")
Hello everyone, we’ve release an update on what happened: > [@Update on the recent server failure issue](https://community.weweb.io/t/update-on-the-recent-server-failure-issue/18915): > > Between Saturday the 21st of June 2025, and Monday the 23rd of June 2025, we experienced a failure on our plugins server. As a result, data fetching for applications using the Airtable plugin, SQL plugin, and REST API plugin with CORS enabled in production was disrupted. This also impacted access to the editor for applications relying on these plugins. The issue has now been resolved, and the server is back to normal, functioning properly. The issue went undetected by our monitoring tools bec…