How to Redirect from WWW to Non-WWW on NGINX. Works for Http to Https too! 

Good tip. THats a more "universal" way to do it. Where as the systemctl method doesn't work on every Unix OS.

Haha thanks.

ww program BP picture

Seconded. Though I'm pretty sure you can route *.example.com via an C-NAME record to your web app, and in Laravel use Route::domain() to detect and group together subdomain routes. laravel.com/docs/5.5/routing#route-group-sub-domain-routing

A detailed explanation would be better

Yes that is the basic premise of how you do it. One feature that sucks about Laravel is that you have to hardcode the domain. THis is what makes it confusing for most people. However I have heard rumors that this might be fixed in Laravel 5.6. (cross your fingers).

Sorry I was trying to show it best I could, but I didnt want to reveal all of my domains and their associated IP addresses. So what you need to do is make an A record that points to the same IP address or server that your Nginx server is on. So in my case, my primary domain is the non-www version. So in order for Nginx to route the www traffic to the non-www you need to make sure the traffic actually gets to the server first. If you don't set up an A record in your DNS then the person who types in your www domain will never reach the server for Nginx to do its magic, because the DNS won't know to pass the traffic off to your server (the user will get a generic browser generated error). Now some DNS providers (any respectable one) allow you to wildcard any subdomain (www is a subdomain) to the same server. That is an option too. I personally don't like wildcarded subdomains unless its a SAAS product that needs them all of the subdomains routed to the server, so I opt to only route the subdomains I want. But to answer your question about what is happening at the domain hosting, I was simply creating an A record for the www subdomain. I sent all for that subdomain to the same server that hosts the non-www version. Once that is set up then the traffic will go to the nginx server and then nginx will route it to the secure port of the non-www version.

Thank you so much that you toke the time to answer my question, that means a lot to me. you are the best :)

Good idea, ill add it to the list for future video ideas.

i am so confused if nginx? load balancers? or route53 cname?

What is chinese?

chinese characters : en.wikipedia.org/wiki/Chinese_characters

Is that bad?

If there a security issue with a specific version, could be... to fix that, in the nginx.conf file, search for "server_tokens off" entry and uncomment it.. that's it

Why not?