mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 17:15:49 +03:00
[GH-ISSUE #1436] The core startup fails. #1432
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1432
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lcopilot on GitHub (Nov 17, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1436
Originally assigned to: @NghiaTranUIT on GitHub.
Description
The core startup fails. Sometimes the core startup fails and the software needs to be restarted. The number of times cannot be determined. Sometimes it can be restarted once it is restarted, and sometimes it needs to be restarted several times before it can be restarted.
Environment
@NghiaTranUIT commented on GitHub (Nov 17, 2022):
it's the first time we hear the report that Proxyman could not start the core.
If you don't mind, please open Proxyman -> Help -> Advanced -> Enable Debug Mode -> Follow the guide
and share with me the error log when the Core is failed to start. I'd like to investigate it 👍
@NghiaTranUIT commented on GitHub (Nov 17, 2022):
One more thing: Please open Preference -> Proxy Port -> Change to 9091.
Port 9090 might be occupied by other apps, so Proxyman could not start 🤔
@lcopilot commented on GitHub (Nov 17, 2022):
Automatic selection of available ports is on
Log
2022-11-17 11:18:51.364 Proxyman[6014:76232] [HelperTool] Bundled 1.4.0 vs OnDisk 1.4.0
2022-11-17 11:18:51.516 Proxyman[6014:76221] [AppCenter] ERROR: -[MSACServiceAbstract canBeUsed]/58 Analytics service hasn't been started. You need to call [MSACAppCenter start:YOUR_APP_SECRET withServices:LIST_OF_SERVICES] first.
2022-11-17 11:18:51.516 Proxyman[6014:76221] [AppCenter] ERROR: -[MSACServiceAbstract canBeUsed]/58 Analytics service hasn't been started. You need to call [MSACAppCenter start:YOUR_APP_SECRET withServices:LIST_OF_SERVICES] first.
2022-11-17 11:18:51.782 Proxyman[6014:76221] [AppCenter] ERROR: -[MSACServiceAbstract canBeUsed]/58 Analytics service hasn't been started. You need to call [MSACAppCenter start:YOUR_APP_SECRET withServices:LIST_OF_SERVICES] first.
2022-11-17 11:18:51.782 Proxyman[6014:76221] [AppCenter] ERROR: -[MSACServiceAbstract canBeUsed]/58 Analytics service hasn't been started. You need to call [MSACAppCenter start:YOUR_APP_SECRET withServices:LIST_OF_SERVICES] first.
2022-11-17 11:18:51.832 Proxyman[6014:76224] [HelperTool] Bundled 1.4.0 vs OnDisk 1.4.0
2022-11-17 11:18:51.935 Proxyman[6014:76221] version = 1.4.0
✅ [NetworkSystem] HTTP Override by HelperTool (New APIs)
❌[ERROR] Server failure, error: 未能完成操作。（Network.NWError错误0。）
2022-11-17 11:18:52.018 Proxyman[6014:76221] version = 1.4.0
❌[ERROR] Failed to bind 127.0.0.1:3500, bind(descriptor:ptr:bytes:): Address already in use (errno: 48)
❌[ERROR] Failed to bind ::0:3500, bind(descriptor:ptr:bytes:): Address already in use (errno: 48)
@NghiaTranUIT commented on GitHub (Nov 17, 2022):
Thanks. The problem is
Can you change the port number to a different port? 9090 or 9091?
It would fix the issue.
@lcopilot commented on GitHub (Nov 17, 2022):
This can solve the problem, but my automatic selection of available ports is enabled. Does this mean that there is a bug in the automatic selection of available ports
@NghiaTranUIT commented on GitHub (Nov 17, 2022):
Yes, it looks like it's a bug. I will investigate.
@NghiaTranUIT commented on GitHub (Nov 24, 2022):
Fixed with this Beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.13.0_Fix_Websocket_failed.dmg
This bug only occurs if we listen in both IPv4 and IPv6 👍
@lcopilot commented on GitHub (Nov 25, 2022):
He has been resolved, thanks to the official positive fix