[GH-ISSUE #2702] frp代理Jupyter Hub（tljh），可以访问服务网页但是无法选择Python内核

gitea-mirror commented

2026-05-05 13:23:16 -06:00

Owner

Originally created by @StevendeLiu on GitHub (Dec 15, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2702

Bug Description

使用frp来代理The littlest Jupyterhub服务，使用代理用的A记录可以访问提供服务的网页，但是无法选择Kernel，也无法进入控制面板来Start、Stop服务。
没有发现异常日志。
另，进来使用Frp代理Jupyter Lab也时常出现503问题或是Server Connection Error，日志正常。

frpc Version

0.37.1

frps Version

0.38.0

System Architecture

Configurations

使用如下的配置进行代理The littlest Jupyterhub服务

[web-desk-epyc-3090-i-jupyter-tjlh-hub]
type = http
local_port = 80
custom_domains = jupyterhub.***.**
host_header_rewrite = localhost

使用连接可以访问提供服务的网页，但是无法选择Kernel，也无法进入控制面板来Start、Stop服务
没有发现异常日志

Logs

No response

Steps to reproduce

安装The littlest Jupyter hub服务
代理本地80端口
使用代理的A记录访问该服务
...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @StevendeLiu on GitHub (Dec 15, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2702 ### Bug Description 使用frp来代理The littlest Jupyterhub服务，使用代理用的A记录可以访问提供服务的网页，但是无法选择Kernel，也无法进入控制面板来Start、Stop服务。没有发现异常日志。另，进来使用Frp代理Jupyter Lab也时常出现503问题或是Server Connection Error，日志正常。 ### frpc Version 0.37.1 ### frps Version 0.38.0 ### System Architecture ln ### Configurations 使用如下的配置进行代理The littlest Jupyterhub服务 ```ini [web-desk-epyc-3090-i-jupyter-tjlh-hub] type = http local_port = 80 custom_domains = jupyterhub.***.** host_header_rewrite = localhost ``` 使用连接可以访问提供服务的网页，但是无法选择Kernel，也无法进入控制面板来Start、Stop服务没有发现异常日志 ### Logs _No response_ ### Steps to reproduce 1. 安装The littlest Jupyter hub服务 2. 代理本地80端口 3. 使用代理的A记录访问该服务 ... ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:23:16 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:23:19 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 15, 2022):

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

@github-actions[bot] commented on GitHub (Jan 15, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.