Repository navigation
Wrong Port #64
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
Description
Activity
Parse-server itself is not actually a server, but middleware that you attach to your actual server. And as middleware, Parse-server doesn't care what port you use–the Parse-server source code doesn't even ever look at the port. The example server shown in the Parse-server README does indeed use a different default port, but like our sample, the Parse-server sample also prefers
process.env.PORTover the default, so if you have need to use a particular port, just set thePORTenvironment variable to a port of your choosing and you should be good to go.- addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Apr 6, 2020 - added a commit that references this issue
on Oct 26, 2022 - added a commit that references this issue
on Nov 3, 2022 - added a commit that references this issue
on Nov 8, 2022 - added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Nov 18, 2022 - added 2 commits that reference this issue
on Nov 18, 2022 - added a commit that references this issue
on Jan 18, 2023 - added a commit that references this issue
on Jan 18, 2023 - added a commit that references this issue
on Jan 25, 2023 - added a commit that references this issue
on Feb 16, 2023
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
Hi Google team,
the implementation of Parse Server:
app.listen(process.env.PORT || 8080, '0.0.0.0', function()
will lead to sporadic nginx 502 gateway errors. The official parse-server repo uses a different port.
Thanks.