[error] open() failed (2: No such file or directory)

[kklouzal]

I'm getting these errors in my System Logs for about 10% of the sites I visit.

Oct 24 01:57:24	pfsense.localdomain		nginx: 2017/10/24 01:57:24 [error] 54655#100207: *18 open() "/usr/local/www/jslog/log.png" failed (2: No such file or directory), client: 10.10.10.1, server: , request: "GET /jslog/log.png?version=-bucket5&location=http%3A%2F%2Fstore.supermicro.com%2Fheatsink%2F1u-active-pro&referrer=https%3A%2F%2Fwww.goo&message=%23using_theme.artsy_albatross%20%23using_theme%20&tabname=oktab1957985944333016&conversation_id=XeeN8BzPMGoSZWZC1E9pr0W80JEzAjro&visitor_id=JmZaozgAzpscZE2I1E9pr0W80JE6Vao3&site_id=5194-535-10-9141&bucket=bucket5&level=count×tamp=1508835442069&properties=%7B%7D&recent_logs=%5B%5D HTTP/1.1", host: "log.olark.com", referrer: "http://store.supermicro.com/heatsink/1u-active-proprietary-cpu-cooler-snk-p0049a4.html"
Oct 25 04:28:31	pfsense.localdomain		nginx: 2017/10/25 04:28:31 [error] 56712#100209: *31 open() "/usr/local/www/js/651393494.js" failed (2: No such file or directory), client: 10.10.10.1, server: , request: "GET /js/651393494.js HTTP/1.1", host: "cdn.optimizely.com", referrer: "http://www.stumbleupon.com/"
Oct 25 04:28:31	pfsense.localdomain		nginx: 2017/10/25 04:28:31 [error] 56431#100237: *30 open() "/usr/local/www/1/widgets.js" failed (2: No such file or directory), client: 10.10.10.1, server: , request: "GET /1/widgets.js HTTP/1.1", host: "platform.stumbleupon.com", referrer: "http://www.stumbleupon.com/"

I've made a post in the pfBlockerNG forum since the error references 10.10.10.1 however I've been referred over here.

Does anyone know whats going on here? Sites that raise this error take a considerable amount of time to present to the browser.

[doktornotor]

@kklouzal:

I've made a post in the pfBlockerNG forum since the error references 10.10.10.1 however I've been referred over here.

No idea why you have been referred here. nginx is not a proxy package.

[kklouzal]

I deleted the squid package since it was caching less than 5% of traffic anyways. But just in case your curious I revisited a bunch of the sites from the log that were throwing the error and it never came up once.