Connect to Stardog with https

Hi there. We recently started running Stardog 5.3.4 with security on and we can connect with our Java app, and can connect using the web console (if I tell my browser to ignore the cert), but I can't get Stardog Studio to connect. If it matters, the address I'm using is https://localhost:5820. I even tried turning on the self-signed cert option. Studio just sits there and spins until it gives up with no errors. Any ideas?

Can you check if there's anything helpful in either the Stardog log file or the Studio log file? Studio logs are at ~/Library/Logs/Stardog\ Studio/log.log for MacOS and %USERPROFILE%\AppData\Roaming\Stardog Studio\log.log on Windows.

[2019-10-04 13:39:50.875] [error] Error: Request Aborted
    at c.on (file:///Applications/Stardog%20Studio.app/Contents/Resources/app.asar/renderer.e573364b8afc221b0489.js:1:614289)
    at CallbacksRegistry.apply (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/callbacks-registry.js:47:25)
    at handleMessage (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:285:21)
    at EventEmitter.ipcRenderer.on.args (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:275:7)
    at EventEmitter.emit (events.js:182:13)
[2019-10-04 13:39:50.886] [error] Request Aborted
[2019-10-04 13:39:54.097] [error] Error: net::ERR_EMPTY_RESPONSE
[2019-10-04 13:39:54.097] [error] net::ERR_EMPTY_RESPONSE
[2019-10-04 13:39:54.236] [error] Error: net::ERR_EMPTY_RESPONSE
[2019-10-04 13:39:54.236] [error] net::ERR_EMPTY_RESPONSE
[2019-10-04 13:40:04.279] [error] Error: net::ERR_EMPTY_RESPONSE
[2019-10-04 13:40:04.280] [error] net::ERR_EMPTY_RESPONSE
[2019-10-04 13:40:09.316] [error] Error: net::ERR_EMPTY_RESPONSE
[2019-10-04 13:40:09.316] [error] net::ERR_EMPTY_RESPONSE
[2019-10-04 13:41:15.158] [error] Error: Request Aborted
    at c.on (file:///Applications/Stardog%20Studio.app/Contents/Resources/app.asar/renderer.e573364b8afc221b0489.js:1:614289)
    at CallbacksRegistry.apply (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/callbacks-registry.js:47:25)
    at handleMessage (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:285:21)
    at EventEmitter.ipcRenderer.on.args (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:275:7)
    at EventEmitter.emit (events.js:182:13)
[2019-10-04 13:41:15.159] [error] Request Aborted
[2019-10-04 13:42:46.325] [error] Error: Request Aborted
    at c.on (file:///Applications/Stardog%20Studio.app/Contents/Resources/app.asar/renderer.e573364b8afc221b0489.js:1:614289)
    at CallbacksRegistry.apply (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/callbacks-registry.js:47:25)
    at handleMessage (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:285:21)
    at EventEmitter.ipcRenderer.on.args (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:275:7)
    at EventEmitter.emit (events.js:182:13)
[2019-10-04 13:42:46.326] [error] Request Aborted
[2019-10-04 13:56:17.151] [error] Error: Request Aborted
    at c.on (file:///Applications/Stardog%20Studio.app/Contents/Resources/app.asar/renderer.e573364b8afc221b0489.js:1:614289)
    at CallbacksRegistry.apply (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/callbacks-registry.js:47:25)
    at handleMessage (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:285:21)
    at EventEmitter.ipcRenderer.on.args (/Applications/Stardog Studio.app/Contents/Resources/electron.asar/renderer/api/remote.js:275:7)
    at EventEmitter.emit (events.js:182:13)
[2019-10-04 13:56:17.154] [error] Request Aborted

Sorry for the inconvenience here, and thanks for providing the log. The error messages shown there occur when Studio makes a request and receives no response for 60 seconds, so it seems that Studio is failing to get any response at all back from your endpoint (consistent with the "spins until it gives up" behavior you're seeing). Can you let us know what version of Studio you're using? (If you're on a version older than v1.12.0, it's possible that upgrading could help you.) Also, I assume you don't see any errors in your stardog.log file when attempting to connect with Studio? Are you using a proxy of any kind?

We'll be creating a ticket for this internally and investigating. In the meantime, any answers to the above questions could help us narrow things down.

Thanks,
Jason

Thanks, Jason. I'm using 1.12.0, no proxy, and I don't see any errors in stardog.log.