Client doesn't show any actionable error when API access is borked or unavailable and exits without notice (also, api.transifex.com is using the wrong TLS cert and any API access is currently broken at the transport layer)

[Swyter]

I was trying to do a normal translation pull, but my scripts acted weird because tx quits immediately. Thinking that something must have changed server-side, I updated the client binary.

Getting things like these:

tx config
tx ERROR: HTTPSConnectionPool(host='api.transifex.com', port=443): Max retries exceeded with url: /auth_check/ (Caused by SSLError(SSLCertVerificationError("hostname 'api.transifex.com' doesn't match '*.svc.transifex.net'")))

Until I arrived to https://status.transifex.com/ I wasn't aware of the scheduled maintenance, as the docs were working correctly.

Would be great to know about it off the bat. Maybe replacing the API endpoint by a dummy one with a specific error that can be printed by the client, or something.

[adimitrokalis]

I wanted to thank you for your feedback. I have informed our product team about your request. They will be evaluating your feedback. Once I have an update, I will let you know. However please keep in mind that such decisions may take some time. So I thank you for your patience in advance.

[mikaelkristiansson]

@Swyter I also had the problem when installing the client in CI (travis), so I had to add requests[security] for it to work:
sudo pip install --upgrade transifex-client requests[security]

maybe this will fix your problem as well?