Skip to content
This repository has been archived by the owner on May 3, 2023. It is now read-only.

403 on sending test result [WRU] [/api/v1/quicktest/results] #83

Closed
r0bs opened this issue Jan 24, 2022 · 19 comments
Closed

403 on sending test result [WRU] [/api/v1/quicktest/results] #83

r0bs opened this issue Jan 24, 2022 · 19 comments
Labels
bug Something isn't working

Comments

@r0bs
Copy link

r0bs commented Jan 24, 2022

Describe the bug

On sending results, I started to receive 403 responses about an hour ago. There seems to be some kind of authorisation issue with my account, that suddenly occurred on the server side.

Before everything worked perfectly, returning 204 responses.

My certificate name: covidbs-wru.schnelltestportal.de-Server-01c37d1f8a33f63c00855fbe0e8b4f63

Expected behaviour

Get a 204 on a valid request.

@r0bs r0bs added the bug Something isn't working label Jan 24, 2022
@jetwes
Copy link

jetwes commented Jan 24, 2022

Same here. Massive Problems since 13:00
I have over 500 Tests in Backlog already.

@brkoglu
Copy link

brkoglu commented Jan 24, 2022

Same here since 13:00 approx. also on PROD

@jetwes
Copy link

jetwes commented Jan 24, 2022

On production. Desaster. All clients and customers are going crazy..

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 24, 2022

cc @dsarkar, @thomasaugsten, @mlenkeit

Incident?

@thomasaugsten
Copy link
Member

I thinks @ascheibal can help here

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 24, 2022

@thomasaugsten It seems like there is a current incident. Can you open an internal investigation?

@jetwes
Copy link

jetwes commented Jan 24, 2022

Is there any ETA on this topic. Is there a status page or something like that?

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 24, 2022

@jetwes

There is no status page. I hope @thomasaugsten started an internal investigation and this will be fixed soon.

@vaubaehn
Copy link

I hope, @ascheibal reads here. In most cases we don't get any reply from him.

@jetwes
Copy link

jetwes commented Jan 24, 2022

I have confirmation from my contact at T-Systems. The issue is known and is under investigation

@ascheibal
Copy link

I forwarded the issue to the operations team.
@vaubaehn: thanks for blaming me. API Partners should have the necessary contacts to address urgent production issues. As you mentioned, I'm probably the wrong person to address those.

@vaubaehn
Copy link

I forwarded the issue to the operations team. @vaubaehn: thanks for blaming me. API Partners should have the necessary contacts to address urgent production issues. As you mentioned, I'm probably the wrong person to address those.

@ascheibal
I'm sorry. But from my experiences in the past, it looked like that serious/important issues got rather ignored. Maybe we can change this in the future?

@novoelgy
Copy link

Dear All, I am sorry for the trouble, ths isuse should be fixed, please check again.

@jetwes
Copy link

jetwes commented Jan 24, 2022

Looking good! Thank you! Now i have to take care on my backlog. 1500 quicktests are waiting...

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Jan 24, 2022

@brkoglu & @r0bs

Can you confirm the fix?

@brkoglu
Copy link

brkoglu commented Jan 24, 2022

Looks also good for me, thx!

@r0bs
Copy link
Author

r0bs commented Jan 24, 2022

@Ein-Tim: works on WRU now

thx! :)

@r0bs r0bs closed this as completed Jan 24, 2022
@vaubaehn
Copy link

@novoelgy
Thanks for fixing on behalf of the user community.
As one could think that server maintenance caused the issue, is there any chance that these works on PROD servers can be done during a night shift in the future?
See also corona-warn-app/cwa-app-android#968 (comment) for another sample incident.

@dsarkar
Copy link
Member

dsarkar commented Jan 24, 2022

Internal Tracking ID: EXPOSUREAPP-11006

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

9 participants