Личный кабинет ошибка 404 Not Found

Jakut

Member
Здравствуйте!

Установил Nemesida WAF, Nemesida WAF API, Личный кабинет Nemesida WAF.
WAF с веб приложением взаимодействует нормально, во всяком случае тестовый запрос отрабатывается корректно.
При попытке входа в личный кабинет появляется ошибка 404 Not Found.


Подскажите, пожалуйста, в чем может быть проблема?
 

rr

Administrator
Здравствуйте!

Установил Nemesida WAF, Nemesida WAF API, Личный кабинет Nemesida WAF.
WAF с веб приложением взаимодействует нормально, во всяком случае тестовый запрос отрабатывается корректно.
При попытке входа в личный кабинет появляется ошибка 404 Not Found.


Подскажите, пожалуйста, в чем может быть проблема?

Добрый день,

/static лишний, правильный путь: /waf/personal/
 

Jakut

Member
Да, после перезагрузки ошибка сохраняется.
2022/03/24 11:20:29 [error] 1604#1604: *12 Nemesida WAF: the request 267a7de0f8cddfc3f7cb411f83998633 blocked by rule ID 1 in zone URL, client: 10.5.97.182, server: your_domain, request: "GET /nwaftest HTTP/1.1", host: "your_domain"
2022/03/24 11:20:36 [error] 1604#1604: *16 Nemesida WAF: the request 7d578549c8fca03fc44ad5252be9899d blocked by rule ID 1 in zone URL, client: 10.5.97.182, server: test-ib1, request: "GET /nwaftest HTTP/1.1", host: "test-ib1"
 

rr

Administrator
Да, после перезагрузки ошибка сохраняется.
2022/03/24 11:20:29 [error] 1604#1604: *12 Nemesida WAF: the request 267a7de0f8cddfc3f7cb411f83998633 blocked by rule ID 1 in zone URL, client: 10.5.97.182, server: your_domain, request: "GET /nwaftest HTTP/1.1", host: "your_domain"
2022/03/24 11:20:36 [error] 1604#1604: *16 Nemesida WAF: the request 7d578549c8fca03fc44ad5252be9899d blocked by rule ID 1 in zone URL, client: 10.5.97.182, server: test-ib1, request: "GET /nwaftest HTTP/1.1", host: "test-ib1"
пришлите, пожалуйста, список файлов /etc/nginx/conf.d и содержимое этих файлов
 

Jakut

Member
пришлите, пожалуйста, список файлов /etc/nginx/conf.d и содержимое этих файлов
Содержимое директории /etc/nginx/conf.d: cabinet.conf, default.conf.disabled, nwaf-api.conf, test-IB1.conf, your_domain.conf.
Добавил обновленный error.log.
##########################################
## Nemesida WAF Cabinet
##########################################

## Cabinet proxy
server {

listen 0.0.0.0:80;
charset utf-8;


location / {
return 301 /waf/personal/;
}

location /waf/personal/static/ {
alias /var/www/app/main/static/;
}

location /waf/personal/ {
proxy_pass http://127.0.0.1:8888/;
include proxy_params;
}

}
##########################################


##########################################
## Cabinet upstream
##########################################

server {

listen 127.0.0.1:8888;

location / {
uwsgi_pass django;
include uwsgi_params;
}

}

upstream django {
server unix:/var/www/app/cabinet.sock;
}

##########################################
server {
listen 80;
server_name localhost;

#access_log /var/log/nginx/host.access.log main;

location / {
root /usr/share/nginx/html;
index index.html index.htm;
}

#error_page 404 /404.html;

# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
}

# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
##########################################
## Nemesida WAF API
##########################################

server {

listen 8080;
root /var/www/html;

uwsgi_read_timeout 600s;
uwsgi_send_timeout 600s;
uwsgi_connect_timeout 120s;
uwsgi_ignore_client_abort on;

location /nw-api/ {
alias /var/www/nw-api/;
include uwsgi_params;
uwsgi_pass unix:/var/www/nw-api/nw-api.sock;
}

}
server {
listen 80;
listen [::]:80;

root /var/www/test-IB1/html;
index index.html index.htm index.nginx-debian.html;

server_name test-IB1;

location / {
try_files $uri $uri/ =404;
}
}
server {
listen 80;
listen [::]:80;

root /var/www/your_domain/html;
index index.html index.htm index.nginx-debian.html;

server_name your_domain www.your_domain;

location / {
try_files $uri $uri/ =404;
}
}
2022/03/24 11:20:29 [error] 1604#1604: *12 Nemesida WAF: the request 267a7de0f8cddfc3f7cb411f83998633 blocked by rule ID 1 in zone URL, client: 10.5.97.182, server: your_domain, request: "GET /nwaftest HTTP/1.1", host: "your_domain"
2022/03/24 11:20:36 [error] 1604#1604: *16 Nemesida WAF: the request 7d578549c8fca03fc44ad5252be9899d blocked by rule ID 1 in zone URL, client: 10.5.97.182, server: test-ib1, request: "GET /nwaftest HTTP/1.1", host: "test-ib1"
2022/03/24 11:39:03 [notice] 1141#1141: signal 15 (SIGTERM) received from 82829, exiting
2022/03/24 11:39:03 [notice] 1604#1604: exiting
2022/03/24 11:39:03 [notice] 1605#1605: exiting
2022/03/24 11:39:04 [notice] 1141#1141: signal 15 (SIGTERM) received from 1, exiting
2022/03/24 11:39:04 [notice] 1605#1605: signal 15 (SIGTERM) received from 1, exiting
2022/03/24 11:39:04 [notice] 1604#1604: signal 15 (SIGTERM) received from 1, exiting
2022/03/24 11:39:04 [notice] 1141#1141: signal 14 (SIGALRM) received
2022/03/24 11:39:04 [notice] 1141#1141: signal 14 (SIGALRM) received
2022/03/24 11:39:04 [notice] 1141#1141: signal 14 (SIGALRM) received
2022/03/24 11:39:04 [notice] 1141#1141: signal 14 (SIGALRM) received
2022/03/24 11:39:05 [notice] 1141#1141: signal 14 (SIGALRM) received
2022/03/24 11:39:07 [notice] 1141#1141: signal 14 (SIGALRM) received
2022/03/24 11:39:07 [notice] 1141#1141: signal 17 (SIGCHLD) received from 1605
2022/03/24 11:39:07 [alert] 1141#1141: worker process 1605 exited on signal 9
2022/03/24 11:39:07 [notice] 1141#1141: signal 29 (SIGIO) received
2022/03/24 11:39:07 [notice] 1141#1141: signal 17 (SIGCHLD) received from 1604
2022/03/24 11:39:07 [alert] 1141#1141: worker process 1604 exited on signal 9
2022/03/24 11:39:07 [notice] 1141#1141: exit
2022/03/24 07:39:30 [notice] 1097#1097: Nemesida WAF: the parameter "nwaf_mla" is valid only in the commercial version and will be ignored in Nemesida WAF Free in /etc/nginx/nginx.conf:42
2022/03/24 07:39:30 [notice] 1097#1097: using the "epoll" event method
2022/03/24 07:39:30 [notice] 1097#1097: nginx/1.20.2
2022/03/24 07:39:30 [notice] 1097#1097: built by gcc 8.5.0 20210514 (Red Hat 8.5.0-4) (GCC)
2022/03/24 07:39:30 [notice] 1097#1097: OS: Linux 4.18.0-348.7.1.el8_5.x86_64
2022/03/24 07:39:30 [notice] 1097#1097: getrlimit(RLIMIT_NOFILE): 1024:262144
2022/03/24 07:39:30 [notice] 1133#1133: start worker processes
2022/03/24 07:39:30 [notice] 1133#1133: start worker process 1137
2022/03/24 07:39:30 [notice] 1133#1133: start worker process 1138
2022/03/24 07:39:30 [error] 1138#1138: Nemesida WAF Free activated
2022/03/24 07:39:32 [error] 1137#1191: Nemesida WAF: unable to connect to the RabbitMQ
2022/03/24 07:39:33 [error] 1138#1155: Nemesida WAF: unable to connect to the RabbitMQ
2022/03/24 11:39:43 [info] 1574#1574: Nemesida WAF: UUID: b77a672c1d83fc5c84396aebd6578860. Load from rules.bin: BL: 419 URL, 352 ARGS, 286 Headers, 313 Body; WL: 4 URL, 6 ARGS, 10 Headers, 4 Body; LM: 0 URL, 0 ARGS, 0 Headers, 0 Body. Processed in /etc/nginx/nginx.conf:42
2022/03/24 11:39:43 [info] 1574#1574: Nemesida WAF Free activated. Processed in /etc/nginx/nginx.conf:42
2022/03/24 11:39:43 [info] 1574#1574: Nemesida WAF: the parameter "nwaf_mla" is valid only in the commercial version and will be ignored in Nemesida WAF Free in /etc/nginx/nginx.conf:42
2022/03/24 11:39:43 [notice] 1133#1133: signal 1 (SIGHUP) received from 1586, reconfiguring
2022/03/24 11:39:43 [notice] 1133#1133: reconfiguring
2022/03/24 11:39:43 [notice] 1133#1133: Nemesida WAF: the parameter "nwaf_mla" is valid only in the commercial version and will be ignored in Nemesida WAF Free in /etc/nginx/nginx.conf:42
2022/03/24 11:39:43 [notice] 1133#1133: using the "epoll" event method
2022/03/24 11:39:43 [notice] 1133#1133: start worker processes
2022/03/24 11:39:43 [notice] 1133#1133: start worker process 1589
2022/03/24 11:39:43 [notice] 1133#1133: start worker process 1590
2022/03/24 11:39:43 [notice] 1137#1137: gracefully shutting down
2022/03/24 11:39:43 [notice] 1138#1138: gracefully shutting down
2022/03/24 11:39:43 [notice] 1137#1137: exiting
2022/03/24 11:39:43 [notice] 1138#1138: exiting
2022/03/24 11:39:43 [notice] 1137#1137: exit
2022/03/24 11:39:44 [notice] 1133#1133: signal 17 (SIGCHLD) received from 1137
2022/03/24 11:39:44 [notice] 1133#1133: worker process 1137 exited with code 0
2022/03/24 11:39:44 [notice] 1133#1133: signal 29 (SIGIO) received
2022/03/24 11:39:43 [notice] 1138#1138: exit
2022/03/24 11:39:45 [notice] 1133#1133: signal 17 (SIGCHLD) received from 1138
2022/03/24 11:39:45 [notice] 1133#1133: worker process 1138 exited with code 0
2022/03/24 11:39:45 [notice] 1133#1133: signal 29 (SIGIO) received
 

rr

Administrator
Спасибо,

проблема возникает, поскольку вы разместили файл test-IB1.conf, который так же, как и ЛК, использует 80 порт.

Решение:
- сменить порт с 80 на 88 для test-IB1.conf (или для ЛК) и перезапустить nginx
 

Jakut

Member
Спасибо,

проблема возникает, поскольку вы разместили файл test-IB1.conf, который так же, как и ЛК, использует 80 порт.

Решение:
- сменить порт с 80 на 88 для test-IB1.conf (или для ЛК) и перезапустить nginx
Сменил порт в cabinet.conf на 88, в your_domain.conf на 81 и добавил 88 порт в firewalld и заработало!
Большое спасибо за помощь!
 
  • Like
Reactions: rr
Top