[GH-ISSUE #4099] error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go value of type v1.ClientConfig

gitea-mirror commented

2026-05-05 14:05:15 -06:00

Owner

Copy link

Originally created by @yinqinghe on GitHub (Mar 24, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4099

Bug Description

error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go value of type v1.ClientConfig

frpc Version

v0.56.0

frps Version

v0.56.0

System Architecture

linux/amd64

Configurations

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 @yinqinghe on GitHub (Mar 24, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4099 ### Bug Description error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go value of type v1.ClientConfig ### frpc Version v0.56.0 ### frps Version v0.56.0 ### System Architecture linux/amd64 ### Configurations ![image](https://github.com/fatedier/frp/assets/70678389/a5d7e526-d6b7-49a8-8ae5-db739c5026b1) ### Logs ![image](https://github.com/fatedier/frp/assets/70678389/a2a4b1ae-2633-4e2e-ab88-73cb6b9ead31) ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:05:15 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:05:18 -06:00

Author

Owner

Copy link

@xqzr commented on GitHub (Mar 25, 2024):

~~[common]~~

@xqzr commented on GitHub (Mar 25, 2024): ~~`[common]`~~

gitea-mirror commented

2026-05-05 14:05:19 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 16, 2024):

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

@github-actions[bot] commented on GitHub (Apr 16, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified