Skip to content

Empty dashdoard  #1460

Closed
Closed

Description

@marad747

my dashboard empty(( http://prntscr.com/qu37ln Help
i used this tutorial https://www.youtube.com/watch?v=4OOnFyXrRvI

Activity

  1. bernardohmr commented on Feb 4, 2020

    @bernardohmr

    Hello, I think I have the same issue (check images below).

    The network requests all respond with code 200. But the render breakes.

    parse-dashboard: 2.0.5
    parse-server: 3.9.0
    express: 4.17.1

    image

    image

  2. davimacedo commented on Feb 11, 2020

    @davimacedo
    Member

    Could you guys please share your package.json and config files?

  3. Meleuo commented on Mar 3, 2020

    @Meleuo

    hello
    I had the same problem
    This is my dashboard profile
    image

  4. davimacedo commented on Mar 4, 2020

    @davimacedo
    Member

    can you please also share your parse dashboard package.json file?

  5. edson-gaspar commented on Mar 23, 2020

    @edson-gaspar

    Hello,
    I solved this issue on my Mac (safari & firefox) cleaning ALL related data stored on my browsers related to domain hosted parse dashboard (cookies, local storage, session storage, cache, etc).

    On Safari you can go to Safari Menu -> Preferences -> Privacy -> Manage site data, them search for domain or localhost if is your case, select the desired domain and click on Remove All, after that, check all data and cache to be cleaned if necessary.

    I think this could be related to version and password authentication policy that was changed on parse server or something like that.

    I hope this help you.

  6. m4ary commented on Mar 29, 2020

    @m4ary

    i have the same problem

  7. stale commented on May 13, 2020

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  8. mtrezza commented on May 18, 2020

    @mtrezza
    Member

    I was able to reproduce (something like) this on AWS Elastic Beanstalk. The dashboard loads but the page is blank:

       <!DOCTYPE html>
        <head>
          <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" />
          <base href="/"/>
          <script>
            PARSE_DASHBOARD_PATH = "/";
          </script>
        </head>
        <html>
          <title>Parse Dashboard</title>
          <body>
            <div id="login_mount"></div>
            
            <script id="csrf" type="application/json">"..."</script>
            <script src="/bundles/login.bundle.js"></script>
          </body>
        </html>
    
  9. removed
    state:wont-fixWon’t be fixed with a clearly stated reason
    on May 18, 2020
  10. mtrezza commented on May 18, 2020

    @mtrezza
    Member

    The reason why Parse Dashboard is showing a blank page when deploying to AWS Elastic Beanstalk is that these files are in .gitignore:

    bundles/
    Parse-Dashboard/public/bundles/
    Parse-Dashboard/parse-dashboard-config.json
    

    For AWS EB CLI this means that the files are not deployed as part of the application. The solution is to either remove the files from .gitignore or add a .ebignore file so that the AWS CLI ignores the .gitignore and deploys all files.

    From the AWS docs:

    If .ebignore isn't present, but .gitignore is, the EB CLI ignores files specified in .gitignore. If .ebignore is present, the EB CLI doesn't read .gitignore.

    When .ebignore is present, the EB CLI doesn't use git commands to create your source bundle. This means that EB CLI ignores files specified in .ebignore, and includes all other files. In particular, it includes uncommitted source files.

    That means that the repository is not out-of-the-box AWS EB CLI deployment compatible. Maybe we should remove the files from .gitignore?

  11. stale commented on Jul 3, 2020

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  12. added
    state:wont-fixWon’t be fixed with a clearly stated reason
    on Jul 3, 2020
  13. PraveenMarapelly commented on May 15, 2021

    @PraveenMarapelly

    I had the same issue, try doing the following steps
    In chrome
    open Settings --> Go to Site settings -->Click on Insecure Content --> Click on "Add" button corresponding to "Allow" copy and paste your Public IPv4 DNS in the address box
    it worked for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    state:wont-fixWon’t be fixed with a clearly stated reason

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions