Production Website Broken

Ask us anything
1

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.

2

Hey ovidysus, check my reply in the other thread - hope this will help you!

2 Likes
3

Solid patch godsend thank you

4

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.

5

Is there any update on this. Can’t make any outbound REST API calls.

6

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.

1 Like
7

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.

8

@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?

1 Like
9

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.

1 Like
10

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

11

Unless you use the WeWeb’s servers to avoid CORS, you should be safe.

1 Like
12

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) ???

1 Like
13

Yes. CORS need to be set up properly to allow your origin to call your API.

1 Like
14

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?

1 Like
15

Hello everyone, we’ve release an update on what happened: