[Feature Request] Allow differentiation of Identification of login from WEB vs. IRC #506

New Issue

2026-10-05T04:25:51+02:00

adam commented

2026-10-05 04:25:51 +02:00

Adminlog and current functions currently identify failed logins by IP, but it does not state whether it's IRC based or webadmin based. This can be confusing for those of us who put stuff in front of the web interface to point to a different IP.

Is it possible to somehow add into the system (for adminlog and failed login attempt data when connected to ZNC) a way to say whether the failed login was from web or irc?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10288206-feature-request-allow-differentiation-of-identification-of-login-from-web-vs-irc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Adminlog and current functions currently identify failed logins by IP, but it does not state whether it's IRC based or webadmin based. This can be confusing for those of us who put stuff in front of the web interface to point to a different IP. Is it possible to somehow add into the system (for adminlog and failed login attempt data when connected to ZNC) a way to say whether the failed login was from web or irc? ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10288206-feature-request-allow-differentiation-of-identification-of-login-from-web-vs-irc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam commented

2026-10-05 04:25:51 +02:00

This is good. 👍

Depending on what kind of proxy or what-have-you you have in front of the webui, the latest versions of ZNC (since 1.6, I believe) understand X-Forwarded-For headers. If the adminlog module or some other part of ZNC doesn't use the IP from that header when present, that's a bug.

This is good. :+1: Depending on what kind of proxy or what-have-you you have in front of the webui, the latest versions of ZNC (since 1.6, I believe) understand `X-Forwarded-For` headers. If the adminlog module or some other part of ZNC doesn't use the IP from that header when present, that's a bug.

adam commented

2026-10-05 04:25:52 +02:00

This could also be useful if there's nothing in front either, such as someone using webadmin vs. irc, etc. whether X-Forwarded-For exists or not.

This could also be useful if there's nothing in front either, such as someone using webadmin vs. irc, etc. whether `X-Forwarded-For` exists or not.

adam commented

2026-10-05 04:25:53 +02:00

Of course, yes. Was just trying to be helpful in case you weren't even getting the actual client IP. This feature request gets a 👍 from me no matter what.

Of course, yes. Was just trying to be helpful in case you weren't even getting the actual client IP. This feature request gets a :+1: from me no matter what.

adam referenced this issue

2026-10-05 04:27:02 +02:00

Add support for IRCv3.2 message tags #519

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#506