[GH-ISSUE #4] CLIProxyAPI process exited abnormally #5

Closed
opened 2026-02-27 16:46:44 +03:00 by kerem · 6 comments
Owner

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

First start and the app throwing an error. Completely unable to use app. I used default configuration for config.yaml file for

Image
Originally created by @UsamaKarim on GitHub (Oct 7, 2025). Original GitHub issue: https://github.com/router-for-me/EasyCLI/issues/4 First start and the app throwing an error. Completely unable to use app. I used default configuration for `config.yaml` file for <img width="1042" height="712" alt="Image" src="https://github.com/user-attachments/assets/5d31213a-95c1-4149-aa4f-9114c4a143f3" />
kerem closed this issue 2026-02-27 16:46:44 +03:00
Author
Owner

@luispater commented on GitHub (Oct 7, 2025):

Did you first run the CLIProxyAPI service locally?

If you've already got the service running, please use Remote mode.

EasyCLI in Local mode automatically updates to the latest binary version of CLIProxyAPI and then starts the service.

<!-- gh-comment-id:3377799871 --> @luispater commented on GitHub (Oct 7, 2025): Did you first run the CLIProxyAPI service locally? If you've already got the service running, please use Remote mode. EasyCLI in Local mode automatically updates to the latest binary version of CLIProxyAPI and then starts the service.
Author
Owner

@UsamaKarim commented on GitHub (Oct 7, 2025):

Did you first run the CLIProxyAPI service locally?

Yes.

In remote mode, it's giving error while connecting.
Image

<!-- gh-comment-id:3377843053 --> @UsamaKarim commented on GitHub (Oct 7, 2025): > Did you first run the CLIProxyAPI service locally? > Yes. In remote mode, it's giving error while connecting. <img width="642" height="492" alt="Image" src="https://github.com/user-attachments/assets/a14951a5-92f1-4e11-af9f-5ad9c8cb5530" />
Author
Owner

@luispater commented on GitHub (Oct 7, 2025):

Use 127.0.0.1 instead of localhost, and try again.

<!-- gh-comment-id:3377874975 --> @luispater commented on GitHub (Oct 7, 2025): Use 127.0.0.1 instead of localhost, and try again.
Author
Owner

@luispater commented on GitHub (Oct 7, 2025):

Furthermore, please make sure that you set remote-management.secret-key in the config.yaml file.

<!-- gh-comment-id:3377886988 --> @luispater commented on GitHub (Oct 7, 2025): Furthermore, please make sure that you set `remote-management.secret-key` in the `config.yaml` file.
Author
Owner

@UsamaKarim commented on GitHub (Oct 7, 2025):

Thanks for the help. It’s working now.

<!-- gh-comment-id:3377904990 --> @UsamaKarim commented on GitHub (Oct 7, 2025): Thanks for the help. It’s working now.
Author
Owner

@luispater commented on GitHub (Oct 7, 2025):

You're welcome, and thanks for using our project.

<!-- gh-comment-id:3377953602 --> @luispater commented on GitHub (Oct 7, 2025): You're welcome, and thanks for using our project.
Sign in to join this conversation.
No labels
bug
pull-request
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
starred/EasyCLI#5
No description provided.