I have a load balancer(174.138.122.79) which is SSL enabled and wants to point to one of the droplet having a rest service (139.59.69.79) with nginx.
174.138.122.79--------------->139.59.69.79(with nginx for 80 to 8080 routing).
I can access the app directly on http://139.59.69.79 and it works fine, but not able to connect via load balancer(443->80 configured).
However, if i make the app run on port say 1134 and enable ufw for that port i can connect from load balancer(443-1134) too.
can you help me solve this?
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!
If I had to make a guess it maybe because you are opening an SSL connection which is encrypted and then trying to forward it to port 80, which isn’t encrypted by default.
That is perhaps why when you change to a non-default port like 1134 then it works without issue.
You may also want to double check to ensure there aren’t existing firewall rules that could be causing a conflict considering that port 80 is standard port.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.