Unable to connect to my application securely in HTTPS
Hello everybody.
I currently host my app on a Windows VPS with Amazon. The app works great when I use it on the internet at the domain address that points to my IP address. However, the application is not secure because it is not in HTTPS. So for everything to be safe I have activated an SSL certificate which works well on my Windows server as you can see on the screenshot where we see that I can go to the login box without problem and we can see that the page is secure with the small padlock.
On the other hand, when I connect to one of my applications I receive this as a message (see screenshot below.)
And when I try to go to the page where I can connect directly to an application, I receive this as a message (see screenshot below).
Is this not working because my apps are running with their own server which is the Tomcat server which is installed on my Windows VPS and if that is the problem is there anyone who can tell me how run my applications that use a Tomcat server on a Windows VPS so that when you enter my applications they are in HTTPS.
Thanks for your help.
- 最新
- 投票最多
- 评论最多
It sounds like your using Lightsail, I would suggest you set up a load balancer in front of your application server and configure it to use a certificate (SSL). You then don't need to have SSL configured on your server. Here are the two articles that I think will help:
- https://lightsail.aws.amazon.com/ls/docs/en_us/articles/create-lightsail-load-balancer-and-attach-lightsail-instances
- https://lightsail.aws.amazon.com/ls/docs/en_us/articles/create-tls-ssl-certificate-and-attach-to-lightsail-load-balancer-https
Once you have this in place, your instance doesn't need to be accessible from the outside, which will make it more secure.
Hope this helps.
Your Java servlet is throwing an error and I would read that carefully (I'm not 100% familiar with what is behind this so I'm deliberately being vague) - but given that it is saying "domain parameter is not specified" you need to configure whatever that is. Perhaps the certificate name, hostname or something else does not match what it expects?
