[GH-ISSUE #5134] [Feature Request] cannot start FRP on claw cloud #4015

Closed
opened 2026-05-05 14:33:04 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @yx86 on GitHub (Jan 17, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5134

Describe the feature request

I tried to create the frp server via run.claw.cloud and I got the following error:

500:services \"frp-bgfxdeys-nodeport\" is forbidden: 
exceeded quota: quota-ns-ne5ruahf, requested: services.nodeports=2, used: services.nodeports=1, limited: services.nodeports=1

it seems that run.claw.cloud limits the free app port numbers. but the existing FRP template needs 2 ports to run 80 and 7500

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @yx86 on GitHub (Jan 17, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5134 ### Describe the feature request I tried to create the frp server via run.claw.cloud and I got the following error: ``` 500:services \"frp-bgfxdeys-nodeport\" is forbidden: exceeded quota: quota-ns-ne5ruahf, requested: services.nodeports=2, used: services.nodeports=1, limited: services.nodeports=1 ``` it seems that run.claw.cloud limits the free app port numbers. but the existing FRP template needs 2 ports to run `80` and `7500` ### Describe alternatives you've considered _No response_ ### 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:33:04 -06:00
Author
Owner

@fatedier commented on GitHub (Jan 20, 2026):

This error is not caused by frp itself. The Kubernetes namespace has a NodePort quota of 1, but the template tries to create a Service with two NodePorts (80 and 7500), so it is rejected. Please remove/disable the public Dashboard port (7500) or expose only one port, or upgrade the plan to get more NodePorts.

<!-- gh-comment-id:3770767347 --> @fatedier commented on GitHub (Jan 20, 2026): This error is not caused by frp itself. The Kubernetes namespace has a NodePort quota of 1, but the template tries to create a Service with two NodePorts (80 and 7500), so it is rejected. Please remove/disable the public Dashboard port (7500) or expose only one port, or upgrade the plan to get more NodePorts.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 4, 2026):

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

<!-- gh-comment-id:3844612167 --> @github-actions[bot] commented on GitHub (Feb 4, 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#4015
No description provided.