ESI Access to Singularity datasource timing out

Hi there,

I am developing an Industralist app and need to get access to the Singularity test server ESI apis. Since some days ago I ever get a “error”: “No reply within 10 seconds” for most of the calls, being them done form my app or from the swagger interface at https://esi.tech.ccp.is/ui/?datasource=singularity.

This is added to the most common error that most of the scope entries are not defined and I have to play to success/error until I found the set of scopes valid for a session test.

Is there any problem on the ESI for Singularity server? It is expected correct behavior that most of the scopes are no defined on the Singularity server ( {“error”:“invalid_scope”,“error_description”:“The requested scopes either don’t exist, or are not valid for this client”} )?

Kind regards.
Adam Antinoo

Do make sure you are using a Singularity dev app for your testing.

https://developers.testeveonline.com/

Also the login url for your sso button link is different. https://sisilogin.testeveonline.com.

I’ll bring this up in #esi ch on slack.

EDIT:

@CCP_SnowedIn is aware. The no reply error should be fixed tomorrow or so. the /ui/ swagger interface will updated to include new scopes soonish as well.

Thank you Blacksmoke16. Yes I have checked that I have properly configured the ESI authorization flow. I have not failures on connecting to the server and making the ESI requests but in getting proper responses. Most of the requests fail after the 10 seconds timeout with no answer so I can not perform any of my tests because most of the calls just timeout.

The same is happening when I make the same test request using the ESI swagger site configured for Singularity. Most of the times I get the error reporting no request in 10 seconds.

This was working perfectly last week when I reconfigured my app to use Singularity. I got access to the assets, the jobs, contracts, pilot public information and some more other entry points. Today, using the same application I just receive exceptions because okhttp exceptions.

java.lang.IllegalStateException: closed
at okhttp3.internal.http1.Http1Codec$FixedLengthSource.read(Http1Codec.java:381)
at okio.RealBufferedSource.readAll(RealBufferedSource.java:163)
Kind regards.

Yea check my edit, CCP’s aware and it’ll be fixed soon.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.