Por que minha instância do Discourse está fazendo essas chamadas

Suporte
1

Acabei de notar logs da minha instância, abaixo está um erro. Por favor, ajude-me a entender o que isso significa. Agradeço antecipadamente.

Estes são alguns links adicionais

“/news/wp-includes/wlwmanifest.xml”
“/2018/wp-includes/wlwmanifest.xml”
“/2019/wp-includes/wlwmanifest.xml”
“/shop/wp-includes/wlwmanifest.xml”
“/wp1/wp-includes/wlwmanifest.xml”
“/test/wp-includes/wlwmanifest.xml”
“/media/wp-includes/wlwmanifest.xml”
“/wp2/wp-includes/wlwmanifest.xml”
“/site/wp-includes/wlwmanifest.xml”
“/cms/wp-includes/wlwmanifest.xml”
“/sito/wp-includes/wlwmanifest.xml”


Mensagem (14 cópias relatadas)

[default] ActionController::RoutingError (Nenhuma rota corresponde a [GET] "/site/wp-includes/wlwmanifest.xml")
lib/middleware/default_headers.rb:13:in `call'
config/initializers/100-quiet_logger.rb:20:in `call'
config/initializers/100-silence_logger.rb:29:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
lib/middleware/processing_request.rb:12:in `call'
lib/middleware/request_tracker.rb:410:in `call'


Backtrace

actionpack (8.0.2.1) lib/action_dispatch/middleware/debug_exceptions.rb:35:in `call'
actionpack (8.0.2.1) lib/action_dispatch/middleware/show_exceptions.rb:32:in `call'
logster (2.20.1) lib/logster/middleware/reporter.rb:40:in `call'
lib/middleware/default_headers.rb:13:in `call'
railties (8.0.2.1) lib/rails/rack/logger.rb:41:in `call_app'
railties (8.0.2.1) lib/rails/rack/logger.rb:29:in `call'
config/initializers/100-quiet_logger.rb:20:in `call'
config/initializers/100-silence_logger.rb:29:in `call'
actionpack (8.0.2.1) lib/action_dispatch/middleware/request_id.rb:34:in `call'
lib/middleware/enforce_hostname.rb:23:in `call'
rack (2.2.17) lib/rack/method_override.rb:24:in `call'
rack (2.2.17) lib/rack/sendfile.rb:110:in `call'
rack-mini-profiler (4.0.1) lib/mini_profiler.rb:191:in `call'
lib/middleware/processing_request.rb:12:in `call'
message_bus (4.4.1) lib/message_bus/rack/middleware.rb:60:in `call'
lib/middleware/request_tracker.rb:410:in `call'
actionpack (8.0.2.1) lib/action_dispatch/middleware/remote_ip.rb:96:in `call'
rails_multisite (7.0.0) lib/rails_multisite/middleware.rb:26:in `call'
railties (8.0.2.1) lib/rails/engine.rb:535:in `call'
railties (8.0.2.1) lib/rails/railtie.rb:226:in `public_send'
railties (8.0.2.1) lib/rails/railtie.rb:226:in `method_missing'
rack (2.2.17) lib/rack/urlmap.rb:74:in `block in call'
rack (2.2.17) lib/rack/urlmap.rb:58:in `each'
rack (2.2.17) lib/rack/urlmap.rb:58:in `call'
unicorn (6.1.0) lib/unicorn/http_server.rb:634:in `process_client'
unicorn (6.1.0) lib/unicorn/http_server.rb:739:in `worker_loop'
unicorn (6.1.0) lib/unicorn/http_server.rb:547:in `spawn_missing_workers'
unicorn (6.1.0) lib/unicorn/http_server.rb:143:in `start'
unicorn (6.1.0) bin/unicorn:128:in `<top (required)>'
vendor/bundle/ruby/3.3.0/bin/unicorn:25:in `load'
vendor/bundle/ruby/3.3.0/bin/unicorn:25:in `<main>'
2

Porque alguns sites WordPress costumavam ter o seu endereço IP e as coisas ainda estão a aceder a essas páginas antigas?

3

Obrigado pela sua resposta rápida. Mas eu nunca tive nenhuma instância do WordPress. Mas, mais importante, devo me preocupar? Alguns desses logs estão atingindo mais de 100.

4

Bots criados por script kiddies estão atacando essas URLs? Apenas batendo. Irritante, mas nada mais.

2 curtidas
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.