Bug #6027

Captive portal 404 log spam

Added by Orsiris de Jong about 4 years ago. Updated about 4 years ago.

Very Low
Captive Portal
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:



Minor bug here, when opening the captive portal, there's no favicon.ico so nginx complains:

nginx: 2016/03/25 11:53:39 [error] 10501#0: *6 open() "/usr/local/captiveportal/favicon.ico" failed (2: No such file or directory), client:, server: , request: "GET /favicon.ico HTTP/1.1", host: ""

As uploading files rename all files to captiveportal-[filename], this can't be solved via GUI.
I indeed uploaded a favicon.ico to /usr/local/captiveportal which fixed the error message.

What about putting a default favicon.ico there ?
Or a gui option to not rename a file if it's called favicon.ico ? I'd be glad to make a PR on git.


Associated revisions

Revision 2f004405 (diff)
Added by Chris Buechler about 4 years ago

Don't log 404s for captive portal. Ticket #6027


#1 Updated by Chris Buechler about 4 years ago

  • Subject changed from Captive portal missing favicon to Captive portal 404 log spam
  • Status changed from New to Resolved
  • Assignee set to Chris Buechler
  • Target version set to 2.3

It's never had one, lighttpd just didn't log 404s there where nginx does. Turning this ticket into that issue since that'll just generate unnecessary log spam.

I just pushed a change to disable 404 logging for captive portal.

I don't think a favicon is important to accommodate. Those who want one can manually upload it. But I'd be fine with not renaming favicon.ico files uploaded to the CP file manager. If you'd like to submit a PR for that, we can get that merged post-2.3.

#2 Updated by Orsiris de Jong about 4 years ago

Great, no more 404 error logs! PR #2799 created :)

#3 Updated by Jose Luis Duran about 4 years ago

What you can do is, in the head of your custom captive portal page, add:

<link rel="icon" href="captiveportal-favicon.ico">

Also available in: Atom PDF