Hi Igor,
Yes the server runs other software including httpd with a similar number of
vhost
# grep "
wrote:
> Anoop,
>
> I don't see any troubles with your configuration.
> Also, if you have 120G of RAM and a single worker - the problem is not in
> nginx.
> Do you have other software running on t
I don't think there's rails passenger settings Adding passenger to the
Gemfile only causes the app to use passenger in development mode
instead of the default (presently puma)
On Tue, Aug 7, 2018 at 6:26 PM, Francis Daly wrote:
> On Tue, Aug 07, 2018 at 03:22:45PM -0400, fugee ohu wrote:
>
> Hi t
If I have `listen 80 ssl;` would that do the redirect automatically
for me without the explicit redirect you gave me?
On Tue, Aug 7, 2018 at 6:23 PM, Jeff Dyke wrote:
> how about adding
> server {
>listen 80;
>redirect https://$host$request_uri 301; //YYMV as to what destination
> you ne
Hi Maxim, that's very helpful...
> -Original Message-
> From: nginx [mailto:nginx-boun...@nginx.org] On Behalf Of Maxim Dounin
> On Tue, Aug 07, 2018 at 02:45:02AM +, Cameron Kerr wrote:
> > Option 3: (does not work)
> This approach is expected to work fine (assuming you've used lim
On Tue, Aug 07, 2018 at 03:22:45PM -0400, fugee ohu wrote:
Hi there,
> I'm trying to enable site wide ssl over port 443 on a site that runs
> on http port 80
> In nginx.conf i have `listen 443 ssl;` for the server but requests for
> the server get routed to the first available host on port 80, an
how about adding
server {
listen 80;
redirect https://$host$request_uri 301; //YYMV as to what destination
you need them to end up at.
}
On Tue, Aug 7, 2018 at 3:58 PM, fugee ohu wrote:
> What do you mean by "also have a port 80 config" ? The port 80 configs
> are my other sites that I ha
What do you mean by "also have a port 80 config" ? The port 80 configs
are my other sites that I haven't created certificates for yet The
port 80 config for the site in question is commented out in favor of
`listen 443 ssl;`
On Tue, Aug 7, 2018 at 3:45 PM, basti wrote:
> first of all use wget or
first of all use wget or curl for testing to bypass browser cache.
when you have also a port 80 config and call http://example.com you
*must* have a redirect to https. when you call https://example.com it
should work, i think (not tested)
On 07.08.2018 21:39, fugee ohu wrote:
> server {
>list
server {
listen 443 ssl;
ssl_certificate /etc/ssl/certs/sitename/certificate.crt;
ssl_certificate_key /etc/ssl/certs/sitename/private.key;
server_name *.sitename.com www.sitename.com sitename;
charset utf-8;
location / {
root /usr/home/fugee/websites/sitename/public;
rails_
server {
listen 80;
# listen 443 ssl;
# ssl_certificate /etc/ssl/certs/ignatzmouse/certificate.crt;
# ssl_certificate_key /etc/ssl/certs/ignatzmouse/private.key;
server_name *.sitename.com www.sitename.com sitename.com;
charset utf-8;
location / {
root /usr/home/fugee/websites
server {
listen 443 ssl;
ssl_certificate /etc/ssl/certs/ignatzmouse/certificate.crt;
ssl_certificate_key /etc/ssl/certs/ignatzmouse/private.key;
server_name *.ignatzmouse.com www.ignatzmouse.com ignatzmouse.com;
charset utf-8;
location / {
root /usr/home/fugee/websites/ignatzm
please show us your config
On 07.08.2018 21:22, fugee ohu wrote:
> I'm trying to enable site wide ssl over port 443 on a site that runs
> on http port 80
> In nginx.conf i have `listen 443 ssl;` for the server but requests for
> the server get routed to the first available host on port 80, another
I'm trying to enable site wide ssl over port 443 on a site that runs
on http port 80
In nginx.conf i have `listen 443 ssl;` for the server but requests for
the server get routed to the first available host on port 80, another
of my sites also in the nginx.conf How can I diagnose this to see
what's
Hello!
On Tue, Aug 07, 2018 at 02:45:02AM +, Cameron Kerr wrote:
> Hi all, I’ve recently deployed a rate-limiting configuration
> aimed at protecting myself from spiders.
>
> nginx version: nginx/1.15.1 (RPM from nginx.org)
>
> I did this based on the excellent Nginx blog post at
> https:
Anoop,
I don't see any troubles with your configuration.
Also, if you have 120G of RAM and a single worker - the problem is not
in nginx.
Do you have other software running on the host?
Basically, you just run out of memory.
You can optimize your reload though: use "service nginx reload" (or
> Hello,
> Thanks for that input, I changed my config like you said and also set the
> fastcgi_param SCRIPT_FILENAME to /path/to/the/index.php;
> But I feel like this should be done by the rewrite directive instead of this
> way. Now that this is working, can someone please tell me if I can use
16 matches
Mail list logo
