[GH-ISSUE #17] alpine build error #7

New issue

Closed

opened 2026-03-04 12:17:55 +03:00 by kerem · 13 comments

kerem commented 2026-03-04 12:17:55 +03:00

Owner

Copy link

Originally created by @phpstatic on GitHub (Jan 9, 2021).
Original GitHub issue: https://github.com/ADD-SP/ngx_waf/issues/17

In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:15:
../../module/ngx_waf/inc/ngx_http_waf_module_util.h:191:27: error: no member named '__in6_u' in 'struct in6_addr'
    memcpy(prefix, &addr6.__in6_u.__u6_addr8, 16);
                    ~~~~~ ^
In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:17:
../../module/ngx_waf/inc/ngx_http_waf_module_ip_trie.h:173:42: error: no member named '__in6_u' in 'struct in6_addr'
            if (CHECK_BIT(inx_addr->ipv6.__in6_u.__u6_addr8[uint8_index], 7 - (bit_index % 8)) != TRUE) {
                          ~~~~~~~~~~~~~~ ^
../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:295:51: note: expanded from macro 'CHECK_BIT'
#define CHECK_BIT(origin, bit_index) (CHECK_FLAG((origin), 1 << (bit_index)))
                                                  ^~~~~~
../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:284:37: note: expanded from macro 'CHECK_FLAG'
#define CHECK_FLAG(origin, flag) (((origin) & (flag)) != 0 ? TRUE : FALSE)
                                    ^~~~~~
In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:17:
../../module/ngx_waf/inc/ngx_http_waf_module_ip_trie.h:194:38: error: no member named '__in6_u' in 'struct in6_addr'
        if (CHECK_BIT(inx_addr->ipv6.__in6_u.__u6_addr8[uint8_index], 7 - (bit_index % 8)) != TRUE) {
                      ~~~~~~~~~~~~~~ ^
../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:295:51: note: expanded from macro 'CHECK_BIT'
#define CHECK_BIT(origin, bit_index) (CHECK_FLAG((origin), 1 << (bit_index)))
                                                  ^~~~~~
../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:284:37: note: expanded from macro 'CHECK_FLAG'
#define CHECK_FLAG(origin, flag) (((origin) & (flag)) != 0 ? TRUE : FALSE)
                                    ^~~~~~
In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:17:
../../module/ngx_waf/inc/ngx_http_waf_module_ip_trie.h:235:42: error: no member named '__in6_u' in 'struct in6_addr'
            if (CHECK_BIT(inx_addr->ipv6.__in6_u.__u6_addr8[uint8_index], 7 - (bit_index % 8)) != TRUE) {
                          ~~~~~~~~~~~~~~ ^
../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:295:51: note: expanded from macro 'CHECK_BIT'
#define CHECK_BIT(origin, bit_index) (CHECK_FLAG((origin), 1 << (bit_index)))
                                                  ^~~~~~
../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:284:37: note: expanded from macro 'CHECK_FLAG'
#define CHECK_FLAG(origin, flag) (((origin) & (flag)) != 0 ? TRUE : FALSE)
                                    ^~~~~~
In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1:
In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:18:
../../module/ngx_waf/inc/ngx_http_waf_module_config.h:522:34: error: no member named '__in6_u' in 'struct in6_addr'
            memcpy(inx_addr.ipv6.__in6_u.__u6_addr8, ipv6.prefix, 16);
                   ~~~~~~~~~~~~~ ^

Originally created by @phpstatic on GitHub (Jan 9, 2021). Original GitHub issue: https://github.com/ADD-SP/ngx_waf/issues/17 ```sh In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:15: ../../module/ngx_waf/inc/ngx_http_waf_module_util.h:191:27: error: no member named '__in6_u' in 'struct in6_addr' memcpy(prefix, &addr6.__in6_u.__u6_addr8, 16); ~~~~~ ^ In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:17: ../../module/ngx_waf/inc/ngx_http_waf_module_ip_trie.h:173:42: error: no member named '__in6_u' in 'struct in6_addr' if (CHECK_BIT(inx_addr->ipv6.__in6_u.__u6_addr8[uint8_index], 7 - (bit_index % 8)) != TRUE) { ~~~~~~~~~~~~~~ ^ ../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:295:51: note: expanded from macro 'CHECK_BIT' #define CHECK_BIT(origin, bit_index) (CHECK_FLAG((origin), 1 << (bit_index))) ^~~~~~ ../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:284:37: note: expanded from macro 'CHECK_FLAG' #define CHECK_FLAG(origin, flag) (((origin) & (flag)) != 0 ? TRUE : FALSE) ^~~~~~ In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:17: ../../module/ngx_waf/inc/ngx_http_waf_module_ip_trie.h:194:38: error: no member named '__in6_u' in 'struct in6_addr' if (CHECK_BIT(inx_addr->ipv6.__in6_u.__u6_addr8[uint8_index], 7 - (bit_index % 8)) != TRUE) { ~~~~~~~~~~~~~~ ^ ../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:295:51: note: expanded from macro 'CHECK_BIT' #define CHECK_BIT(origin, bit_index) (CHECK_FLAG((origin), 1 << (bit_index))) ^~~~~~ ../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:284:37: note: expanded from macro 'CHECK_FLAG' #define CHECK_FLAG(origin, flag) (((origin) & (flag)) != 0 ? TRUE : FALSE) ^~~~~~ In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:17: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_check.h:17: ../../module/ngx_waf/inc/ngx_http_waf_module_ip_trie.h:235:42: error: no member named '__in6_u' in 'struct in6_addr' if (CHECK_BIT(inx_addr->ipv6.__in6_u.__u6_addr8[uint8_index], 7 - (bit_index % 8)) != TRUE) { ~~~~~~~~~~~~~~ ^ ../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:295:51: note: expanded from macro 'CHECK_BIT' #define CHECK_BIT(origin, bit_index) (CHECK_FLAG((origin), 1 << (bit_index))) ^~~~~~ ../../module/ngx_waf/inc/ngx_http_waf_module_macro.h:284:37: note: expanded from macro 'CHECK_FLAG' #define CHECK_FLAG(origin, flag) (((origin) & (flag)) != 0 ? TRUE : FALSE) ^~~~~~ In file included from ../../module/ngx_waf/src/ngx_http_waf_module_core.c:1: In file included from ../../module/ngx_waf/inc/ngx_http_waf_module_core.h:18: ../../module/ngx_waf/inc/ngx_http_waf_module_config.h:522:34: error: no member named '__in6_u' in 'struct in6_addr' memcpy(inx_addr.ipv6.__in6_u.__u6_addr8, ipv6.prefix, 16); ~~~~~~~~~~~~~ ^ ```

kerem 2026-03-04 12:17:55 +03:00

• closed this issue
• added the
  bug
  label

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Jan 9, 2021):

Thanks for pointing out this bug caused by some undefined behavior in the code.

I have uploaded the hotfix commit and you can execute the following command to recompile the installation. If there are no errors please close the issue.

git checkout master
git pull --rebase
git checkout -b hotfix-v3.0.1 origin/hotfix-v3.0.1

<!-- gh-comment-id:757142157 --> @ADD-SP commented on GitHub (Jan 9, 2021): Thanks for pointing out this bug caused by some undefined behavior in the code. I have uploaded the hotfix commit and you can execute the following command to recompile the installation. If there are no errors please close the issue. ```bash git checkout master git pull --rebase git checkout -b hotfix-v3.0.1 origin/hotfix-v3.0.1 ```

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@phpstatic commented on GitHub (Jan 10, 2021):

build error fixed.

I am not sure how to setup the the cc and ipv4 black list to work. here is my config file in server section:

listen 88;
waf on;
waf_mode STD;
waf_rule_path /etc/nginx/waf/rules/;
waf_cc_deny_limit 10 60;

test ok and restart:

nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
/etc/init.d/nginx restart
[ ok ] Restarting nginx (via systemctl): nginx.service.

and also put my ip into /etc/nginx/waf/rules/ipv4, return 200.

test with wrk -t1 -c100 -d3, all 200.

 wrk -t1 -c100 -d3 http://remote:88/
Running 3s test @ http://remote:88/
  1 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   142.11ms  228.44ms   1.79s    88.59%
    Req/Sec     1.00k   810.67     2.96k    83.33%
  2982 requests in 3.01s, 0.92MB read
  Socket errors: connect 0, read 0, write 0, timeout 3
Requests/sec:    989.16
Transfer/sec:    313.94KB

add (?i)(?: curl/) into /etc/nginx/waf/rules/user-agent

*   Trying 127.0.1.1...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x55721df6cf90)
* Connected to localhost (127.0.1.1) port 88 (#0)
> GET / HTTP/1.1
> Host: localhost:88
> User-Agent: curl/7.64.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Server: nginx
< Date: Sun, 10 Jan 2021 04:33:31 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 2
< Last-Modified: Sun, 10 Jan 2021 04:08:30 GMT
< Connection: keep-alive
< Keep-Alive: timeout=120
< Vary: Accept-Encoding
< ETag: "5ffa7dbe-2"
< X-Content-Type-Options: nosniff
< Accept-Ranges: bytes
< 
a
* Connection #0 to host localhost left intact
* ```

<!-- gh-comment-id:757414018 --> @phpstatic commented on GitHub (Jan 10, 2021): build error fixed. I am not sure how to setup the the cc and ipv4 black list to work. here is my config file in server section: ```conf listen 88; waf on; waf_mode STD; waf_rule_path /etc/nginx/waf/rules/; waf_cc_deny_limit 10 60; ``` test ok and restart: ```sh nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful /etc/init.d/nginx restart [ ok ] Restarting nginx (via systemctl): nginx.service. ``` and also put my ip into /etc/nginx/waf/rules/ipv4, return 200. test with ` wrk -t1 -c100 -d3`, all 200. ```sh wrk -t1 -c100 -d3 http://remote:88/ Running 3s test @ http://remote:88/ 1 threads and 100 connections Thread Stats Avg Stdev Max +/- Stdev Latency 142.11ms 228.44ms 1.79s 88.59% Req/Sec 1.00k 810.67 2.96k 83.33% 2982 requests in 3.01s, 0.92MB read Socket errors: connect 0, read 0, write 0, timeout 3 Requests/sec: 989.16 Transfer/sec: 313.94KB ``` add `(?i)(?: curl/)` into `/etc/nginx/waf/rules/user-agent` ```sh * Trying 127.0.1.1... * TCP_NODELAY set * Expire in 200 ms for 4 (transfer 0x55721df6cf90) * Connected to localhost (127.0.1.1) port 88 (#0) > GET / HTTP/1.1 > Host: localhost:88 > User-Agent: curl/7.64.0 > Accept: */* > < HTTP/1.1 200 OK < Server: nginx < Date: Sun, 10 Jan 2021 04:33:31 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 2 < Last-Modified: Sun, 10 Jan 2021 04:08:30 GMT < Connection: keep-alive < Keep-Alive: timeout=120 < Vary: Accept-Encoding < ETag: "5ffa7dbe-2" < X-Content-Type-Options: nosniff < Accept-Ranges: bytes < a * Connection #0 to host localhost left intact * ```

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Jan 10, 2021):

Do you have ngx_http_rewrite_module installed and using a configuration like the one below?

server {
    ....
    listen 88;
    waf on;
    waf mode STD;
    waf_rule_path /etc/nginx/waf/rules/;
    waf_cc_deny_limit 10 60;
    
    location / {
        return 200 'Hello World!';
    }
    ....
}

If so, please change it to something like this and retest it.

server {
    ....
    listen 88;
    waf on;
    waf mode STD;
    waf_rule_path /etc/nginx/waf/rules/;
    waf_cc_deny_limit 10 60;

    root /path/to/html;
    index index.html index.htm;
    ....
}

The reason for this is that ngx_http_rewrite_module is mounted in an earlier processing phase than ngx_waf, so if return is used it will return the result directly instead of calling a subsequent processing phase, and ngx_waf will not be able to inspect the request.

At the moment, no other directives has been found to have a similar effect.

<!-- gh-comment-id:757427514 --> @ADD-SP commented on GitHub (Jan 10, 2021): Do you have `ngx_http_rewrite_module` installed and using a configuration like the one below? ```text server { .... listen 88; waf on; waf mode STD; waf_rule_path /etc/nginx/waf/rules/; waf_cc_deny_limit 10 60; location / { return 200 'Hello World!'; } .... } ``` If so, please change it to something like this and retest it. ```text server { .... listen 88; waf on; waf mode STD; waf_rule_path /etc/nginx/waf/rules/; waf_cc_deny_limit 10 60; root /path/to/html; index index.html index.htm; .... } ``` The reason for this is that `ngx_http_rewrite_module` is mounted in an earlier processing phase than `ngx_waf`, so if `return` is used it will return the result directly instead of calling a subsequent processing phase, and `ngx_waf` will not be able to inspect the request. At the moment, no other directives has been found to have a similar effect.

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@phpstatic commented on GitHub (Jan 10, 2021):

I have no rewrite:

server {
        listen 88;
        root /var/www;
        include conf.d/waf.ini;
}

waf.ini

waf on;
waf_mode STD;
waf_rule_path /etc/nginx/waf/rules/;
waf_cc_deny_limit 500 60;

When I try this:

server {
        listen 88;
        root /var/www;
    waf on;
    waf mode STD;
    waf_rule_path /etc/nginx/waf/rules/;
    waf_cc_deny_limit 10 60;
}

nginx -t
nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5

In the log objs/addon/src/ngx_http_waf_module_core.o is link into nginx, now sure why has this error.

I always use include conf.d/wal.ini style to manage different module conf file, never see this kink error.

<!-- gh-comment-id:757487430 --> @phpstatic commented on GitHub (Jan 10, 2021): I have no rewrite: ```conf server { listen 88; root /var/www; include conf.d/waf.ini; } ``` waf.ini ```ini waf on; waf_mode STD; waf_rule_path /etc/nginx/waf/rules/; waf_cc_deny_limit 500 60; ``` When I try this: ```conf server { listen 88; root /var/www; waf on; waf mode STD; waf_rule_path /etc/nginx/waf/rules/; waf_cc_deny_limit 10 60; } ``` ```sh nginx -t nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5 ``` In the log `objs/addon/src/ngx_http_waf_module_core.o` is link into nginx, now sure why has this error. I always use `include conf.d/wal.ini` style to manage different module conf file, never see this kink error.

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Jan 10, 2021):

Can you post the output of nginx -V?

It looks like you are using a static module, can you test the dynamic module to see if it has the same problem?

<!-- gh-comment-id:757487902 --> @ADD-SP commented on GitHub (Jan 10, 2021): Can you post the output of `nginx -V`? It looks like you are using a static module, can you test the dynamic module to see if it has the same problem?

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Jan 10, 2021):

I have no rewrite:

server {
        listen 88;
        root /var/www;
        include conf.d/waf.ini;
}

waf.ini

waf on;
waf_mode STD;
waf_rule_path /etc/nginx/waf/rules/;
waf_cc_deny_limit 500 60;

When I try this:

server {
        listen 88;
        root /var/www;
    waf on;
    waf mode STD;
    waf_rule_path /etc/nginx/waf/rules/;
    waf_cc_deny_limit 10 60;
}

nginx -t
nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5

In the log objs/addon/src/ngx_http_waf_module_core.o is link into nginx, now sure why has this error.

I always use include conf.d/wal.ini style to manage different module conf file, never see this kink error.

server {
        listen 88;
        root /var/www;
    waf on;
    waf mode STD;
    waf_rule_path /etc/nginx/waf/rules/;
    waf_cc_deny_limit 10 60;
}

There is a spelling error, waf mode should be corrected to waf_mode, there is an underscore between the two words.

<!-- gh-comment-id:757492749 --> @ADD-SP commented on GitHub (Jan 10, 2021): > I have no rewrite: > > ``` > server { > listen 88; > root /var/www; > include conf.d/waf.ini; > } > ``` > > waf.ini > > ```ini > waf on; > waf_mode STD; > waf_rule_path /etc/nginx/waf/rules/; > waf_cc_deny_limit 500 60; > ``` > > When I try this: > > ``` > server { > listen 88; > root /var/www; > waf on; > waf mode STD; > waf_rule_path /etc/nginx/waf/rules/; > waf_cc_deny_limit 10 60; > } > ``` > > ```shell > nginx -t > nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5 > ``` > > In the log `objs/addon/src/ngx_http_waf_module_core.o` is link into nginx, now sure why has this error. > > I always use `include conf.d/wal.ini` style to manage different module conf file, never see this kink error. ```text server { listen 88; root /var/www; waf on; waf mode STD; waf_rule_path /etc/nginx/waf/rules/; waf_cc_deny_limit 10 60; } ``` There is a spelling error, `waf mode` should be corrected to `waf_mode`, there is an underscore between the two words.

kerem commented 2026-03-04 12:17:56 +03:00

Author

Owner

Copy link

@phpstatic commented on GitHub (Jan 12, 2021):

Yes, the binary is static linked.

nginx -V
nginx version: nginx/1.18.0 (nginx)
built by gcc version 9.3.0
built with OpenSSL 1.1.0 (compatible; BoringSSL) (running with BoringSSL)
TLS SNI support enabled
configure arguments:--conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --user=www-data --group=www-data --without-select_module --with-poll_module --with-file-aio --with-threads --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_sub_module --with-http_stub_status_module --with-http_slice_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_auth_request_module --with-http_secure_link_module --with-stream --with-stream_ssl_module --with-stream_ssl_preread_module --with-stream_realip_module --with-pcre --with-pcre-jit --with-openssl --with-zlib --with-zlib-asm=pentiumpro --with-libatomic --with-http_addition_module --without-http_uwsgi_module --with-mail --with-mail_ssl_module --with-http_mp4_module --with-http_flv_module --add-module=devel_kit --add-module=brotli --add-module=zstd --add-module=substitutions_filter --add-module=headers-more --add-module=h264_streaming --add-module=vod --add-module=secure-token --add-module=flv --add-module=dynamic_limit_req --add-module=slice --add-module=njs/nginx --add-module=vts --with-http_geoip_module --with-stream_geoip_module --add-module=geoip2 --add-module=ipip --add-module=ModSecurity --add-module=security_headers --add-module=tcp-keepalive --with-http_v3_module --with-openssl --with-quiche

change to waf_mode still get same results:

nginx -t
nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5
nginx: configuration file /etc/nginx/nginx.conf test failed

<!-- gh-comment-id:758408161 --> @phpstatic commented on GitHub (Jan 12, 2021): Yes, the binary is static linked. ```sh nginx -V nginx version: nginx/1.18.0 (nginx) built by gcc version 9.3.0 built with OpenSSL 1.1.0 (compatible; BoringSSL) (running with BoringSSL) TLS SNI support enabled configure arguments:--conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --user=www-data --group=www-data --without-select_module --with-poll_module --with-file-aio --with-threads --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_sub_module --with-http_stub_status_module --with-http_slice_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_auth_request_module --with-http_secure_link_module --with-stream --with-stream_ssl_module --with-stream_ssl_preread_module --with-stream_realip_module --with-pcre --with-pcre-jit --with-openssl --with-zlib --with-zlib-asm=pentiumpro --with-libatomic --with-http_addition_module --without-http_uwsgi_module --with-mail --with-mail_ssl_module --with-http_mp4_module --with-http_flv_module --add-module=devel_kit --add-module=brotli --add-module=zstd --add-module=substitutions_filter --add-module=headers-more --add-module=h264_streaming --add-module=vod --add-module=secure-token --add-module=flv --add-module=dynamic_limit_req --add-module=slice --add-module=njs/nginx --add-module=vts --with-http_geoip_module --with-stream_geoip_module --add-module=geoip2 --add-module=ipip --add-module=ModSecurity --add-module=security_headers --add-module=tcp-keepalive --with-http_v3_module --with-openssl --with-quiche ``` change to `waf_mode` still get same results: ```sh nginx -t nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5 nginx: configuration file /etc/nginx/nginx.conf test failed ```

kerem commented 2026-03-04 12:17:57 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Jan 12, 2021):

Yes, the binary is static linked.

nginx -V
nginx version: nginx/1.18.0 (nginx)
built by gcc version 9.3.0
built with OpenSSL 1.1.0 (compatible; BoringSSL) (running with BoringSSL)
TLS SNI support enabled
configure arguments:--conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --user=www-data --group=www-data --without-select_module --with-poll_module --with-file-aio --with-threads --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_sub_module --with-http_stub_status_module --with-http_slice_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_auth_request_module --with-http_secure_link_module --with-stream --with-stream_ssl_module --with-stream_ssl_preread_module --with-stream_realip_module --with-pcre --with-pcre-jit --with-openssl --with-zlib --with-zlib-asm=pentiumpro --with-libatomic --with-http_addition_module --without-http_uwsgi_module --with-mail --with-mail_ssl_module --with-http_mp4_module --with-http_flv_module --add-module=devel_kit --add-module=brotli --add-module=zstd --add-module=substitutions_filter --add-module=headers-more --add-module=h264_streaming --add-module=vod --add-module=secure-token --add-module=flv --add-module=dynamic_limit_req --add-module=slice --add-module=njs/nginx --add-module=vts --with-http_geoip_module --with-stream_geoip_module --add-module=geoip2 --add-module=ipip --add-module=ModSecurity --add-module=security_headers --add-module=tcp-keepalive --with-http_v3_module --with-openssl --with-quiche

change to waf_mode still get same results:

nginx -t
nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5
nginx: configuration file /etc/nginx/nginx.conf test failed

Hello, I found some problems with the configure arguments you gave. I downloaded the source code from nginx.org. I didn't find the --with-http_v3_module and --with-quiche arguments, where did you download the source code from? Maybe we are using a different source code for NGINX.

<!-- gh-comment-id:758713602 --> @ADD-SP commented on GitHub (Jan 12, 2021): > Yes, the binary is static linked. > > ```shell > nginx -V > nginx version: nginx/1.18.0 (nginx) > built by gcc version 9.3.0 > built with OpenSSL 1.1.0 (compatible; BoringSSL) (running with BoringSSL) > TLS SNI support enabled > configure arguments:--conf-path=/etc/nginx/nginx.conf --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --user=www-data --group=www-data --without-select_module --with-poll_module --with-file-aio --with-threads --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_sub_module --with-http_stub_status_module --with-http_slice_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_auth_request_module --with-http_secure_link_module --with-stream --with-stream_ssl_module --with-stream_ssl_preread_module --with-stream_realip_module --with-pcre --with-pcre-jit --with-openssl --with-zlib --with-zlib-asm=pentiumpro --with-libatomic --with-http_addition_module --without-http_uwsgi_module --with-mail --with-mail_ssl_module --with-http_mp4_module --with-http_flv_module --add-module=devel_kit --add-module=brotli --add-module=zstd --add-module=substitutions_filter --add-module=headers-more --add-module=h264_streaming --add-module=vod --add-module=secure-token --add-module=flv --add-module=dynamic_limit_req --add-module=slice --add-module=njs/nginx --add-module=vts --with-http_geoip_module --with-stream_geoip_module --add-module=geoip2 --add-module=ipip --add-module=ModSecurity --add-module=security_headers --add-module=tcp-keepalive --with-http_v3_module --with-openssl --with-quiche > ``` > > change to `waf_mode` still get same results: > > ```shell > nginx -t > nginx: [emerg] invalid number of arguments in "waf" directive in /etc/nginx/conf.d/aa.conf:5 > nginx: configuration file /etc/nginx/nginx.conf test failed > ``` Hello, I found some problems with the configure arguments you gave. I downloaded the source code from `nginx.org`. I didn't find the `--with-http_v3_module` and `--with-quiche` arguments, where did you download the source code from? Maybe we are using a different source code for NGINX.

kerem commented 2026-03-04 12:17:57 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Jan 19, 2021):

Hello, the latest stable version has been released, which supports printing debug logs. You can adjust the error log level to debug after the update and upload the error.log file to help locate the error, remember to clear the privacy information in the file.

<!-- gh-comment-id:762548432 --> @ADD-SP commented on GitHub (Jan 19, 2021): Hello, the latest stable version has been released, which supports printing debug logs. You can adjust the error log level to `debug` after the update and upload the `error.log` file to help locate the error, remember to clear the privacy information in the file.

kerem commented 2026-03-04 12:17:57 +03:00

Author

Owner

Copy link

@phpstatic commented on GitHub (Feb 2, 2021):

The http3 patch is come from CloudFlare quiche patch. I will try and update the new version.

<!-- gh-comment-id:771342601 --> @phpstatic commented on GitHub (Feb 2, 2021): The http3 patch is come from CloudFlare quiche patch. I will try and update the new version.

kerem commented 2026-03-04 12:17:57 +03:00

Author

Owner

Copy link

@phpstatic commented on GitHub (Feb 7, 2021):

I can confirm the build is working now, but some time get Segmentation fault. not sure it is ngx_waf related.

<!-- gh-comment-id:774788600 --> @phpstatic commented on GitHub (Feb 7, 2021): I can confirm the build is working now, but some time get Segmentation fault. not sure it is ngx_waf related.

kerem commented 2026-03-04 12:17:57 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Feb 8, 2021):

I can confirm the build is working now, but some time get Segmentation fault. not sure it is ngx_waf related.

You can compile a program suitable for debugging by changing the parameters -with-cc-opt='-O0 -g' and -with-debug in the configuration script. When you get an error, you can debug the core file with gdb and generally find out the location of the source code of the error.

<!-- gh-comment-id:775256810 --> @ADD-SP commented on GitHub (Feb 8, 2021): > I can confirm the build is working now, but some time get Segmentation fault. not sure it is ngx_waf related. You can compile a program suitable for debugging by changing the parameters `-with-cc-opt='-O0 -g'` and `-with-debug` in the configuration script. When you get an error, you can debug the `core` file with `gdb` and generally find out the location of the source code of the error.

kerem commented 2026-03-04 12:17:57 +03:00

Author

Owner

Copy link

@ADD-SP commented on GitHub (Mar 1, 2021):

I closed this issue because I did not receive a response for more than 15 days, so you can reopen it if you have questions.

<!-- gh-comment-id:787690859 --> @ADD-SP commented on GitHub (Mar 1, 2021): I closed this issue because I did not receive a response for more than 15 days, so you can reopen it if you have questions.

kerem referenced this issue 2026-03-04 12:19:03 +03:00

[PR #11] Check uthash library at configure time #116

kerem referenced this issue 2026-03-13 16:30:12 +03:00

[GH-ISSUE #7] Evaluate use of system uthash #140

kerem referenced this issue 2026-03-13 17:08:00 +03:00

[PR #11] [MERGED] Check uthash library at configure time #231

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

lts

lts-dev

add_sp/refactor-replace-libcurl-with-subreq

current-dev

current

current-dev-backup

v6.1.10

v10.1.2

v6.1.9

v6.1.8

v10.1.1

v10.1.0

v6.1.7

v10.0.1

v10.0.0

v9.0.6

v9.0.5

v6.1.6

v6.1.5

v9.0.4

v9.0.3

v9.0.2

v9.0.1

v9.0.0

v8.0.3

v6.1.4

v8.0.2

v8.0.1

v6.1.3

v8.0.0

v7.1.0

v6.1.2

v7.0.1

v7.0.0

v6.1.1

v6.1.0

v6.0.3

v6.0.2

v6.0.2-beta.1

v6.0.1

v6.0.1-beta.2

v6.0.1-beta.1

v6.0.0

v6.0.0-beta.4

v5.5.1

v6.0.0-beta.2

v6.0.0.beta.3

v6.0.0-beta.1

v5.5.0

v5.4.2

v5.4.2-beta.2

v5.4.2-beta.1

v5.4.1

v5.4.1-beta.1

v5.4.0

v5.4.0-beta.1

v5.3.2

v5.3.1

v5.3.0

v5.3.0-beta.4

v5.3.0-beta.3

v5.3.0-beta.2

v5.3.0-beta.1

v5.2.0

v5.2.0-beta.2

v5.2.0-beta.1

v5.1.1

v5.1.1-beta.1

v5.1.0

v5.0.0

v5.0.0-beta.5

v5.0.0-beta.4

v5.0.0-beta.3

v5.0.0-beta.2

v5.0.0-beta.1

v4.1.0-beta.4

v4.1.0-beta.3

v4.1.0-beta.2

v4.1.0-beta.1

v4.0.0

v4.0.0-beta.2

v3.1.6

v3.2.0-beta.1

v3.1.5

v3.1.4

v3.1.3

v3.1.2

v3.1.1

v3.1.0

v3.1.0-beta-1

v3.0.3-beta-3

v3.0.2

v3.0.3-beta-2

v3.0.3-beta-1

v3.0.2-beta-2

v3.0.2-beta-1

v3.0.1

v3.0.0

v3.0.0-beta-2

v3.0.0-beta-1

v2.1.1

v2.1.0

v2.0.2

v2.0.1

v2.0.1-beta-1

v2.0.0

v2.0.0-beta.1

v1.0.1

v1.0.0

v1.0.0-RC2

v1.0.0-RC1

Labels

Clear labels   

MacOS

  

Nginx

  

OpenResty

  

Tengine

  

bug

  

documentation

  

enhancement

  

needs-investigation

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

stale

  

stale

  

stale

  

timeout

  

wontfix

No labels

MacOS

Nginx

OpenResty

Tengine

bug

documentation

enhancement

needs-investigation

pull-request

question

stale

stale

stale

timeout

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ngx_waf#7

No description provided.