Currently I'm getting Started with Stardog Cloud. My Stardog Free Server (explorer and studio) is not responding. See information below. Any suggestions?
It looks like you are trying to create a connection to a Stardog instance, but the endpoint you entered is https://cloud.stardog.com/ which is the portal where you log in to the Stardog Cloud portal.
After you log in to the portal, click the "Get a Stardog Cloud instance" button. From there, you can allocate a Free instance or purchase an Essentials instance. Once the Stardog instance is allocated, we automatically create a connection to it for you.
What was the sequence of steps that got you to this point? It looks like you were able to allocate a Stardog Free instance (two actually, using two different accounts). Did you get the "Taking too long" message waiting for the Free instance to be created or did you get that when you tried to connect to it?
If you are able to successfully log in to the Stardog Cloud portal, but then redirecting to the instance takes too long, try running the diagnostic page (Stardog Cloud)
This happens when creating it... So I tried to create a new one with another account, but still not working. FYI, I created a second account as for the first one i received an error when tryin to create a new instance.
Test authorization header received
Test custom header received
Connection ID: 86830d0e-ce8c-42da-8f37-e78f7306642b
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.81 Safari/537.36 Edg/104.0.1293.54
Response Time: 208 ms
Stardog Portal: Authenticated
Email Verified
Identifier Value
Header Value
Accept-Encoding: gzip, deflate, br
Accept-Language: nl,en;q=0.9,en-GB;q=0.8,en-US;q=0.7
Host: cloud.stardog.com
Referer: Stardog Cloud
Sec-Ch-Ua: "Chromium";v="104", " Not A;Brand";v="99", "Microsoft Edge";v="104"
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-62fbb14c-1d5bee9612e4322542162539
X-Forwarded-For: 188.118.8.124
X-Forwarded-Port: 443
X-Forwarded-Proto: https
X-Request-Started-At: 1660662092156
The second account you used still has an active Free instance associated with it. If you log out of the Stardog Cloud portal and then log back in, do you see the instance in your list of connections? What happens when go to the diagnostic page (Stardog Cloud)? If the diagnostics are all green, try going back to the login page and click on the connection to your Free instance.
Note that we have seen cases where redirecting from the login page at https://cloud.stardog.com to the instance (an address of the form https://sd-a1234567.stardog.cloud:5820) is blocked by corporate firewalls. If you are currently accessing Stardog Cloud from your corporate network, are you able to try accessing it from a different network (outside the corporate VPN if you are currently in one, inside a different VPN, from a non-corporate network)?
We have seen this with other users, where they can access their Stardog Cloud instance from some networks but not others. The failed access occurs when the user is on a corporate network with restrictive firewall rules.
For these users, logging in to the Stardog Cloud portal (https://cloud.stardog.com/) works just fine, but then when the user redirects to the instance (with a name like https://sd-12345678.stardog.cloud:5820), access is blocked. We have tried making the instance available on the standard HTTPS port (443 instead of 5820), but that has not fixed the problem.
Your options at this point are to work with your company's network-management team to allow access to hosts with a domain name ending in "stardog.cloud", or to access your Stardog Cloud Free instance from a network that does not block access.
