[GH-ISSUE #5075] 0.65版本linux/386的FRPC镜像无法识别配置文件0.64可以 #3987

Closed
opened 2026-05-05 14:32:07 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @MrLiuGangQiang on GitHub (Nov 25, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5075

Bug Description

同样的frpc配置文件用linux/386的镜像0.64可以启动0.65不行直接未识别配置文件,用0.65的windows版本的frpc测试过是可以识别的

frpc Version

0.65

frps Version

0.65

System Architecture

linux/386

Configurations

auth.method = "token"
auth.token = "xxxxx"
auth.additionalScopes = ["HeartBeats"]
serverAddr = "xxx"
serverPort = 26001

transport.protocol = "tcp"
transport.tcpMuxKeepaliveInterval = 30
transport.heartbeatInterval = 30
transport.tls.enable = true
transport.tls.certFile = "/etc/frp/cert/xx.pem"
transport.tls.keyFile = "/etc/frp/cert/xx.key"
transport.tls.serverName = "frp.lfans.cn"

user = "办公室"
proxies
name = "公司路由.WEB"
type = "tcp"
localIP = "10.168.120.254"
localPort = 443
remotePort = 28000
transport.useEncryption = true
transport.useCompression = true

Logs

没有日志

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 @MrLiuGangQiang on GitHub (Nov 25, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5075 ### Bug Description 同样的frpc配置文件用linux/386的镜像0.64可以启动0.65不行直接未识别配置文件,用0.65的windows版本的frpc测试过是可以识别的 ### frpc Version 0.65 ### frps Version 0.65 ### System Architecture linux/386 ### Configurations auth.method = "token" auth.token = "xxxxx" auth.additionalScopes = ["HeartBeats"] serverAddr = "xxx" serverPort = 26001 transport.protocol = "tcp" transport.tcpMuxKeepaliveInterval = 30 transport.heartbeatInterval = 30 transport.tls.enable = true transport.tls.certFile = "/etc/frp/cert/xx.pem" transport.tls.keyFile = "/etc/frp/cert/xx.key" transport.tls.serverName = "frp.lfans.cn" user = "办公室" [[proxies]] name = "公司路由.WEB" type = "tcp" localIP = "10.168.120.254" localPort = 443 remotePort = 28000 transport.useEncryption = true transport.useCompression = true ### Logs 没有日志 ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [x] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 14:32:07 -06:00
Author
Owner

@chapulin2760-art commented on GitHub (Nov 25, 2025):

Descripción del error

同样的frpc配置文件用linux/386的镜像0.64可以启动0.65不行直接未识别配置文件,用0.65的windows版本的frpc测试过是可以识别的

Versión frpc

0,65

Versión frps

0,65

Arquitectura del sistema

Linux/386

Configuraciones

auth.method = "token" auth.token = "xxxxx" auth.additionalScopes = ["HeartBeats"] serverAddr = "xxx" serverPort = 26001

transporte.protocolo = "tcp" transporte.tcpMuxKeepaliveInterval = 30 transporte.heartbeatInterval = 30 transporte.tls.enable = verdadero transporte.tls.certFile = "/etc/frp/cert/xx.pem" transporte.tls.keyFile = "/etc/frp/cert/xx.key" transporte.tls.serverName = "frp.lfans.cn"

usuario = "办公室" proxies nombre = "公司路由.WEB" tipo = "tcp" localIP = "10.168.120.254" localPort = 443 puerto remoto = 28000 transport.useEncryption = true transport.useCompression = true

Registros

没有日志

Pasos para reproducir

...

Zona afectada

  • Documentos[x] Instalación[ ] Rendimiento y escalabilidad[ ] Seguridad[ ] Experiencia de usuario[ ] Prueba y lanzamiento[ ] Infraestructura para desarrolladores[ ] Complemento de cliente[ ] Complemento de servidor[ ] Extensiones[ ] Otros
<!-- gh-comment-id:3576285367 --> @chapulin2760-art commented on GitHub (Nov 25, 2025): > ### Descripción del error > 同样的frpc配置文件用linux/386的镜像0.64可以启动0.65不行直接未识别配置文件,用0.65的windows版本的frpc测试过是可以识别的 > > ### Versión frpc > 0,65 > > ### Versión frps > 0,65 > > ### Arquitectura del sistema > Linux/386 > > ### Configuraciones > auth.method = "token" auth.token = "xxxxx" auth.additionalScopes = ["HeartBeats"] serverAddr = "xxx" serverPort = 26001 > > transporte.protocolo = "tcp" transporte.tcpMuxKeepaliveInterval = 30 transporte.heartbeatInterval = 30 transporte.tls.enable = verdadero transporte.tls.certFile = "/etc/frp/cert/xx.pem" transporte.tls.keyFile = "/etc/frp/cert/xx.key" transporte.tls.serverName = "frp.lfans.cn" > > usuario = "办公室" [[proxies]] nombre = "公司路由.WEB" tipo = "tcp" localIP = "10.168.120.254" localPort = 443 puerto remoto = 28000 transport.useEncryption = true transport.useCompression = true > > ### Registros > 没有日志 > > ### Pasos para reproducir > > ... > > ### Zona afectada > * [ ] Documentos[x] Instalación[ ] Rendimiento y escalabilidad[ ] Seguridad[ ] Experiencia de usuario[ ] Prueba y lanzamiento[ ] Infraestructura para desarrolladores[ ] Complemento de cliente[ ] Complemento de servidor[ ] Extensiones[ ] Otros
Author
Owner

@github-actions[bot] commented on GitHub (Dec 10, 2025):

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

<!-- gh-comment-id:3634874571 --> @github-actions[bot] commented on GitHub (Dec 10, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@chapulin2760-art commented on GitHub (Dec 10, 2025):

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

<!-- gh-comment-id:3638372324 --> @chapulin2760-art commented on GitHub (Dec 10, 2025): > Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@chapulin2760-art commented on GitHub (Dec 19, 2025):

Descripción del error

同样的frpc配置文件用linux/386的镜像0.64可以启动0.65不行直接未识别配置文件,用0.65的windows版本的frpc测试过是可以识别的

Versión frpc

0,65

Versión frps

0,65

Arquitectura del sistema

Linux/386

Configuraciones

auth.method = "token" auth.token = "xxxxx" auth.additionalScopes = ["HeartBeats"] serverAddr = "xxx" serverPort = 26001

transporte.protocolo = "tcp" transporte.tcpMuxKeepaliveInterval = 30 transporte.heartbeatInterval = 30 transporte.tls.enable = verdadero transporte.tls.certFile = "/etc/frp/cert/xx.pem" transporte.tls.keyFile = "/etc/frp/cert/xx.key" transporte.tls.serverName = "frp.lfans.cn"

usuario = "办公室" proxies nombre = "公司路由.WEB" tipo = "tcp" localIP = "10.168.120.254" localPort = 443 puerto remoto = 28000 transport.useEncryption = true transport.useCompression = true

Registros

没有日志

Pasos para reproducir

...

Zona afectada

  • Documentos[x] Instalación[ ] Rendimiento y escalabilidad[ ] Seguridad[ ] Experiencia de usuario[ ] Prueba y lanzamiento[ ] Infraestructura para desarrolladores[ ] Complemento de cliente[ ] Complemento de servidor[ ] Extensiones[ ] Otros
<!-- gh-comment-id:3673635355 --> @chapulin2760-art commented on GitHub (Dec 19, 2025): > ### Descripción del error > 同样的frpc配置文件用linux/386的镜像0.64可以启动0.65不行直接未识别配置文件,用0.65的windows版本的frpc测试过是可以识别的 > > ### Versión frpc > 0,65 > > ### Versión frps > 0,65 > > ### Arquitectura del sistema > Linux/386 > > ### Configuraciones > auth.method = "token" auth.token = "xxxxx" auth.additionalScopes = ["HeartBeats"] serverAddr = "xxx" serverPort = 26001 > > transporte.protocolo = "tcp" transporte.tcpMuxKeepaliveInterval = 30 transporte.heartbeatInterval = 30 transporte.tls.enable = verdadero transporte.tls.certFile = "/etc/frp/cert/xx.pem" transporte.tls.keyFile = "/etc/frp/cert/xx.key" transporte.tls.serverName = "frp.lfans.cn" > > usuario = "办公室" [[proxies]] nombre = "公司路由.WEB" tipo = "tcp" localIP = "10.168.120.254" localPort = 443 puerto remoto = 28000 transport.useEncryption = true transport.useCompression = true > > ### Registros > 没有日志 > > ### Pasos para reproducir > > ... > > ### Zona afectada > * [ ] Documentos[x] Instalación[ ] Rendimiento y escalabilidad[ ] Seguridad[ ] Experiencia de usuario[ ] Prueba y lanzamiento[ ] Infraestructura para desarrolladores[ ] Complemento de cliente[ ] Complemento de servidor[ ] Extensiones[ ] Otros
Author
Owner

@github-actions[bot] commented on GitHub (Jan 3, 2026):

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

<!-- gh-comment-id:3706541024 --> @github-actions[bot] commented on GitHub (Jan 3, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d 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#3987
No description provided.