You can also do 'nginx -s reload' which will reload your configurations and not take the site down by restarting nginx. Great videos. Really enjoying them.
@JacurtisTutorials
7 жыл бұрын
Good tip. THats a more "universal" way to do it. Where as the systemctl method doesn't work on every Unix OS.
@anirudhkrishna9655
6 жыл бұрын
Hit the 100th like, great detailed tutorial, keep making tutorial on nginx, there are not many of them on youtube. Peace.
@predatoreyez
3 жыл бұрын
Awesome explanation, very simple and clear and yet very helpful and not confusing. Good job
@eleftrik
7 жыл бұрын
Hi, you said that Let's Encrypt certificate is on goblockade.com. But what about www.goblockade.com? "curl -i www.goblockade.com" reports "curl: (51) SSL: no alternative certificate subject name matches target host name", Chrome automatically redirect to goblockade.com, Firefox returns a warning about unsecure connection (correct). How do you usually deal this case? Do you request another SSL certificate for www domain? I think this is an important point. Thank you
@systemicacloud6017
5 жыл бұрын
Thanks very much, worked nice, i tested CentOS Linux release 7.7.1908 (Core) and nginx version: nginx/1.16.1.
@michaelfarhat4881
3 жыл бұрын
Saved my day dude. Thanks
@miyukinagara
2 жыл бұрын
thx bro for explain, I have a little question about that. if i doing that. is good for seo ?
@MauricioMartinez0707
4 жыл бұрын
Exactly what I was looking for. Thanks man
@micosair
7 жыл бұрын
You`re on fire lately!
@JacurtisTutorials
7 жыл бұрын
Haha thanks.
@infinitylooks4556
7 жыл бұрын
Hey, your videos are very thoughtful and awesome. Do a video on sub domain routing both in development and production, thanks!
@cooldude3010
7 жыл бұрын
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
@infinitylooks4556
7 жыл бұрын
A detailed explanation would be better
@JacurtisTutorials
7 жыл бұрын
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).
@gokhangorkem
6 жыл бұрын
This is great dude. Awesome.
@mohamedgabr4911
7 жыл бұрын
thank you for the video, but how does that happen on your domain hosting? just wondering, does it take any extra configuration on the domain hosting ? thanks!
@JacurtisTutorials
7 жыл бұрын
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.
@mohamedgabr4911
7 жыл бұрын
Thank you so much that you toke the time to answer my question, that means a lot to me. you are the best :)
@trendyfashion9349
6 жыл бұрын
https enabled and redirecting my http to https but without any greenlock pad what should I do
@kesitkusumo628
6 жыл бұрын
Great! Nice Tutorial.
@vhoraayan3372
5 жыл бұрын
ww program BP picture
@maxmininformer6697
6 жыл бұрын
how to redirect 301 from one domain to another even each post to another post, both hosted on digital ocean with serverpilot.. please send link if video is available..
@apichaidensamut
5 жыл бұрын
Very nice video thanks
@mazenn99
3 жыл бұрын
thank you very much
@EdwinRebolledo
4 жыл бұрын
Good video!
@briangichohi594
5 жыл бұрын
what font are you using for your terminal?
@prasannakumarpulagam
4 жыл бұрын
Hi How can i map url in Nginx? for example I want to map the ClouderaManager IP(192.168.0.xx:7180) and port number to Nginx server, How can I do that? can you explain me please.
@SoloTravelBlog
2 жыл бұрын
File doesn't exist ....
@fabiansanchezp
5 жыл бұрын
Muchas gracias. Me sirvió demasiado.
@rahulak6596
3 жыл бұрын
thanks bro..
@skarnvy8109
7 жыл бұрын
I would be grateful if you could make a video about using & generating dynamic sub-domains with laravel :)
@JacurtisTutorials
7 жыл бұрын
Good idea, ill add it to the list for future video ideas.
@juanrincon6576
5 ай бұрын
Come back Alex!!
@skalippanbalippan6972
6 жыл бұрын
Thanks man
@robsonscheppercachoeira6721
6 жыл бұрын
Perfect!
@pequlatv4814
3 жыл бұрын
I had 4 courses relating just plain web development, absolutley noone on the whole univeristy wanted to show me how to do this
@sireeshasiri8107
Жыл бұрын
how to convert http to https in hpux
@bloggervista
7 жыл бұрын
Thx alex
@DarkWaffle56
4 жыл бұрын
This didn't solve my problem, so hopefully my solution will help others: 1. Go to EC2 panel, and click on Load Balancer tab, and then on your load balancer; 2. Make sure you have 2 listeners: one for HTTP and one for HTTPS (otherwise create those); 3. Edit the rules for each one of them, adding a new rules for each that specifies your (www)(dot)(dot)com to go to port 443 and to be redirected to (dot)com; 4. Having the rules for both HTTP and HTTPS to be redirected to 443 with no "WWW" will be working immediately after that. Hopefully this helped. PS 1: I didn't have sites-available folder in my nginx for my Elastic Beanstalk app EC2. Apart from that, the steps I am saying are much more safer and easier to do. PS 2: Modifications in the EC2 will not be persisted as well since Elastic Beanstalk can instantiate new ones for your app, so keep this in mind.
@icalculi
3 жыл бұрын
i am so confused if nginx? load balancers? or route53 cname?
@ergurkha3157
7 жыл бұрын
I can see the nginx version you have installed...
@JacurtisTutorials
7 жыл бұрын
Is that bad?
@ergurkha3157
7 жыл бұрын
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
@cromartie1984
7 жыл бұрын
why does it appear in chinese on google search ?
@JacurtisTutorials
7 жыл бұрын
What is chinese?
@cromartie1984
7 жыл бұрын
chinese characters : en.wikipedia.org/wiki/Chinese_characters
@Graf777gos
7 жыл бұрын
Do not have redirect www.domain.com to domain.com
@JacurtisTutorials
7 жыл бұрын
Why not?
@davidsontechnology4757
4 жыл бұрын
I bring you blessings from my LORD JESUS CHRIST WHO Is coming again to judge the living and the dead. Please give your life to HIM
Пікірлер: 51