Cloud Trial Account not able to create cloud trial instance

Stardog Cloud
1

You must wait until your instance is cleaned up

Can you please help fix this error?

2

When you canceled your Stardog Cloud free instance, it went into an inactive state, but it had not yet been deleted from your account. I have removed it from your account, so that you can now allocate another.

Regards,

Paul Place

3

Thank you Paul. I'm able to create one now.

After creating I get an error - "There is an error with your connection, please check here to check diagnostics page.->"

4

Please post the info from the diagnostic page, either a screen shot or the text you get when you click the "Copy to Clipboard" button.

5

Your connection to Stardog is not valid, please ask an administrator to verify your username has access.

Test authorization header received
Test custom header received
Connection ID: 55c0bf7a-7f09-440c-8d99-30e961a358eb
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36
Response Time: 123 ms
Stardog Portal: Authenticated
Email Verified
Service: https://sd-cfa1b0be.stardog.cloud:5820 Network Error
Server: https://sd-cfa1b0be.stardog.cloud:5820 Unauthorized
Identifier Value
Username manjunath.venkobarao@merck.com
Provider auth0
OAuth Subject auth0|6410902cc9d8b3d9cc74b630
Header Value
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Host: cloud.stardog.com
Referer: Stardog Cloud
Sec-Ch-Ua: "Google Chrome";v="111", "Not(A:Brand";v="8", "Chromium";v="111"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "Windows"
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-origin
X-Amzn-Trace-Id: Root=1-6410d333-2e12e4255e92bba01773a75a
X-Forwarded-For: 155.91.28.246
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Request-Started-At: 1678824243339

6

This is most likely due to the fact that the URL to your Stardog Cloud Free instance has a non-standard top-level DNS name (.cloud in this case) or is accessing SSL on port 5820 instead of the standard SSL port (443).

We have seen this issue with other users who access a Stardog Cloud instance from a corporate network, where firewall rules are sometimes overly restrictive.

Please try logging in to the Stardog Cloud portal (https://cloud.stardog.com) from a different network, and see if you are able to connect to your instance. In this case, "different network" means from a home network, or from a different VPN, etc.

7

Thanks that resolved the issue now.