Hi,
Thanks for your contribution to the nginx community Piotr and your reply.
Do you have any suggestions on how to bypass this problem?
Any update on the module in the near future that might fix this issue?
Thanks
Jan
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236987,237036#msg-2
Sent from my BlackBerry 10 smartphone.
Hey,
As a quick test you may try switching to a proxy + proxy_cache
setup instead of slowfs_cache to see if slowfs_cache module
problem or something more general.
It's a known issue with my ngx_slowfs_cache module.
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
*sigh* Clearly I am missing something here, as the only nginx.conf file
I have is the one I posted last night. There is no upstream server; the
code for that was from the example config file I was trying to modify
for my purposes.
It seems that this copypasta approach isn't adequate for setting
Are you saying that you do not have administrative control of your system?
Jonathan is right - set policies that disallow large file sizes and enforce
them.
If necessary use chron to check for large files and remove them.
On Wed, Mar 6, 2013 at 2:28 PM, Calin Don wrote:
> Unfortunately the wa
your nginx-conf please that points to your upstream http://forum.nginx.org/read.php?2,236971,237029#msg-237029
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Unfortunately the way big files are getting there is beyond my control.
On Wed, Mar 6, 2013 at 5:30 PM, Jonathan Matthews
wrote:
> On 6 March 2013 13:28, Calin Don wrote:
> > Hi,
> >
> > Is there a way to server files only below a certain size?
> > eg. Return 403 on files bigger than 5MB?
>
> A
Thanks! The Resolver did the trick.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236969,237020#msg-237020
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I'm not sure what you mean here; Which aspects of the actual
configuration? The Capistrano deployment, the Unicorn.rb file, or some
other part of the Nginx configuration? I've attached the former two,
with the sensitive data masked out of course, but I'm not certain what
else you would need.
I did
Joseph O. Wrote:
---
> Ah, thank you. Removing the site configuration file did fix the
> gateway
> error, but now the server is still pointing at the default Nginx
> welcome
> page. Can you (or anyone else here) give me any advice on how to get
>
Yes you are right. Thank you.
On Mar 6, 2013, at 5:44 PM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Mar 06, 2013 at 04:45:33PM +0200, Kiril Kalchev wrote:
>
>> Just for the record, I think I found a kind of solution. It
>> looks good if my backend returns http codes 3xx. I have tried
>> with
Hello!
On Wed, Mar 06, 2013 at 04:45:33PM +0200, Kiril Kalchev wrote:
> Just for the record, I think I found a kind of solution. It
> looks good if my backend returns http codes 3xx. I have tried
> with 333 and 334 and it looks great. I know it is an ugly hack,
> but my findings may help to o
On 6 March 2013 12:34, Andre Jaenisch wrote:
> 2013/3/6 onel0ve :
>> I just need to convert this to nginx rules .
>
> I guess, the thing is, that you shall learn, how this can be achieved.
> So you can do it on your own the next time.
> In case you've tried it yet, it may be helpful to show your a
On 6 March 2013 13:28, Calin Don wrote:
> Hi,
>
> Is there a way to server files only below a certain size?
> eg. Return 403 on files bigger than 5MB?
Assuming you're talking about local filesystem files, you might try to
proxy_pass back round to yourself, and do an if() based on
$upstream_http_c
Ah, thank you. Removing the site configuration file did fix the gateway
error, but now the server is still pointing at the default Nginx welcome
page. Can you (or anyone else here) give me any advice on how to get the
server to point to my actual service?
BTW, you pointed out that there was an ups
Just for the record, I think I found a kind of solution. It looks good if my
backend returns http codes 3xx. I have tried with 333 and 334 and it looks
great. I know it is an ugly hack, but my findings may help to other poor souls.
I hope this behavior will not change in the next versions.
Re
Hello!
On Wed, Mar 06, 2013 at 04:02:30PM +0200, Kiril Kalchev wrote:
> Is there any way to force nginx to read request body? I really
> don't care about this overhead, I hit connection limit much more
> faster. Thank you for the super fast answer.
No, there is no way to force nginx to read re
Is there any way to force nginx to read request body? I really don't care about
this overhead, I hit connection limit much more faster. Thank you for the super
fast answer.
Regards,
Kiril
On Mar 6, 2013, at 3:54 PM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Mar 06, 2013 at 03:44:37PM +0200, Ki
Hello!
On Wed, Mar 06, 2013 at 03:44:37PM +0200, Kiril Kalchev wrote:
> I have noticed that when I set 'proxy_intercept_errors on;' in
> my nginx config it kills tcp connection to the origin server if
> it returns 4xx or 5xx?
> This is my example config to reproduce the
> situation(https://gi
Hi,
I have noticed that when I set 'proxy_intercept_errors on;' in my nginx config
it kills tcp connection to the origin server if it returns 4xx or 5xx?
This is my example config to reproduce the
situation(https://gist.github.com/kirilkalchev/5098882). I am in a situation
where my backend se
Hi,
On Sun, Mar 03, 2013 at 07:38:39PM +0100, GASPARD kévin wrote:
Hi there,
>Probably a single extra try_files line will work for you.
This is my new config file :
location ~ \.php$ {
try_files $uri $uri/ /index.php?q=$uri&$args;
}
You will probably
Hi,
Is there a way to server files only below a certain size?
eg. Return 403 on files bigger than 5MB?
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Wed, Mar 06, 2013 at 07:43:54AM +0100, Evgeny T. wrote:
> Nginx не отдает файлы > 1мб
>
> Есть Rails + Nginx + Unicorn
> Все работает, мелкие файлы отдаются, даже видео через JWPlayer
> проигрывается.
> Проблема в том, что есть флешка 1.8 МБ и когда пытаешься ее вывести на
> страницу и
Hello!
On Wed, Mar 06, 2013 at 05:28:12AM -0500, yvlasov wrote:
> Hello
> In our setup we have an NGNX as front-end and several back-end.
> The problem is our load profile, we have a lot of simple and fast http
> requests, and very few but very heavy in terms of time and BE cpu requests.
>
> So
2013/3/6 onel0ve :
> I just need to convert this to nginx rules .
I guess, the thing is, that you shall learn, how this can be achieved.
So you can do it on your own the next time.
In case you've tried it yet, it may be helpful to show your attempts.
Look, it seems that you want others to do your
Hello!
On Wed, Mar 06, 2013 at 07:16:39AM -0500, jan5134 wrote:
> Thanks for the quick reply.
>
> I would like to test that but i'm kind of new to nginx and also our website
> can't have any downtime.
> Any other suggestion maybe?
Try to reproduce the problem in a sandbox, it should help with
Thanks for the quick reply.
I would like to test that but i'm kind of new to nginx and also our website
can't have any downtime.
Any other suggestion maybe?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236987,236989#msg-236989
___
nginx ma
Hello!
On Wed, Mar 06, 2013 at 07:02:28AM -0500, jan5134 wrote:
> Hi,
>
> I'm having issues with nginx where my cache directory keeps growing until
> the hdd is full.
> If anyone can give me any information on how to solve this it will be
> appreciated.
>
> nginx -V:
>
> nginx version: nginx/1
Hi,
I'm having issues with nginx where my cache directory keeps growing until
the hdd is full.
If anyone can give me any information on how to solve this it will be
appreciated.
nginx -V:
nginx version: nginx/1.2.1
built by gcc 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC)
TLS SNI support enabled
conf
Hello!
On Wed, Mar 06, 2013 at 01:23:28AM +0100, Arman Mirk wrote:
> I notice our server is rapidly responding 500 errors for random pages.
> Our setup is pretty basic. We are running Nginx 0.7.6 with Unicorn and a
> Rails app on a Ubuntu 10.4 server.
>
> What ever the problem, it doesn't seem t
For beter understanding here is my config sniper
upstream super_upstream {
keepalive 128;
server be1 max_fails=45 fail_timeout=3s;
server be2 max_fails=45 fail_timeout=3s;
server be3 max_fails=45 fail_timeout=3s;
}
server {
server_name pytn.ru;
location ^~
Hello
In our setup we have an NGNX as front-end and several back-end.
The problem is our load profile, we have a lot of simple and fast http
requests, and very few but very heavy in terms of time and BE cpu requests.
So my idea is to use proxy_next_upstream for simple request as usual and it
work
On Tue, Mar 05, 2013 at 12:17:03AM +, Jonathan Matthews wrote:
> A slight thinko crept in to my original mail; there's a small
> difference (which does remove a minor complexity) as I've marked below
> ...
>
> On 4 March 2013 23:58, Jonathan Matthews wrote:
> [snip]
> > --
I just need to convert this to nginx rules .
# To ignore htaccess - enlist here
RewriteCond $1
!^(index\.php|ftpservice|demo|ftpdb|MDF|phpsysinfo|admin|templates|links|
api|forum|articles|imageGallery|language|includes|ajax|resources|fonts|images|parse|directory|
uploads|system|rss\.php|robots\.t
34 matches
Mail list logo
