Deploying react on ubuntu droplet
up vote
0
down vote
favorite
I've got a locally perfectly working react app on port 3000.
Finally bought a droplet, installed and configured nginx + ssl.
Everything 'normal' is working just fine.
When i'm deploying my react app, npm server starts, looks normal but...
mydomain.net, mydomain.net:3000 etc. is just not working (i see only my html file, no react rendering).
What i'm missing?
reactjs nginx
asked Nov 11 at 14:20
Wiktor W
1
add a comment |
up vote
0
down vote
favorite
I've got a locally perfectly working react app on port 3000.
Finally bought a droplet, installed and configured nginx + ssl.
Everything 'normal' is working just fine.
When i'm deploying my react app, npm server starts, looks normal but...
mydomain.net, mydomain.net:3000 etc. is just not working (i see only my html file, no react rendering).
What i'm missing?
reactjs nginx
asked Nov 11 at 14:20
Wiktor W
1
It's not possible to know from just what you've told us. Check the browser devtools for any errors or resources that failed to load. Maybe you have hardcodedlocalhostsomewhere? Typically you would use port 443 for ssl / https. To use it on port 3000 might require some changes in your configuration. A typical setup is to use nginx to serve the app on port 443, not port 3000. Do you use an app server such as express to render the react application, or is it just client side?
– Håken Lid
Nov 11 at 14:40
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've got a locally perfectly working react app on port 3000.
Finally bought a droplet, installed and configured nginx + ssl.
Everything 'normal' is working just fine.
When i'm deploying my react app, npm server starts, looks normal but...
mydomain.net, mydomain.net:3000 etc. is just not working (i see only my html file, no react rendering).
What i'm missing?
reactjs nginx
asked Nov 11 at 14:20
Wiktor W
1
I've got a locally perfectly working react app on port 3000.
Finally bought a droplet, installed and configured nginx + ssl.
Everything 'normal' is working just fine.
When i'm deploying my react app, npm server starts, looks normal but...
mydomain.net, mydomain.net:3000 etc. is just not working (i see only my html file, no react rendering).
What i'm missing?
reactjs nginx
reactjs nginx
asked Nov 11 at 14:20
Wiktor W
1
asked Nov 11 at 14:20
Wiktor W
1
asked Nov 11 at 14:20
Wiktor W
1
asked Nov 11 at 14:20
Wiktor W
1
asked Nov 11 at 14:20
Wiktor W
1
1
It's not possible to know from just what you've told us. Check the browser devtools for any errors or resources that failed to load. Maybe you have hardcodedlocalhostsomewhere? Typically you would use port 443 for ssl / https. To use it on port 3000 might require some changes in your configuration. A typical setup is to use nginx to serve the app on port 443, not port 3000. Do you use an app server such as express to render the react application, or is it just client side?
– Håken Lid
Nov 11 at 14:40
add a comment |
It's not possible to know from just what you've told us. Check the browser devtools for any errors or resources that failed to load. Maybe you have hardcodedlocalhostsomewhere? Typically you would use port 443 for ssl / https. To use it on port 3000 might require some changes in your configuration. A typical setup is to use nginx to serve the app on port 443, not port 3000. Do you use an app server such as express to render the react application, or is it just client side?
– Håken Lid
Nov 11 at 14:40
It's not possible to know from just what you've told us. Check the browser devtools for any errors or resources that failed to load. Maybe you have hardcoded
localhost somewhere? Typically you would use port 443 for ssl / https. To use it on port 3000 might require some changes in your configuration. A typical setup is to use nginx to serve the app on port 443, not port 3000. Do you use an app server such as express to render the react application, or is it just client side?– Håken Lid
Nov 11 at 14:40
It's not possible to know from just what you've told us. Check the browser devtools for any errors or resources that failed to load. Maybe you have hardcoded
localhost somewhere? Typically you would use port 443 for ssl / https. To use it on port 3000 might require some changes in your configuration. A typical setup is to use nginx to serve the app on port 443, not port 3000. Do you use an app server such as express to render the react application, or is it just client side?– Håken Lid
Nov 11 at 14:40
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Maybe to configure NGINX as a reverse proxy?
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
eg adding in NGINX configuration file:
location /
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
answered Nov 11 at 19:56
Boris Traljić
35428
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Maybe to configure NGINX as a reverse proxy?
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
eg adding in NGINX configuration file:
location /
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
answered Nov 11 at 19:56
Boris Traljić
35428
add a comment |
up vote
0
down vote
Maybe to configure NGINX as a reverse proxy?
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
eg adding in NGINX configuration file:
location /
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
answered Nov 11 at 19:56
Boris Traljić
35428
add a comment |
up vote
0
down vote
up vote
0
down vote
Maybe to configure NGINX as a reverse proxy?
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
eg adding in NGINX configuration file:
location /
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
answered Nov 11 at 19:56
Boris Traljić
35428
Maybe to configure NGINX as a reverse proxy?
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
eg adding in NGINX configuration file:
location /
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
answered Nov 11 at 19:56
Boris Traljić
35428
answered Nov 11 at 19:56
Boris Traljić
35428
answered Nov 11 at 19:56
Boris Traljić
35428
answered Nov 11 at 19:56
Boris Traljić
35428
35428
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53249634%2fdeploying-react-on-ubuntu-droplet%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It's not possible to know from just what you've told us. Check the browser devtools for any errors or resources that failed to load. Maybe you have hardcoded
localhostsomewhere? Typically you would use port 443 for ssl / https. To use it on port 3000 might require some changes in your configuration. A typical setup is to use nginx to serve the app on port 443, not port 3000. Do you use an app server such as express to render the react application, or is it just client side?– Håken Lid
Nov 11 at 14:40