parse-community / parse-community/parse-dashboard

Server not reachable: server version too low

Open
#2,515 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug
Dominant language
JavaScript
Stars
3.8k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

New Issue Checklist
Issue Description

dashboard display: Server not reachable: server version too low

Steps to reproduce
app.use("/dashboard", dashboard);

server.start().then(function () {
    console.log("server start completed")
    app.use("/parse", server.app);
})
Actual Outcome
Node app is running on port: 1337
server start completed
WARNING, Unable to connect to 'http://localhost:1337/parse'. Cloud code and push notifications may be unavailable!

Expected Outcome
Node app is running on port: 1337
 server start completed
Environment

Dashboard

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

Server

  • Parse Server version: 6.4.0
  • Operating system: mac os 13.6.1
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 7.0
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local
Logs
8:57:40 AM - Starting compilation in watch mode...
[TS] 
[TS] 
[TS] 8:57:42 AM - Found 0 errors. Watching for file changes.
[TS] DATABASE_URI not specified, falling back to localhost.
[TS] databaseUri: mongodb://localhost:27017/dev
[TS] redisUri not specified, falling back to localhost.
[TS] redisUri: redis://localhost:6379
[TS] warn: DeprecationWarning: The Parse Server option 'allowExpiredAuthDataToken' default will change to 'false' in a future version.
[TS] warn: DeprecationWarning: The Parse Server option 'encodeParseObjectInCloudFunction' default will change to 'true' in a future version.
[TS] app: 2.538s
[TS] Node app is running on port: 1337
[TS] server start completed
[TS] 
[TS] WARNING, Unable to connect to 'http://localhost:1337/parse'. Cloud code and push notifications may be unavailable!
[TS] 


Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the warning with the shown dashboard mount and server.start() sequence, using Parse Dashboard 5.3.0 and Parse Server 6.4.0. Trace the dashboard's server-reachability check and compare its expected endpoint with the mounted /parse route; done means the local server is recognized without the version or connectivity warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mongodb
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.