[GH-ISSUE #4024] 使用type=“http”穿透http服务时 无法登出 #3184

Closed
opened 2026-05-05 14:03:36 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @NanoNM on GitHub (Feb 25, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4024

Bug Description

使用type=“http”穿透http服务时 管理器页面一直保持登录状态 手动删除cookie session也不行 手动登出也不行

frpc Version

0.54.0

frps Version

0.53.2

System Architecture

linux/amd64

Configurations

serverAddr = "xxx"
serverPort = 15443

auth.token = "xxx"

frps.toml

webServer.addr = "0.0.0.0"
webServer.port = 7000

dashboard 用户名密码,可选,默认为空

webServer.user = "admin"
webServer.password = "admin"

proxies
name = "unraid"
type = "http"
localPort = 80
customDomains = ["unraid.xxx.xxx"]
httpUser = "xxx"
httpPassword = "xxx"

Logs

No response

Steps to reproduce

...

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @NanoNM on GitHub (Feb 25, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4024 ### Bug Description 使用type=“http”穿透http服务时 管理器页面一直保持登录状态 手动删除cookie session也不行 手动登出也不行 ### frpc Version 0.54.0 ### frps Version 0.53.2 ### System Architecture linux/amd64 ### Configurations serverAddr = "xxx" serverPort = 15443 auth.token = "xxx" # frps.toml webServer.addr = "0.0.0.0" webServer.port = 7000 # dashboard 用户名密码,可选,默认为空 webServer.user = "admin" webServer.password = "admin" [[proxies]] name = "unraid" type = "http" localPort = 80 customDomains = ["unraid.xxx.xxx"] httpUser = "xxx" httpPassword = "xxx" ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [X] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:03:36 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 18, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:2002684827 --> @github-actions[bot] commented on GitHub (Mar 18, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3184
No description provided.