Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with creating a new reality #408

Closed
nicelic opened this issue Jan 8, 2025 · 2 comments
Closed

Problems with creating a new reality #408

nicelic opened this issue Jan 8, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@nicelic
Copy link

nicelic commented Jan 8, 2025

Hello,
when I was using beta1 and beta2, I found that I could not create a user after creating an entry point when I created a new reality in the settings. When creating a user, it would display unknown data. As long as the reality created using the beta version, it would display unknown data. There was no such problem when using the reality created using v1.1.0 (creating a user and selecting the newly created entry point). After many experiments, I can rule out the sni domain name problem (the reality domain name is what I used frequently before) and the transmission protocol problem (I have tried h2, grpc, and tcp). I personally think that the newly created reality was not saved. There is a save button after creating a new reality in v1.1.0, but it was removed in the beta version. But I have no substantial evidence.

the log:
2025/01/08 02:00:41 INFO - inbound/vless[vless-58928]tcp server started at [::]:58928
2025/01/08 02:00:41 INFO - remove inbound: vless-58928
2025/01/08 02:00:34 INFO - inbound/vless[vless-58928]tcp server started at [::]:58928
2025/01/08 02:00:34 INFO - remove inbound: vless-58928
2025/01/08 01:59:49 ERROR - inbound/vless[reality_tcp_47.242.198.34]process connection from 164.52.24.180:53157: TLS handshake: REALITY: processed invalid connection
2025/01/08 01:59:10 INFO - inbound/vless[vless-58928]tcp server started at [::]:58928
2025/01/08 01:59:10 INFO - remove inbound: vless-58928
2025/01/08 01:58:29 ERROR - inbound/vless[reality_tcp_47.242.198.34]process connection from 138.197.79.193:49482: TLS handshake: REALITY: processed invalid connection
2025/01/08 01:58:13 INFO - inbound/vless[vless-58928]tcp server started at [::]:58928
2025/01/08 01:58:13 INFO - remove inbound: vless-58928
2025/01/08 01:58:13 INFO - inbound/vless[reality_h2_47.242.198.34]tcp server started at [::]:27530

@nicelic nicelic added the bug Something isn't working label Jan 8, 2025
@nicelic
Copy link
Author

nicelic commented Jan 8, 2025

Now, I use the script to downgrade to version 1.1.0, and found that the newly created inbound station is automatically deleted, and when I create a new inbound station, no matter which reality template I choose, it will automatically become the template "None" state after saving. I guess there is an error in the "save" somewhere, and it is not actually saved and exported as the singbox configuration. I hope this is a bug discovery and help to troubleshoot
QQ20250108-102137

@alireza0
Copy link
Owner

Hello @nicelic,
Thank you for your report. It might be a inconsistency between client and server.
I will keep it in my mind for further tests.
But please wait for final core and panel release.

Also please be informed that backward compatibility is not possible after this new version!
It is because this version is a refactor and will remove some parts which is mandatory in previous version.

@alireza0 alireza0 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants