Answer the question
In order to leave comments, you need to log in
Difficulties with *.site.com and 443 redirects. How to fix?
Gentlemen, please tell me about nginx.
the config is formatted like this: https://pastebin.com/uWvg0LZv
and there is a difficulty: it doesn’t want to redirect to 443 and
when
test.site.by is requested, it
gives
https://%2A.site.by/
which, when decoding, I get
https: //*.site.by/
I don't understand where the plug is
Answer the question
In order to leave comments, you need to log in
my God and simply to register a host not destiny?
return 301 https://$host$request_uri ;
that's why you invent a bicycle
3 human configs for each domain separate beautiful convenient fashionable youth
No need to invent a bicycle, and then heroically solve it.
In short, do this
proxy_pass https://127.0.0.1:4443 ;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header HTTPS YES;
And most importantly, in 99% of manas on the Internet there is an error and you make it like idiots, then you get
problems with refery
http ->http
https -> https
without any crutches in the form of 443->80
If debian then proxmox.
I don’t know how it is there in the cluster, but how simple the virtualization management system works just fine.
I worked with about 20 proxmox installations, there are no special complaints. I myself keep several of my servers with proxmox and also just rejoice (for a year and a half, there didn’t seem to be a single problem from proxmox). The guys I knew raised a cluster with live migration on the third version and said that everything was already in production there and it works for them so far, which is very good.
If you already have MS and Vmware licenses, then choose between them.
There was a real experience of remote implementation to Krasnodar (full transfer from XenServer to Vmware with VDI deployment) - the project is many times larger than yours.
All parameters of the virtualization system (ups, raid, smart, temperature, hypervisor load, VM health) need to be monitored with email notificationEverything is realizable.
Downtime allowed for guest VMsI propose to design systems immediately without such deplorable moods.
The main thing is the safety and recoverability of guest VMsusing the Vaaem solution is the best solution for reserving a Vmware / Hyper-V virtual infrastructure The
Good afternoon!
Look at virtualization from RedHat, it seems to me there is a lot of interesting things there. There is a commercial version (RHEV) for virtualization of servers and desktops (from your question it is not entirely clear what you want to virtualize), today it already works quite well.
You can also see a free analogue (on the basis of which a commercial distribution kit is then made, as I understand it): www.ovirt.org/Home Perhaps a free analogue will be enough for your tasks, you can implement it in a couple of days.
I hope the information will be useful to you.
I will support the previous speaker about Proxmox. However, not everything is so rosy with him. But in general, it does not cause much trouble (except for hanging backups somewhere once a month).
What to choose for independent implementation? Please share your real experience.
The Vmware vSphere Essentials Plus Kit license is just for three servers, what you need. If you are not going to renew your subscription to VmWAre, then as Proxmox advised above.
All parameters of the virtualization system (ups, raid, smart, temperature, hypervisor load, VM health) need to be monitored with email notification
The virtualization system must be able to gracefully shut down before the UPS is completely discharged
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question