Connector: 404 - file not found for file: * - Endless amount of this is being logged on the Cloud environment. Not locally. Edge Health Probe causing the issue?
0
Hi, We have millions and millions of this in our logs – at least 5 per second! Does anybody have an idea where to look for what is causing this? We’re running Mx 8.18.1. ==== Update 3 (thanks to the people reading this and thinking with me :-) After starting the TEST env, this what you see: 12:26:48 PMAPPINFOConfiguration: Updating configuration... 12:26:49 PMAPPINFOStorageS3: Endpoint set to: s3.eu-central-1.amazonaws.com/cf-shared-prod-1-eu-central-1 12:26:49 PMSYSINFOContainer became healthy 12:26:49 PMREQINFOvdl-vbc-parts-test.mendixcloud.com - [2021-07-09T10:26:49.432188313Z] "GET /* HTTP/1.1" 502 0 150 "-" "Edge Health Probe" "10.10.11.89:52140" "10.10.136.29:61110" x_forwarded_for:"147.243.117.7, 10.10.11.89" x_forwarded_proto:"http" vcap_request_id:"80b0fbb6-0993-4745-74fd-90d6cbccb5f7" response_time:0.008587 gorouter_time:0.000288 app_id:"5ffe9623-d129-4b26-9475-66cd41e80456" app_index:"0" x_cf_routererror:"-" x_b3_traceid:"6bd096c781fecbc3" x_b3_spanid:"6bd096c781fecbc3" x_b3_parentspanid:"-" b3:"6bd096c781fecbc3-6bd096c781fecbc3" 12:26:49 PMAPPINFO2021/07/09 10:26:49 [error] 93#0: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 147.243.117.7, server: _, request: "GET /* HTTP/1.1", upstream: "http://127.0.0.1:8081/*", host: "vdl-vbc-parts-test.mendixcloud.com" 12:26:49 PMAPPINFO2021/07/09 10:26:49 [error] 93#0: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 147.243.162.7, server: _, request: "GET /* HTTP/1.1", upstream: "http://127.0.0.1:8081/*", host: "vdl-vbc-parts-test.mendixcloud.com" 12:26:49 PMAPPINFO2021/07/09 10:26:49 [error] 93#0: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 147.243.23.135, server: _, request: "GET /* HTTP/1.1", upstream: "http://127.0.0.1:8081/*", host: "vdl-vbc-parts-test.mendixcloud.com" 12:26:49 PMAPPINFOServices: Adding 0 authority certificate(s) 12:26:49 PMAPPINFOConfiguration: Configuration updated. Here I also see a reference upstream: "http://127.0.0.1:8081/*". Does that make sense? It looks like the Edge Health Probe thingy started here and started directly after the Container became healthy logline. Is there a link between the two? ==== Second update: Robert pointed to Azure health check. We’re now thinking about this but … how … If anybody could just fire these requests to our app, how to find the source – who to ask to please, please stop firing these requests :-) The issue is really only our TEST env. ACCP and PROD are clean. Another thing, if this kind bombardments can just happen and just every other system could do this, isn’t there a way to block this? I did see whitelisting is possible, is it also possible to blacklist IP addresses or is this not the way to approach this? ==== Update: Robert showed me how to show the HTTP reqs in the log and now I see more info. I guess it means the environment is bombarded with requests, but this is a terrain I’m not familiar with. Below a picture of the logs. 11:04:45 AMAPPERRORConnector: 404 - file not found for file: * 11:04:45 AMAPPERRORConnector: 404 - file not found for file: * 11:04:46 AMAPPERRORConnector: 404 - file not found for file: * 11:04:45 AMAPPERRORConnector: 404 - file not found for file: * 11:04:46 AMAPPERRORConnector: 404 - file not found for file: *
asked
Toon Verschoor - Deloitte
2 answers
1
This looks like it’s Azure Front Door making the requests. Are you hosted on Azure, or using the functionality for anything?
Might it be that you did a restore from production or accp to the test environment without the filedocuments? Because it could simply be a file that is present in accp and production but due to a database only restore to test that it is not available in the test environment. The * character is strange though. Normally you would see some filename here like favicon.ico or something like that.