frozenicechan

Just to add, Supabase realtime does not guarantee delivery. If you're truly concern about making sure the manager gets notified then a DB trigger with an event into lets say a "notification" table would be 100% better. Then you have the client additionally check on its own too every lets say 5 minutes and go, "did I miss something?" After they get the notify, the client does the lookup on that specific info that changed.

If nothing happens, wait an hour before trying again. Sometimes mail servers are dumb and do dumb things and refuse to deliver emails. Just a problem existed since their creation, waiting is usually the solution 99.9% of the time.

Can be delayed a bit or typically spambox if it's been over 10 minutes.

I'm a bit confused on the order of issues here, what's breaking first the database or auth, and are you 100% on that? Are you seeing high usage or any other logs? By your messaging it sounds like the database actually craps out first, auth then crashes after, you restart the project and it recovers. But, "The database recovered but the auth service process never restarted.". Which then would suggest the restart didn't work. Sorry but this doesn't make sense. Are you doing full project restarts or just fast database reboot?

The initial question would be, what are you using realtime actually for? If I have an internal website that allows to lets say share customer data. I definitely wouldn't want realtime updates to all my employees when employee A says Customer 123 has a new phone number. Only when employee B goes, I need to contact Customer 123 their app would then query what's the details of that said customer. Think of realtime kinda like this discord server(not the best example but bare with me), you and me are having an immediate realtime conversation. The other "employees" at our company lets say are all the users in this server with us. They can see our messages immediately as well. Is this needed in your app?

Google Login Example

1. Yes 2. Yes, but free tier does have limits in terms of how much you can use. Free tier won't be able to handle a production level traffic but by that time I'd hope you upgraded to Pro. 3. Not sure what you mean by that, free tier can't use custom domains. You'll need to upgrade to Pro and then pay an additional $10 a month for custom domain. However this does not affect you hosting like a website mysuperwebsite(dot)com and having all the features utilize it. It just means that APIs and Auth will, depending on what you use, show your supabase .co domain somewhere(I'll post a picture what google login looks like as example). 4. Yes 5. There are also a few odd limitations on Free that don't affect most people like you can't keep on Free and upgrade the database power or space, must upgrade to Pro first. However for a small project it'll probably be fine but what's a small project to you? What's a medium? If you're hosting a small website to show off your favorite brand of cookies and cakes that gets 10 users a day, you'll be fine. If you're looking for something free that'll handle thousands a users a day with multiple interactions, then no, you'll likely burn through that Free tier quickly.

Only support can help, we have some mods around here that can push your ticket a bit more forward but that's no guarantee since the push is very limited. Have to play the waiting game sadly.

This is a user helping user forum but yes, the rest of the world is working fine and only Jio's users are experiencing the issue. Thus the issue is with them as Supabase does not control the internet/other ISPs DNS servers.

Definitely possible, and that log's picture doesn't show anything besides dashboard access. What features of supabase do you all use? Storage? Edge Functions? Is everything locked down as in RLS policies and auth requirements to upload/change stuff? Do you see any unwanted data stored anywhere like in storage or in your tables? Who's actually hosting the website and do you have a CDN in front of it?

Based on OP's name alone, this is likely another person caught by the JioFiber block

You will need to reach out to JioFiber for any possible chance of knowing that information. As said before hand it could be a day or weeks...or longer. It's all Jio's side of things, I doubt it's anything with Supabase who likely just got caught in middle of it all.

Only other solution you have is try doing a proxy for your site to potentially resolve the issue: https://github.com/singh-inder/proxy-to-supabase-cloud

I mean Supabase already stated they've reached out to Jio but that's the extend they can do. The ISP is the one implementing the block for w/e reason and in these situations there's little one can do to convince them to undo the block. Jio will review and make their decision but who knows that could be anywhere from a day to weeks as I've heard of in the past. You'll have to just hope Jio undoes the block but this is the reality of why ISP blocking causes so many problems is they block legit services not-related to the block's original target.

Can you connect to it at all? By chance are there any long running heavy queries? If the database is maxed in usage I've seen people report thier database being unhealthy. If 100% sure it isn't that. Only support likely can help you.

Could be a bad set of servers, in any case have you tried a full project restart on your main project to see if that resolves the issue?

Haven't done this myself. However I don't see why this wouldn't be possible with your own custom docker compose setup: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml

First off, sorry to hear that. Without knowing your setup it's a bit hard to tell. Cloudflare can help to some degree by just covering but now that they know your setup most likely, good chance they maybe able to hit you again directly. This is what I would do and see if it possible. They may not be possible but try and see if it is: 1. Can your API requests be cached off somehow? What I've done for one project to prevent user API abuse is the most common data, 90% of what users will request for GET requests is gathered hourly via a cron task that puts that information into an AWS S3 bucket as a gzip file. That is then served through Cloudflare. Users then when using the site download via the Cloudflare cache and extract that gzip first. 2. Can you use a cloudflare worker to handle your requests so users must use that to do GET requests? If you can have a worker be the one handling your requests as a simple middleman, unless your requests are super heavy or have some odd setup, should be feasible. It's just a simple proxy and you can then do rate limits through there on top of cloudflare's own DDoS protection. 3. Can you improve the query at all so that the data gathered is the bare minimum? Less IO time possible?

awesome, glad to hear it!

You'd have to contact support as this is a user helping user forum. Regardless I doubt they'd be willing to hand that information out without some serious proof you are who you say you are and even then the chance is low. I would just keep guessing your email address you think you used. As for the information you do have. The Supabase URL and anon key are all public facing information, anyone can retrieve that instantly from your application/website so that would not be enough to prove you are the owner of the account in question.

This is mainly a user helping user forum. On top of contacting support have you tried a full project restart?

This is a user helping user forum mostly so no one can help you directly here. If you have an invoice though, that organization will have to pay regardless of your position in that organization. There's no way around this situation that I know of. Which tbh makes sense otherwise people could just create a new project, migrate the data and avoid paying. or have a new project spend it up and owe even more money to supabase.

While not guaranteed there are reports and suggested in the past that if you immediately upgrade to Pro right now, your 7 past days worth of backups will be available to use. Which after you do your restore you can downgrade back to free. Obviously that'll cost you $25 to do so but honestly likely your only possible solution. Though there is one recent report where the upgrade Pro path resulted in them seeing all their backups in progress and not available and had to reach out to support. Not sure the result of that one.

I don't think you can outside of a project upgrade. https://supabase.com/docs/guides/platform/database-size#reducing-disk-size

You can't alter the table directly through the table editor. You have to either use the interface(Sidebar -> Integrations -> Cron -> Jobs), SQL editor, or use a tool like HeidiSQL on your computer to connect to the DB and change entries.

I would focus on these 4 main things to review on if you'll go over any limits. 1. Users: How many MAUs do I have? / What's my peak concurrent user count? 2. Database: Do I have any heavy requests and are they run constantly? 3. Storage/Egress: How much data are my users polling per month? 4. Edge Functions: How many serverless functions do my users call per month?

Yeah it's a bit confusing initially. There are set limits on the free plan, if you go over those you can be restricted and project paused until you pay. On the pro plan with cap on you just have higher limits unless you turn off the cap which allows for a lot more. Just gotta be careful you don't spend like crazy hehe. The confusing piece I'm guessing most run into is the instance part itself where the database runs. On the pro plan you get enough credits to cover a single **micro ** instance size database for the month. Which depending on how many user's you actively have and how heavy your queries that should be a good start. If you have a bigger user base though you'll definitely want to get something a bit bigger like a small or medium but they are jumps even with the $10 off, going from $5 to $50 respectively on top of your pro's $25 a month.

If you are truly only planning to use object storage, I recommend Cloudflare R2 instead. Far more space on their free plan and you don't have to try and keep your project alive on the supabase free plan since you're not using the database side of things.

While I do not know the C# version, from the JS client all those things you listed are either invoked by the client or directly on the supabase side of things itself. There would be no additional server involvement in theory. The problem is without knowing how your client and server directly interact or what all your server did before hand it's a pretty big guess. However my feeling as someone who moved a JS project from Atlas + AppServices to Supabase a year ago, with no additional server, it was actually quite quick in the end. It took far longer doing the data migration from MongoDB into PostgreSQL than setting up the app's features to use supabase lol

By chance are you trying to run this on Linux? You need to manually add the *host.docker.internal:host-gateway* as an extra_host/--add-host to assist the networking side of things.

Well if you have many projects are you at risk of losing access to them? Supabase allows you to have 2 free active projects, any more I'm pretty sure is a breach of policy and can result in a restriction/ban. Not to mention this is costs them money which is why they are paused in the first place when inactive. So just go to the dashboard weekly for both your projects.

Have you tried a full project restart? This resolves a lot of issues when your database is acting up.

I wonder if this is a DNS issue, could you try changing your local DNS settings to like Cloudflare's 1.1.1.1 and see if that helps?

Just anyone who wants to open an issue or generate a solution.

``` const profileImageUrl = isInvitedUser || isEmailUser || isFlyUser ? undefined : getGitHubProfileImgUrl(member.username)``` https://github.com/supabase/supabase/blob/a15ef2b08476df8a54ba4e99df681fcc7ad211e8/apps/studio/components/interfaces/Organization/TeamSettings/MemberRow.tsx#L54

If you want you can open an issue on it in github or anyone else who comes across this thread wants to fix it/open an issue. Otherwise when I have a chance I'll take a look in the next day or two, it be midnight here right now heh.

okay so the team page is clearly defaulting everything to github

LOL

https://myaccount.google.com/ so if you go there, is that same picture there?

Is it by chance a gmail account? As my gmail account also has its own avatar. But whomever if your email provider is likely providing that picture by my guessing.

How do you signin to your Supabase account as it's likely pulled from that provider. For example I utilize Github login and so my profile user picture is pulled from Github's profile automatically. Thus I would likely need to change it in Github to be reflected in Supabase.

Are you trying to get this working locally or in Supabase Cloud? Since you specifically talk about config.toml I'm going to assume local which also interesting you say: "I have NOT passed a secret" does that also mean you are not setting it environmentally? **SUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_SECRET=** is definitely needed

I haven't done this with edge functions so I can only assume something is available. But my immediate solution would try connecting your supabase metrics to like Grafana which then notifies you when something is erroring/timing out/etc. https://supabase.com/docs/guides/telemetry/metrics or if you has the money to and are on a higher plan. Log Drain and handle monitoring your own way: https://supabase.com/docs/guides/telemetry/log-drains

eu-west-2 is working for me as well just fine, no issues reported on cloudflare's front either. could be a small set of servers

You'll need to open up a support request to do so as this is mostly a user helping user forum. Is this on a free plan or pro?

One of the main selling points of docker is what's inside always work no matter where it runs, it really doesn't care what's on the outside. Thus select any version you want and 99.9% of the time it'll work as long as you're not do something unique with OS fun which you and most people will not. Personally I would go with the version at 17.6.1.063 (just upgraded myself and its working great) that way you're matching what's the latest in the cloud at the moment. Which you should do the upgrade for your own cloud in Supabase to this version as well while you're at it.

<@1436739289604952094> What's the status of your project say? Have you restarted the project?

It does actually install the CLI within the project. Once added you can run all the commands straight from the project folder. The question is, what specifically are you trying to do? There's can be different tools to setup along with depending on what you're looking for.

Thinking you mean Bolt?

true