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
I'm trying to run my sandstorm host on an actual server on the internet; so I want to change "localhost" to my domain name, and 3000 to 80.
I've already discovered that I "meteor --port 80" won't work unless I first do these:
sudo setcap 'cap_net_bind_service=+ep' ~/.meteor/tools/latest/mongodb/bin/mongod
sudo setcap 'cap_net_bind_service=+ep' ~/.meteor/tools/latest/bin/node
However:
When I load the new page in the browser on port 80, it doesn't seem to work. Chrome's dev console doesn't report any failed network requests; but something must be wrong with the websocket that gets created.
Also, "localhost:3000" seems to be hardcoded somewhere as the redirect url for Google oauth.
The text was updated successfully, but these errors were encountered:
The recommended solution here is to stick an nginx reverse proxy in front of the node server. nginx is all set up to open port 80 before dropping privs -- node doesn't seem very good at this. Also, with nginx you can support SSL. I need to write some docs on this with example configs.
BTW, note that running the server through the "meteor" command is intended for local development. When deploying something more production-y, you should use "meteor bundle" to create a tarball, unpack that tarball somewhere, and read the readme inside.
That said, that doesn't necessarily solve your problems. And, actually, running in dev mode probably makes sense if you expect to tweak the code at all.
I'm trying to run my sandstorm host on an actual server on the internet; so I want to change "localhost" to my domain name, and 3000 to 80.
I've already discovered that I "meteor --port 80" won't work unless I first do these:
sudo setcap 'cap_net_bind_service=+ep' ~/.meteor/tools/latest/mongodb/bin/mongod
sudo setcap 'cap_net_bind_service=+ep' ~/.meteor/tools/latest/bin/node
However:
The text was updated successfully, but these errors were encountered: