DeepL translation stops working #744
Description
For the past several months, I have been getting the following response when I try to use DeepL for translation:
DeepL: Response status code does not indicate success: 403 (Forbidden)
I have verified that my API key is valid and active. I can make translation requests using Postman using the same credentials and it works properly.
I was able to make this work by uninstalling and reinstalling ResX Manager, but it only worked until the next time I opened a solution and tried to translate.
It's unclear to me how to reproduce this bug, because it works until it doesn't.
The expected behavior is for translation using DeepL to produce results.