Nginx conf - templates for Backdrop CMS - Drupal

Community Support Web
21

We just have a quite different point of view about this case, which you can read out from our information post you’ll find here: GitHub - hestiacp/hestiacp: Hestia Control Panel | A lightweight and powerful control panel for the modern web.

For the redirect you could also basicly use a alias in the current hosting of your new domain, then check in the nginx config the http_host value and rewrite it, if it isnt the new domain:

if ($http_host = olddomain.tld) {
  rewrite  (.*)  https://www.newdomain.tld$1;
}
22

well, just to contribute with my profile, personally I used to run lamp stack with no interface on vps for several years… then, when secure https connection became mandatory (to not get that ugly “not secure site” on chrome, and I found out the benefits in performances on using nginx I switched to Vesta, for saving myself from hassles (nginx and let’s encrypt out of the box). And now to hestia, since Vesta looks kinda outdated. Also, I always used cheap unmanaged vps services (no cpanel, no plesk), with maybe 1 gb ram…

23

Hi very interesting.
At the moment i have set up second hestiacp locally even with dynamic ip for my home automation and for other testing porposes.
this works very well.
but for some software i neet to have one domain and different ports for different functions"websites"

for example

https://mylocalserver.com

i can redirect with proxypass

    location / {
	proxy_pass http://192.168.1.100:8081;
}

this works for
https://mylocalserver.com and redirects to 8081

but i have second function on http://192.168.1.100:8082

but when i enter https://mylocalserver.com:8082 the port is not given through because of my template…
does someone have a hint what i can do in this siutation? especially when i use this dynamic nginx template file from hestiacp which generates the appropriate nginx.conf when selected in hestia admin?