1.9 stream not working? 'directive is not allowed here'

Robert Paprocki rpaprocki at fearnothingproductions.net
Tue Apr 28 22:27:05 UTC 2015


It needs to be at the -same- level as the http {} block, not -within- the
http {} block.

worker_processes  4;

events {
    worker_connections  8192;
}

http {
    include       mime.types;
    default_type  application/octet-stream;
}

stream {
    upstream stream_backend {
        server 192.168.222.22:810 weight=5;
        server 192.168.222.17:810 weight=5;
    }
    server {
        listen     12345;
        proxy_pass stream_backend;
    }
}

On Tue, Apr 28, 2015 at 2:49 PM, itpp2012 <nginx-forum at nginx.us> wrote:

> Minimal conf;
>
> worker_processes  4;
>
> events {
>     worker_connections  8192;
> }
>
> http {
>     include       mime.types;
>     default_type  application/octet-stream;
>
>     stream {
>         upstream stream_backend {
>             server 192.168.222.22:810 weight=5;
>             server 192.168.222.17:810 weight=5;
>         }
>     }
>
>     server {
>         listen     12345;
>         proxy_pass stream_backend;
>     }
>
> }
>
> nginx -t
> nginx: [emerg] "stream" directive is not allowed here in conf\nginx.conf:11
> nginx: configuration file conf\nginx.conf test failed
>
> Whats incorrect here then?
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,258463,258467#msg-258467
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150428/e45b17e9/attachment-0001.html>


More information about the nginx mailing list