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

error menu not showing #98

Closed
mrphuong186 opened this issue Nov 1, 2024 · 3 comments
Closed

error menu not showing #98

mrphuong186 opened this issue Nov 1, 2024 · 3 comments
Labels
documentation Improvements or additions to documentation troubleshooting 🔧 Not a bug. Something went wrong for specific users, let's find a solution together

Comments

@mrphuong186
Copy link

screenshot_1730435812
error menu not showing
sometimes have to restart many times to show menu
please guide how to solve
thank you very much

@MRColorR
Copy link
Owner

MRColorR commented Nov 1, 2024

Thank you for reporting this issue.

This is the first time this odd behavior has been reported, and since no errors are popping up, it's quite hard to determine how or if it's related to the code. It seems you might be using a very old release, and something could be blocking the update checker function at startup. Please update your m4b to the latest version, as V3 has been deprecated.

I would also like to point out that we have an issue template in place to guide users in providing all the necessary information to help us understand the environment and the cause of their issues. Unfortunately, your report did not include context such as the Docker version, OS version, OS architecture, etc.

If after updating to the V4 release your issue still occurs:

  • Could you please provide these details so we can better assist you?
  • Also try to run money4band in debug mode by passing --log-level DEBUG as flag to the main and check the generated logs.
    If your issue is resolved after the update, please let us know and feel free to close the issue.

Thank you for your cooperation.

@mrphuong186
Copy link
Author

Thank you for reporting this issue.

This is the first time this odd behavior has been reported, and since no errors are popping up, it's quite hard to determine how or if it's related to the code. It seems you might be using a very old release, and something could be blocking the update checker function at startup. Please update your m4b to the latest version, as V3 has been deprecated.

I would also like to point out that we have an issue template in place to guide users in providing all the necessary information to help us understand the environment and the cause of their issues. Unfortunately, your report did not include context such as the Docker version, OS version, OS architecture, etc.

If after updating to the V4 release your issue still occurs:

  • Could you please provide these details so we can better assist you?
  • Also try to run money4band in debug mode by passing --log-level DEBUG as flag to the main and check the generated logs.
    If your issue is resolved after the update, please let us know and feel free to close the issue.

Thank you for your cooperation.
thanks for your support
as you said V4 version has no menu error
but because it doesn't have new proxy update function or is it broken like in V3?
and the next problem seems honeygain version 0.8.1 always in state Connected. Waiting for traffic...
in V3 i use honeygain version 0.6.6 it works
and very strange i run more than 1 device and the score received is only equal to 1 device?
please give me a solution, thank you very much.
screenshot_1730506595

@MRColorR MRColorR added documentation Improvements or additions to documentation troubleshooting 🔧 Not a bug. Something went wrong for specific users, let's find a solution together labels Nov 2, 2024
@MRColorR
Copy link
Owner

MRColorR commented Nov 2, 2024

  • Regarding the proxy functions V4 has enhanced proxy support significantly (more details in changelogs and on discord M4B community). Many users are successfully using it in this configuration. If an app does not support proxies and actively blocks proxy IPs, there's not much we can do. This does not mean the proxy is broken, but rather that the app does not support it. Additionally, the proxy in use must be capable of accepting the ports and protocols used by the apps, or they won't work. This is a proxy provider issue, not something we can change on our side.

    • If you have found a bug in the image used in V3 and V4 for running proxies, the issue can be resolved by reporting it to the image developer on their GitHub project. Once the new image is online, Money4Band will use it automatically. If you have identified a bug or error in the logic or have a solution or alternative to a problem you've found with the proxies, please share it with us so we can address it.
  • Regarding Honeygain, they do not permit proxies. They accept one device per IP, and your IP must not be banned by Honeygain. As your devices are connected, it could be a networking/routing issue between your network, your ISP network, your DNS provider, and Honeygain. Alternatively, Honeygain may have decided not to send traffic to your devices at the moment. Check the Honeygain container logs to see if there are any errors and report back to Honeygain for further assistance. Additionally, Honeygain started building multiarch images starting from version 0.8.0, but I am still using version 0.6.6. There might be something they are still figuring out with these new images. In the meantime i'll investigate this behavior and if i find something i'll discuss it in the discord community.

This is what i can say with the current information, if there is something i missed please explain and i will try to assist you further.

@MRColorR MRColorR closed this as completed Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation troubleshooting 🔧 Not a bug. Something went wrong for specific users, let's find a solution together
Projects
None yet
Development

No branches or pull requests

2 participants