starred/EasyCLI
1
0
Fork 0
mirror of https://github.com/router-for-me/EasyCLI.git synced 2026-04-25 15:45:53 +03:00
Code Issues 15 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #6] 代理vpn时,好像不能运行这个软件 #4

New issue
Closed
opened 2026-02-27 16:46:44 +03:00 by kerem · 5 comments
kerem commented 2026-02-27 16:46:44 +03:00
Owner
Copy link

Originally created by @ZZZdragondYNGPHX on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/router-for-me/EasyCLI/issues/6

当我代理vpn时,会显示错误,然后软件重启,重新进入后会白屏无响应,只有任务管理器强制关闭才行,而且每一次都这样
Image

Image
Originally created by @ZZZdragondYNGPHX on GitHub (Oct 14, 2025). Original GitHub issue: https://github.com/router-for-me/EasyCLI/issues/6 当我代理vpn时,会显示错误,然后软件重启,重新进入后会白屏无响应,只有任务管理器强制关闭才行,而且每一次都这样 <img width="917" height="632" alt="Image" src="https://github.com/user-attachments/assets/53b9175d-cd2e-43ce-ac99-46301ee4283b" /> <img width="926" height="630" alt="Image" src="https://github.com/user-attachments/assets/321e0dba-edf2-4505-9fdf-10a4efc83878" />
kerem closed this issue 2026-02-27 16:46:44 +03:00
kerem commented 2026-02-27 16:46:44 +03:00
Author
Owner
Copy link

@benzntech commented on GitHub (Oct 22, 2025):

This issue appears to be related to the CLIProxyAPI port conflict. When using a VPN proxy, the application may fail to start properly if port 8317 is already in use.

Troubleshooting steps:

  1. Check if port 8317 is already occupied:

    • Windows: netstat -ano | findstr :8317
    • macOS/Linux: lsof -i :8317

  2. If a process is using port 8317, you can either:

    • Kill the existing process
    • Or configure EasyCLI to use a different port in the settings

  3. If the app becomes unresponsive (white screen), force quit and restart after ensuring port 8317 is available.

Could you share the error message you're seeing when the VPN is active? This will help identify the specific issue.

<!-- gh-comment-id:3433405226 --> @benzntech commented on GitHub (Oct 22, 2025): This issue appears to be related to the CLIProxyAPI port conflict. When using a VPN proxy, the application may fail to start properly if port 8317 is already in use. **Troubleshooting steps:** 1. Check if port 8317 is already occupied: - Windows: `netstat -ano | findstr :8317` - macOS/Linux: `lsof -i :8317` 2. If a process is using port 8317, you can either: - Kill the existing process - Or configure EasyCLI to use a different port in the settings 3. If the app becomes unresponsive (white screen), force quit and restart after ensuring port 8317 is available. Could you share the error message you're seeing when the VPN is active? This will help identify the specific issue.
kerem commented 2026-02-27 16:46:44 +03:00
Author
Owner
Copy link

@benzntech commented on GitHub (Oct 23, 2025):

I see the issue - CLIProxyAPI is listening on IPv6 (*:8317) but EasyCLI is trying to connect via IPv4 (localhost:8317). This mismatch can cause connection issues.

<!-- gh-comment-id:3434908367 --> @benzntech commented on GitHub (Oct 23, 2025): I see the issue - CLIProxyAPI is listening on IPv6 (*:8317) but EasyCLI is trying to connect via IPv4 (localhost:8317). This mismatch can cause connection issues.
kerem commented 2026-02-27 16:46:44 +03:00
Author
Owner
Copy link

@ZZZdragondYNGPHX commented on GitHub (Oct 23, 2025):

Thank you for your help. I just tried but still can't solve the problem. I have given up debugging and tried other CLI agent software.

Image
<!-- gh-comment-id:3435599824 --> @ZZZdragondYNGPHX commented on GitHub (Oct 23, 2025): Thank you for your help. I just tried but still can't solve the problem. I have given up debugging and tried other CLI agent software. <img width="892" height="620" alt="Image" src="https://github.com/user-attachments/assets/1bb70f20-680f-437e-881b-7bfb80d8ffb0" />
kerem commented 2026-02-27 16:46:44 +03:00
Author
Owner
Copy link

@benzntech commented on GitHub (Oct 23, 2025):

Implemented automatic port cleanup to address the port conflict issue. The app now automatically kills any process using port 8317 before starting CLIProxyAPI.

<!-- gh-comment-id:3435802616 --> @benzntech commented on GitHub (Oct 23, 2025): Implemented automatic port cleanup to address the port conflict issue. The app now automatically kills any process using port 8317 before starting CLIProxyAPI.
kerem commented 2026-02-27 16:46:45 +03:00
Author
Owner
Copy link

@ZZZdragondYNGPHX commented on GitHub (Oct 23, 2025):

Thanks for your help,bro

<!-- gh-comment-id:3435813737 --> @ZZZdragondYNGPHX commented on GitHub (Oct 23, 2025): Thanks for your help,bro
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.1.32
v0.1.31
v0.1.30
v0.1.29
v0.1.28
v0.1.27
v0.1.26
v0.1.25
v0.1.24
v0.1.23
v0.1.22
v0.1.21
v0.1.20
v0.1.19
v0.1.18
v0.1.17
v0.1.16
v0.1.15
v0.1.14
v0.1.13
v0.1.12
v0.1.11
v0.1.10
v0.1.9
v0.1.8
v0.1.7
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
bug

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
starred/EasyCLI#4
No description provided.