Skip to content

SSL Errors #5

@mwishoff

Description

@mwishoff

Hey, so I started trying to use the library and was encountering a few SSL errors.

lib=4.0.0
OpenSSL v1.1.1c
Tried with python 3.6.4, and python 3.7.4

The first error I was getting was:
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:777)

Without updating my code or changing anything it is now displaying a different SSl error:
self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1076)

I've tried two ways, both return the same SSL Wrong Version Number.

First:
lib.cfg['token'] = 'MY_TOKEN'
HaloAPI = lib.halo.infinite['@0.2.0']
result = HaloAPI.stats.matches.list(gamertag='citizen kwho')
pprint(result)

Second:
url = 'https://halo.api.stdlib.com/[email protected]/stats/matches/retrieve/'
params = {
'id': '26829e9a-7fab-4c2b-ac28-a62360e55946',
'Content-Type': 'application/json'
}
headers = {
'Authorization': f'Bearer {dev_token}'
}
response = requests.get(url, params=params, headers=headers, verify=False)
pprint(response.json()

I then tried to see if the URL would resolve in my browser expecting a 401 error since I didn't pass my token and got an SSL error there as well. I can't tell exactly if this error is with the acode python bindings, or more specifically with the halo.api.stdlib API itself. Any additional input would be appreciated.

SSL_Error

Update:
After additional poking and prodding, I cleared my cache and was able to get a 200 response using the gateway method using requests. But the Acode lib-python library still gives me a SSL wrong version error.

It seems to have only worked one time though, and is back to providing the SSL wrong version error again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions