• MD_PRD about 1 year ago

    MD_PRD geändert about 1 year ago
    Hi,

    Anybody else experiencing problems? Suddenly I recieve 502 as a response. I've changed nothing in my code.

    This URL in a webbrowser works fine:
    https://api.discogs.com/releases/400502

    When i drag the result of this call in Fiddler to the composer-tab and execute the call again, I receive a 502 result.

    Regards,
    Coen van Elst
  • vinyle-actu about 1 year ago

    Hi, impossible to connect with Oauth since this morning, unfortunately unable to fix the issue ... I haven't changed anything in my code, I'm lost ... There might be an issue with the https://api.discogs.com/oauth/request_token endpoint (which is working fine in the browser though).... Help please !
  • presidentcamacho about 1 year ago

    Same thing here. Java code that worked fine up to a couple of days ago now fails to connect: Remote host closed connection during handshake
  • Glassdub about 1 year ago

    Any update on this???
  • vinyle-actu about 1 year ago

    Back to normal here ...
  • MD_PRD about 1 year ago

    Same here, issue resolved!
  • MD_PRD about 1 year ago

    MD_PRD geändert about 1 year ago
    Well, I thought the issue had been resolved completely but there still seems to be an issues with getting album covers and artist pictures. Anybody else experiencing this issue?

    And a reaction of the Discogs team is appreciated ;-)

    Regards,
    Coen van Elst
  • Team 22

    eknudtson about 1 year ago

    eknudtson geändert about 1 year ago
    Hi,

    You should make sure your API client is capable of supporting TLS 1.2. We are deprecating the use of TLS 1.0 and TLS 1.1 (our CDN already has, this is likely why you're unable to retrieve images). We announced the TLS 1.2 requirement back when we switched the API to HTTPS only : https://www.discogs.com/forum/thread/347984#7033144
  • MD_PRD about 1 year ago

    MD_PRD geändert about 1 year ago
    Hi eknudtson,

    Thanx! I realised that my app was still using TLS 1.0. I've changed to TLS 1.2 and it's working like a charm.

    But then again; am I correct that I now experience a change which has been announced a year ago?

    Regards,
    Coen van Elst
  • Team 22

    eknudtson about 1 year ago

    MD_PRD
    Hi eknudtson,

    Thanx! I realised that my app was still using TLS 1.0. I've changed to TLS 1.2 and it's working like a charm.

    But then again; am I correct that I now experience a change which has been announced a year ago?

    Regards,
    Coen van Elst


    We waited on fully removing TLS 1.0 and 1.1, but as our CDN provider has now disabled the protocols we are moving on it too. Given that these protocols are deprecated in the latest PCI-DSS requirements, by next year most sites on the internet will require a client capable of TLS 1.2.

Anmelden Sie müssen angemeldet sein, um posten zu können.