Parse Dashboard 4.1.1 isn't accessible after migration to another VPS

[vzukanov]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

After migration to a new VPS, Parse Dashboard isn't accessible, even though Parse Server functions properly

Steps to reproduce

Create backup of MongoDB data on the old server using mongodump command.
Install Parse Server 4.10.7 and Parse Dashboard 4.1.1 on the new server.
Restore from backup on the new server using mongorestore command.
Perform all the required setup of the new server (DNS records, certs, etc.).
Launch Parse Server and Parse Dashboard.
Attempt to access Parse Server through API (works).
Attempt to open Parse Dashboard (doesn't work).

Actual Outcome

When trying to access Parse Dashboard through a web-browser, I see the initial animation, but then nothing is shown.

Expected Outcome

Login screen should be shown.

Environment

Dashboard

• Parse Dashboard version: 4.1.1
• Browser (Safari, Chrome, Firefox, Edge, etc.): Firefox, Edge

Server

• Parse Server version: 4.10.7
• Operating system: Ubuntu
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): DigitalOcean

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 3.6.8
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local (same host as Parse Server)

Additional info

This was far from the first time I migrated my server. All the configuration is stored in code, so the process is automated and shouldn't have much variation. In fact, the last time I migrated the server was during investigation of another problem in the context of Parse about a month ago. Surpisingly, this time the flow resulted in broken Dashboard.

I spent many hours on this issue because the old server (which I migrated from) had the same versions of Parse Server and Parse Dashboard installed, so I naturally assumed that the issue isn't related to versions. However, after checking zillion other factors, I decided to attempt going through the entire migration flow again, but using Parse Dashboard 4.1.0. To my great surpirse, Parse Dashboard became accessible. Then I upgraded the dashboard to version 4.1.1 and it remained functional.
Therefore, it looks like there is some problem with starting from 4.1.1 right away, but this issue doesn't happen if I upgrade to that version from 4.1.0.

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

I'm closing this as it does not seem to be a Parse Dashboard issue.

• For help with Parse Platform we recommend our community forum
• For coding questions we recommend Stack Overflow using the parse-platform tag
• For network and server questions we recommend ServerFault using the parse-server tag

Feel free to comment if you have any questions and we can re-open this issue.

[vzukanov]

I'm a bit confused. From what I explained in the ticket, this might be a real problem affecting the latest version of Parse Dashboard. Can you explain why you concluded that "it does not seem to be a Parse Dashboard issue"?

[mtrezza]

As I understand the issue happens due to a change in your environment. Please post in the forum for help with troubleshooting. If it is confirmed that it's an issue, we can reopen here.

[vzukanov]

As I wrote, I found a workaround for my situation, so I don't need help at this point. Just thought to report back in case this info will be helpful. If you still don't see a problem here, then, maybe, there is indeed none.

[mtrezza]

I don't see how anyone but yourself could investigate this. The issue description mentions custom migration scripts, DNS, cert set-ups, DB backup restores and environment / architecture changes. All these parameters are opaque to us.

The only suggestion I can give is that since you pinned the issue down to the version 4.1.1, you could revert the few commits between 4.1.0 and 4.1.1 one by one to see whether any of them causes the issue you experience. From there we could re-open this issue.

Alternatively, you could try to reproduce the issue with a clean, new install of Parse Dashboard so that is becomes reproducible for everyone. You'd need to rewrite your issue description and we could also re-open the issue.

[mtrezza]

@vzukanov Did you read through existing issues? Could #2112 be similar to your issue? If it is, then please let's continue the discussion there to avoid duplicate threads.