We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on Vesta 2.0 and expect to release it by the end of 2024. Read more about it: https://vestacp.com/docs/vesta-2-development
SSL IP to Domain - Problem
SSL IP to Domain - Problem
Hey guys,
So here's my problem.
viewtopic.php?f=20&t=4336 (I tried the solution in this as well and it didn't work, Did the same thing as setting the server_name)
I set server_name to my domain and everything, I set the DNS record for server1.mydomain.net and server1.mydomain.net loads a unable to connect error, Which is understandable. (note, mydomain.net isn't my domain, mydomain is the filler)
However, I am trying to force it to load on my domain and i can't get it to work.
If i visit the IP of my server it redirects to https://www.server1.mydomain.net:80 except that doesn't work, It loads a server not found page. If i remove www. and i change 80 to 8083 then VestaCP Login is shown.
How do i make it so that if someone tries to open the server IP then it redirects to the proper url? ( https://server1.mydomain.net:8083)
My Nginx Conf (changed my domain and removed IP):
Thanks! :)
So here's my problem.
viewtopic.php?f=20&t=4336 (I tried the solution in this as well and it didn't work, Did the same thing as setting the server_name)
I set server_name to my domain and everything, I set the DNS record for server1.mydomain.net and server1.mydomain.net loads a unable to connect error, Which is understandable. (note, mydomain.net isn't my domain, mydomain is the filler)
However, I am trying to force it to load on my domain and i can't get it to work.
If i visit the IP of my server it redirects to https://www.server1.mydomain.net:80 except that doesn't work, It loads a server not found page. If i remove www. and i change 80 to 8083 then VestaCP Login is shown.
How do i make it so that if someone tries to open the server IP then it redirects to the proper url? ( https://server1.mydomain.net:8083)
My Nginx Conf (changed my domain and removed IP):
Code: Select all
server {
listen ***.**.**.***:80 default;
server_name server1.mydomain.net;
#access_log /var/log/nginx/***.**.**.***.log main;
location / {
proxy_pass http://***.**.**.***:8080;
}
}
Re: SSL IP to Domain - Problem
https://www.server1.mydomain.net:80
why you use port? you already have https == 443 port in url
why you use port? you already have https == 443 port in url
Re: SSL IP to Domain - Problem
I don't have a choice. If i set the server_name it does that automatically...skurudo wrote:https://www.server1.mydomain.net:80
why you use port? you already have https == 443 port in url
VestaCP login works off of port 8083 and then the server automatically adds www. in the url which doesn't work.
I need to know how to remove the www. from being added and make it load 8083 instead of 80 at the end so it actually provides the VestaCP login..
I haven't touched VestaCP in terms of this other than what i specified so it's default with Vesta.
EDIT:
and now if i set the server_name and try to visit the IP it doesn't redirect either.