Can't access Dashboard for fauna-dev

Hi, I’m trying to follow Fauna Dev :: Fauna Documentation, I ran the following command:

docker run -d --name faunadb -p 8443:8443 -p 8084:8084 \
  -v /Users/aprilmintacpineda/docker-volumes/faunadb:/var/lib/faunadb \
  -v /Users/aprilmintacpineda/docker-volumes/faunadb:/var/log/faunadb \
  fauna/faunadb

and got the following logs

***********************************************************************************

** jamm will use sun.misc.Unsafe to compute the size of objects on heap.

** This is not safe and results in wrong assumptions of the free/occupied Java

** heap and potentially in OOMs. The implementation performs arithmetics on the

**  "cookies" returned by Unsafe.objectFieldOffset(), althought the Javadoc says:

** "Do not expect to perform any sort of arithmetic on this offset; 

** it is just a cookie which is passed to the unsafe heap memory accessors."

** The implementation does not always consider Java object layouts in under

** all circumstances for all JVMs.

**

** Solutions:

** - Use a JDK/JVM with JEP-8249196

** - Load jamm as an agent into the JVM

***********************************************************************************

FaunaDB Enterprise Edition 22.04.00-8fad92d

===========================================

Starting...

Loaded configuration from /etc/faunadb.yml...

Trace sampling enabled without exporters?

Feature Flags disabled.

Data path: /var/lib/faunadb

Temp path: /var/lib/faunadb/tmp

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Identified as cd4385f9-07d2-4056-abb8-dfc1f4aaa4be at 172.17.0.2.

Snapshot path: /var/lib/faunadb/snapshots

Admin endpoint: 127.0.0.1:8444

Network Host ID: 172.17.0.2

Cluster name: fauna

Replica name: NoDC

API endpoint: 0.0.0.0:8443

API(plain) endpoint: 0.0.0.0:8445

FaunaDB is shutting down after 0 seconds.

Shutdown complete.

***********************************************************************************

** jamm will use sun.misc.Unsafe to compute the size of objects on heap.

** This is not safe and results in wrong assumptions of the free/occupied Java

** heap and potentially in OOMs. The implementation performs arithmetics on the

**  "cookies" returned by Unsafe.objectFieldOffset(), althought the Javadoc says:

** "Do not expect to perform any sort of arithmetic on this offset; 

** it is just a cookie which is passed to the unsafe heap memory accessors."

** The implementation does not always consider Java object layouts in under

** all circumstances for all JVMs.

**

** Solutions:

** - Use a JDK/JVM with JEP-8249196

** - Load jamm as an agent into the JVM

***********************************************************************************

FaunaDB Enterprise Edition 22.04.00-8fad92d

===========================================

Starting...

Loaded configuration from /etc/faunadb.yml...

Trace sampling enabled without exporters?

Feature Flags disabled.

Data path: /var/lib/faunadb

Temp path: /var/lib/faunadb/tmp

WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.

WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.



================================================================================

New fauna version available 5.0.0-beta -> 1.5.3-SNAPSHOT

Changelog: https://github.com/fauna/faunadb-jvm/blob/main/CHANGELOG.txt

================================================================================

HTTP Server started at port 8084.

FaunaDB is ready.

FaunaDB is ready.

WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.

WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.



================================================================================

New fauna version available 5.0.0-beta -> 1.5.3-SNAPSHOT

Changelog: https://github.com/fauna/faunadb-jvm/blob/main/CHANGELOG.txt

================================================================================

HTTP Server started at port 8084.

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Identified as cd4385f9-07d2-4056-abb8-dfc1f4aaa4be at 172.17.0.2.

Snapshot path: /var/lib/faunadb/snapshots

Admin endpoint: 127.0.0.1:8444

Network Host ID: 172.17.0.2

Cluster name: fauna

Replica name: NoDC

FaunaDB is ready.

API endpoint: 0.0.0.0:8443

API(plain) endpoint: 0.0.0.0:8445

FaunaDB is ready.

But I can’t seem to be able to access http://localhost:8084/graphql, it will say This site can’t be reached, the only port I can access is http://localhost:8443/ which is asking me for a login credential, I entered my fauna login credentials but it did not work.

Taking issues in reverse order, Fauna Dev does not contain a Dashboard instance. Navigating to http://localhost:8443/ wont be useful; the sign in is looking for Basic auth, and the default secret is secret (there’s no connection to accounts on dashboard.fauna.com).

I’m running the same Fauna Dev image, although I don’t mount local folders for persistent storage, and the GraphQL API fields queries and allows me to import a schema.

Maybe shut down the container and try starting it again?

You can check if the port is open with:

$ netstat -ant | grep 8084
tcp46      0      0  *.8084                 *.*                    LISTEN 

If you get no result, the port is not open. At that point, you’d want to investigate your Docker Desktop settings, or perhaps firewall settings (to see if the OS allows that port to talk).

Ahhh I see, do you know if there’s any viewer that I can use since it does not have a dashboard but a viewer will be useful, like MySQL workbench for mysql for example

You could try the standalone GraphQL Playground (a version of which is integrated into the Fauna Dashboard):

I mean for the FQL side, some of my projects do not use GraphQL.

We don’t provide a point-and-click viewer, aside from the Dashboard, so I don’t have any great suggestions for you.

Personally, I use fauna-shell for all of my exploratory querying. I keep an editor window open with all of the queries that I need to repeat fairly frequently, and then copy+paste those into fauna-shell as needed.