You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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?
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.
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
Activity
bernardohmr commentedon Feb 4, 2020
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
davimacedo commentedon Feb 11, 2020
Could you guys please share your package.json and config files?
Meleuo commentedon Mar 3, 2020
hello

I had the same problem
This is my dashboard profile
davimacedo commentedon Mar 4, 2020
can you please also share your parse dashboard package.json file?
edson-gaspar commentedon Mar 23, 2020
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 commentedon Mar 29, 2020
i have the same problem
stale commentedon 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.
mtrezza commentedon May 18, 2020
I was able to reproduce (something like) this on AWS Elastic Beanstalk. The dashboard loads but the page is blank:
mtrezza commentedon May 18, 2020
The reason why Parse Dashboard is showing a blank page when deploying to AWS Elastic Beanstalk is that these files are in
.gitignore: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
.gitignoreor add a.ebignorefile so that the AWS CLI ignores the.gitignoreand deploys all files.From the AWS docs:
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 commentedon 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.
PraveenMarapelly commentedon May 15, 2021
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