Vercel with AWS EC2 Elastic IP #6858
Replies: 2 comments 2 replies
-
Hi, I have managed to get it to work. Will proceed to close the discussion. |
Beta Was this translation helpful? Give feedback.
2 replies
-
This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Hello everyone,
I have a domain with Vercel i.e. domain.dev which serves my frontend. The project settings is linked to the frontend repository.
I have a separate backend server which is in NodeJS and the instance is running in AWS EC2. I am able to access the address and receive the following response:
I want to link the NodeJS server as a subdomain i.e. api.domain.dev, and have done the following:
(added A record with the IP pointing to the Elastic IP of the EC2 Instance).
However, when I tried to navigate to the page i.e. api.domain.dev, I encountered "The site can't be reached, api.domain.dev refused to connect". Removing the sub domain i.e. domain.dev shows that the frontend is still up and running.
I am unsure of how I can proceed from here, do I just have to wait it out for the DNS to be configured?
Thanks in advanced and any advice would be greatly appreciated.
Example
No response
Steps to Reproduce
Beta Was this translation helpful? Give feedback.
All reactions