Question: Attention needed

RogueEdit / pyRogue

Educational Project

GNU Affero General Public License v3.0

51 stars 38 forks source link

Question: Attention needed #80

Closed Ashukyo closed 3 months ago

Ashukyo commented 3 months ago

A clear and concise description of what the question is.

I tried logging into the editor but it wouldn't let me. It keeps saying login failed. 403 Client error: forbidden for url : https://api.pokerogue.net/account/login . I tried 3 different accounts to see if it worked and nothing. Do you know how I could fix this by chance?

JulianStiebler commented 3 months ago

You tryed the hotfixed version? V0.1.6

Thizzle715 commented 3 months ago

You tryed the hotfixed version? V0.1.6

Just gonna reply for them rq, The hotfixed version is having the same issue at the moment. It really is a game of cat and mouse.

Thizzle715 commented 3 months ago

image_2024-06-06_053950258

DivineDiamond commented 3 months ago

im having the same issue. is it cool if i just leave this here to be notified when theres a fix?

caprino12 commented 3 months ago

i have the same problem

Ashukyo commented 3 months ago

You tryed the hotfixed version? V0.1.6

I just did, it works thank you very much. Didn't see the hotfix earlier.

Edit: It is no longer working same issue as stated in the op

JulianStiebler commented 3 months ago

Yeah we are trying to get another fix but ...^^

JulianStiebler commented 3 months ago

v0.1.2 works with the old login logic tho

Reizen82 commented 3 months ago

Seems to be getting this when it tries to save to the server for 0.1.2

SummerBreezze commented 3 months ago

Yeah we are trying to get another fix but ...^^

how long would it take?

JulianStiebler commented 3 months ago

@Reizen82 500 is always a server error, wait a bit it resolves itself

and so far every version is working again. Its just that they ban the header information if its too often used and we have soo many users its hard to keep on top^^ but those access headers are unbanned after a while so it resolves itself.

The fix should be avaible today so we have fallback option that imitiaates your browser, which should ALWAYS work, also we can construct new heaeder dat from remote source and such with the new update

JulianStiebler commented 3 months ago

v0.1.5 v0.1.6

are working for me currently again, use as long as the headers are free to live :'D

To explain; we need access information to imitate browsers to be able to get a response from the server, and they "ban" those access information due to many users on the same access information. -so dumb xD

And yea next version we hve both loginlogics combied, login with your own browser and such or the fast method as now (which you see is unreliable)

We didnt even touch the v0.1.5 v0.1.6

and they just work again.

Sorry for the inconvenience but this is not on us really, but we trying our best to deliver a smoother experience :) Also, the next version has more clear error responses aswell