gcui-art / suno-api

Use API to call the music generation AI of suno.ai, and easily integrate it into agents like GPTs.
https://suno.gcui.ai
GNU Lesser General Public License v3.0
1.13k stars 257 forks source link

SUNO UPDATED THEIR CLIENT AND BROKE THE API #127

Open calvinusesyourcode opened 1 month ago

calvinusesyourcode commented 1 month ago

Description

client?_clerk_js_version=4.73.3 seems to have broke the API. The cookie now has extra values not previously present.

Expected behaviour

Everything working fine like 2 days ago.

Output

/api/get_limit returns Internal server error. Error: Failed to get session id, you may need to update the SUNO_COOKIE and no amount of updating the cookie works. /api/custom_generate returns a vague Vercel error.

GSejas commented 1 month ago

Seeing the same problem over here.

swumagic commented 1 month ago

you need to update the SUNO_COOKIE every seven days。my client?_clerk_js_version=4.73.3 API IS OK

Description 描述

client?_clerk_js_version=4.73.3 seems to have broke the API. The cookie now has extra values not previously present.client?_clerk_js_version=4.73.3 似乎已经破坏了 API。 cookie 现在具有以前不存在的额外值。

Expected behaviour 预期行为

Everything working fine like 2 days ago.一切都像两天前一样运行良好。

Output 输出

/api/get_limit returns Internal server error. Error: Failed to get session id, you may need to update the SUNO_COOKIE and no amount of updating the cookie works. /api/get_limit 返回 Internal server error. Error: Failed to get session id, you may need to update the SUNO_COOKIE 并且对 cookie 进行的任何更新都不起作用。 /api/custom_generate returns a vague Vercel error. /api/custom_generate 返回一个模糊的 Vercel 错误。

swumagic commented 1 month ago

Seeing the same problem over here.在这里看到同样的问题。

you need to update the SUNO_COOKIE every seven days。my client?_clerk_js_version=4.73.3 API IS OK

mshartman commented 1 month ago

Description

client?_clerk_js_version=4.73.3 seems to have broke the API. The cookie now has extra values not previously present.

Expected behaviour

Everything working fine like 2 days ago.

Output

/api/get_limit returns Internal server error. Error: Failed to get session id, you may need to update the SUNO_COOKIE and no amount of updating the cookie works. /api/custom_generate returns a vague Vercel error.

I don't think the API being broken is explicitly a cookie issue as I am able to get_limit after updating my cookie. It seems to me that the Suno update changed some of the dependencies relied upon in SunoApi.ts -- which may be fixable.

MelvinMaonn commented 1 month ago

Description

client?_clerk_js_version=4.73.3 seems to have broke the API. The cookie now has extra values not previously present.

Expected behaviour

Everything working fine like 2 days ago.

Output

/api/get_limit returns Internal server error. Error: Failed to get session id, you may need to update the SUNO_COOKIE and no amount of updating the cookie works. /api/custom_generate returns a vague Vercel error.

I don't think the API being broken is explicitly a cookie issue as I am able to get_limit after updating my cookie. It seems to me that the Suno update changed some of the dependencies relied upon in SunoApi.ts -- which may be fixable.

So do you have any idea to solve the problems?

hanhnq commented 1 month ago

Description

client?_clerk_js_version=4.73.3 seems to have broke the API. The cookie now has extra values not previously present.

Expected behaviour

Everything working fine like 2 days ago.

Output

/api/get_limit returns Internal server error. Error: Failed to get session id, you may need to update the SUNO_COOKIE and no amount of updating the cookie works. /api/custom_generate returns a vague Vercel error.

I don't think the API being broken is explicitly a cookie issue as I am able to get_limit after updating my cookie. It seems to me that the Suno update changed some of the dependencies relied upon in SunoApi.ts -- which may be fixable.

So do you have any idea to solve the problems?

Signout and use the other account

taaako commented 1 month ago

[FYI] I tried this and it worked for me! Hope this helps. If your cookie starts with something other than __client, such as __cf, look for the part that starts with __client. (I found mine about in the middle.) If you still can't find it, you may have to be logged in to find it. If you find it, try putting it in the .env from where it starts with __client. *But I checked the cookie for the SUNO service and it started with __client, so maybe it's already solved?