Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Empty dashdoard #1460

Closed
marad747 opened this issue Jan 28, 2020 · 11 comments
Closed

Empty dashdoard #1460

marad747 opened this issue Jan 28, 2020 · 11 comments
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@marad747
Copy link

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

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

@davimacedo
Copy link
Member

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

@Meleuo
Copy link

Meleuo commented Mar 3, 2020

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

@davimacedo
Copy link
Member

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

@edson-gaspar
Copy link

edson-gaspar commented Mar 23, 2020 •
edited
Loading

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.

@m4ary
Copy link

m4ary commented Mar 29, 2020

i have the same problem

@stale
Copy link

stale bot commented May 13, 2020

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.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label May 13, 2020
@mtrezza
Copy link
Member

mtrezza commented May 18, 2020 •
edited
Loading

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>

@stale stale bot removed the state:wont-fix Won’t be fixed with a clearly stated reason label May 18, 2020
@mtrezza
Copy link
Member

mtrezza commented May 18, 2020 •
edited
Loading

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?

@stale
Copy link

stale bot commented Jul 3, 2020

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.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Jul 3, 2020
@stale stale bot closed this as completed Jul 11, 2020
@PraveenMarapelly
Copy link

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

@snyk-bot snyk-bot mentioned this issue May 24, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@edson-gaspar @davimacedo @mtrezza @marad747 @m4ary @Meleuo @bernardohmr @PraveenMarapelly