Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Heya,
Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.
The issue seems to happen because when you’re trying to proxy pass to route ‘/hello’, there’s a ‘return 404;’ defined for ‘/hello’ location in your Nginx configuration.
A way to solve your problem can be add a trailing slash after ‘/hello’ inside ‘proxy_pass’ like this:
- location /greet {
- proxy_pass http://localhost:4200/hello/;
- }
After this, you need to restart your nginx server. Some routes can be sensitive to trailing slashes and adding a slash can make a difference.
Also, it’s worth noting that with your current configuration, any visit to ‘http://localhost/hello’ directly will return a 404 as per your explicit configuration:
- location /hello {
- return 404;
- }
If you want to change this behavior, adjust the /hello location block accordingly.
Please check this link for more useful information regarding Nginx proxying.
Hope that this helps!