starred/EasyCLI

Fork 0

mirror of https://github.com/router-for-me/EasyCLI.git synced 2026-04-25 07:35:51 +03:00

[GH-ISSUE #2] Cannot set password or launch if password is set #3

New issue

Closed

opened 2026-02-27 16:46:42 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 16:46:42 +03:00

Owner

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

Originally assigned to: @luispater on GitHub.

Cannot set password.

Steps I did:

Clone repo
npm install && npm run build
Run ././src-tauri/target/release/easycli
Choose local and try to set password

I've also tried pre-configuring the config.yaml. I set the secret-key beforehand and that introduces an entirely new error:

./easycli
[CLIProxyAPI][START] exec: /home/rashino/cliproxyapi/6.0.20/cli-proxy-api
[CLIProxyAPI][START] args: -config /home/rashino/cliproxyapi/config.yaml --password PwBtPtrVAtRP6Sjj62d0IfyklbEUSI4j
[CLIProxyAPI][STDOUT] CLIProxyAPI Version: 6.0.20, Commit: 4a31f76, BuiltAt: 2025-10-01T12:19:32Z

(easycli:990426): libayatana-appindicator-WARNING **: 15:12:28.550: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
[KEEP-ALIVE] Started keep-alive for port 8317
[KEEP-ALIVE] Starting keep-alive loop for port 8317
[KEEP-ALIVE] Sending request to: http://127.0.0.1:8317/keep-alive
[KEEP-ALIVE] Using password: PwBtPtrV...
[KEEP-ALIVE] Request error: error sending request for url (http://127.0.0.1:8317/keep-alive)
[CLIProxyAPI][STDOUT] [2025-10-02 15:12:28] [info] [main.go:121] CLIProxyAPI Version: 6.0.20, Commit: 4a31f76, BuiltAt: 2025-10-01T12:19:32Z
[KEEP-ALIVE] Stopping keep-alive mechanism                                                                   → 5.23s

It uses a random secret key on each launch and overwrites the config file, deleting everything and creating a brand new, random password.

Originally created by @DevGuyRash on GitHub (Oct 2, 2025). Original GitHub issue: https://github.com/router-for-me/EasyCLI/issues/2 Originally assigned to: @luispater on GitHub. <img width="526" height="379" alt="Image" src="https://github.com/user-attachments/assets/eeba54f5-142f-4b33-85cf-38a9ef0dcfb0" /> Cannot set password. Steps I did: 1. Clone repo 2. `npm install && npm run build` 3. Run `././src-tauri/target/release/easycli` 4. Choose local and try to set password I've also tried pre-configuring the `config.yaml`. I set the `secret-key` beforehand and that introduces an entirely new error: ```bash ./easycli [CLIProxyAPI][START] exec: /home/rashino/cliproxyapi/6.0.20/cli-proxy-api [CLIProxyAPI][START] args: -config /home/rashino/cliproxyapi/config.yaml --password PwBtPtrVAtRP6Sjj62d0IfyklbEUSI4j [CLIProxyAPI][STDOUT] CLIProxyAPI Version: 6.0.20, Commit: 4a31f76, BuiltAt: 2025-10-01T12:19:32Z (easycli:990426): libayatana-appindicator-WARNING **: 15:12:28.550: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code. [KEEP-ALIVE] Started keep-alive for port 8317 [KEEP-ALIVE] Starting keep-alive loop for port 8317 [KEEP-ALIVE] Sending request to: http://127.0.0.1:8317/keep-alive [KEEP-ALIVE] Using password: PwBtPtrV... [KEEP-ALIVE] Request error: error sending request for url (http://127.0.0.1:8317/keep-alive) [CLIProxyAPI][STDOUT] [2025-10-02 15:12:28] [info] [main.go:121] CLIProxyAPI Version: 6.0.20, Commit: 4a31f76, BuiltAt: 2025-10-01T12:19:32Z [KEEP-ALIVE] Stopping keep-alive mechanism → 5.23s ``` It uses a random secret key on each launch and overwrites the config file, deleting everything and creating a brand new, random password.

kerem

2026-02-27 16:46:42 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 16:46:44 +03:00

Author

Owner

@DevGuyRash commented on GitHub (Oct 2, 2025):

I actually figured it out partially.

Whenever you have api-keys: set in the root of config.yaml, it will not launch and you'll get the codeblock above. If you delete it from the cofnig, it launches fine. You can then add one post-launch in the GUI. However, if you close and reopen, it will fail to open again. So you can't use access keys reliably if you want to use the GUI.

@DevGuyRash commented on GitHub (Oct 2, 2025): I actually figured it out partially. Whenever you have `api-keys:` set in the root of `config.yaml`, it will not launch and you'll get the codeblock above. If you delete it from the cofnig, it launches fine. You can then add one post-launch in the GUI. However, if you close and reopen, it will fail to open again. So you can't use access keys reliably if you want to use the GUI.

kerem commented

2026-02-27 16:46:44 +03:00

Author

Owner

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

I fixed the bug in v0.1.13, you may try again.

If the bug still persists, maybe you should clean up the ~/cliproxyapi directory

@luispater commented on GitHub (Oct 3, 2025): I fixed the bug in v0.1.13, you may try again. If the bug still persists, maybe you should clean up the ~/cliproxyapi directory

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#3

No description provided.

Rows
Columns