starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-25 03:14:50 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

Logging and Fail2ban support #217

New Issue
Closed
opened 2026-02-04 17:53:48 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 17:53:48 +03:00
Owner
Copy Link

Originally created by @StevenJCorreia on GitHub (Aug 20, 2022).

Hey all,

Background

I started hosting and using Planka on my home server recently and I was concerned that there was no support to expose the logs, specifically failed authentication attempts, and point Fail2ban to them in order to automatically ban people attempting to get into accounts.

Proposed Features

  • Log failed authentication attempts to a logfile
    • Invalid username/email
    • Invalid password
  • Expose a logfile directory to host machine so server admin can point Fail2ban to them
  • Update any related documentation to include feature once implemented

Implementation

I already have a working version of what is requested above, but I would like to hear others' opinions regarding this feature before a PR is opened.

Originally created by @StevenJCorreia on GitHub (Aug 20, 2022). Hey all, # Background I started hosting and using Planka on my home server recently and I was concerned that there was no support to expose the logs, specifically failed authentication attempts, and point [Fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to them in order to automatically ban people attempting to get into accounts. # Proposed Features - Log failed authentication attempts to a logfile - Invalid username/email - Invalid password - Expose a logfile directory to host machine so server admin can point Fail2ban to them - Update any related documentation to include feature once implemented # Implementation I already have a working version of what is requested above, but I would like to hear others' opinions regarding this feature before a PR is opened.
OVERLORD commented 2026-02-04 17:54:03 +03:00
Author
Owner
Copy Link

@nickbe commented on GitHub (Aug 21, 2022):

This is simply something that was not important at the time. Please go ahead and make a pull request for this. We will review the log format then....

@nickbe commented on GitHub (Aug 21, 2022): This is simply something that was not important at the time. Please go ahead and make a pull request for this. We will review the log format then....
OVERLORD commented 2026-02-04 17:54:10 +03:00
Author
Owner
Copy Link

@StevenJCorreia commented on GitHub (Aug 21, 2022):

@nickbe PR opened. (#284)

@StevenJCorreia commented on GitHub (Aug 21, 2022): @nickbe PR opened. (#284)
OVERLORD commented 2026-02-04 17:54:17 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Aug 23, 2022):

🙏

@meltyshev commented on GitHub (Aug 23, 2022): 🙏
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#217
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?