Cache and admin right for Stardog Studio (docker version)


We have stardog 8.1.1 and have a mysterious problem. We use Stardog Studio to connect to Stardog. It seems to have a connection problem.

Let me explain:
I connect with my admin account
I log out with my admin account
I can login in with any username and password (even non-existent) and I inherit the admin rights of my admin account, even if the account does not exist, and has no admin rights.

If I clear my cache and try to log in again with the fake non-existent account, no login as expected.

Do you have any idea what is causing this problem?

Thank you very much.

Hello, were you using Studio from or is it a local installation of Studio or


I am using Studio installed on Azure VM Linux Ubuntu with Docker. Not the cloud version of Stardog.

This is a known issue in dockerized editions of Studio. If you're able to, we'd recommend using the cloud version at From there you can also connect to your local Stardog server.

We do not want to use stardog Cloud, is it possible to install Stardog Studio without using Docker (
is the solution to the problem?

Thank you Paul

I am running Stardog in a vm running on my desktop and accessible from - so short answer is yes, longer answer is that you need to enable CORS for the browser and stardog studio. Basically, you install Stardog manually into a Linux VM, then add that stardog instance to studio. (You can log into and add a "local" instance instance to studio.)

Paul, Shane,
Thank you for your answer.

If I link my stardog VM server to my stardog cloud account, does my data transit through Stardog Cloud? This is my concern about using stardog cloud.

No, the communications from Stardog Applications to a Stardog Server go from your browser to the server, they are not routed via Cloud.

If you consider the case of a localhost based server, there's no way our Cloud servers can access that URL, that could only happen if the calls are from your browser to your localhost.

Free free to check this in your network tab in your browser, you can see this for yourself. The applications do talk to the server, for example, to get your list of connections, but queries, data and the like stay between your browser and your server.