Z User 090d81605e fix(subscription): return actual error message instead of generic 'failed' ...

The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.
fix(subscription): return actual error message instead of generic 'failed'
The generic 'subscription generation failed' gave users no clue what
was wrong. Now the actual error is returned in the JSON response:
- 'user is not bound to any listener' → bind the user to a node
- 'no exportable proxies for user' → check listener config / protocol
- 'failed to load credentials' → check credential_key / user passwords
- 'listener X requires at least one active user' → bind active users
The log.Printf is still present for server-side diagnostics.

2026-08-31 03:05:07 +00:00

..

access_token.go

fix(backend): XFF-aware rate limiting, host trust, error sanitization

2026-08-29 09:39:00 +00:00

config_routes.go

update

2026-08-19 12:49:36 +08:00

cors.go

fix(non-listener): enforcement retry, DB restore warning, security headers, config placeholder, sensitive key gaps, dead UI options, bot API server, update.sh dedup

2026-08-30 11:13:08 +00:00

dashboard.go

feat(p1): dashboard users totals (online/enabled/total)

2026-08-17 20:55:13 +08:00

deps.go

fix: wire listener.Handler for /nodes templates/versions; cascade delete bindings

2026-08-17 18:19:08 +08:00

mihomo_routes.go

fix: align listener generation with mihomo official spec

2026-08-16 09:21:42 +08:00

panel_server.go

feat(nat): custom panel port/listen/public_url via env, API, settings UI, install.sh

2026-08-29 12:33:28 +08:00

panel_settings.go

fix(all-remaining): 24 audit findings — Medium + Low severity

2026-08-31 00:19:24 +00:00

route_registration_test.go

test: prevent duplicate listener and node route registration

2026-08-18 13:49:00 +08:00

router_test.go

update

2026-08-16 11:16:41 +08:00

router.go

fix(all-remaining): 24 audit findings — Medium + Low severity

2026-08-31 00:19:24 +00:00

routing_routes.go

feat: config groups/rules API routes for routing UI

2026-08-16 23:06:14 +08:00

subscription.go

fix(subscription): return actual error message instead of generic 'failed'

2026-08-31 03:05:07 +00:00