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

[BUG] upgrade from 1.6.1-rc1 to 1.6.1-rc2 make freeze in read-only mode #2052

Open
2 tasks done
thelittlefireman opened this issue Mar 1, 2025 · 4 comments
Open
2 tasks done
Assignees
Labels
bug Something isn't working next minor

Comments

@thelittlefireman
Copy link
Contributor

What happened?

I've upgrade from 1.6.1-rc1 to 1.6.1-rc2 and now my bw-ui is frozen in read-only mode. What happen ? how can i change it to writable mode ?

How to reproduce?

Use ui and upgrade from 1.6.1-rc1 to 1.6.1-rc2

Configuration file(s) (yaml or .env)

Relevant log output

BunkerWeb version

1.6.1-rc2

What integration are you using?

Docker

Linux distribution (if applicable)

synology

Removed private data

  • I have removed all private data from the configuration file and the logs

Code of Conduct

  • I agree to follow this project's Code of Conduct
@thelittlefireman thelittlefireman added the bug Something isn't working label Mar 1, 2025
@TheophileDiot
Copy link
Member

Hi, it would be really helpful to have some logs, as outlined in the Relevant log output section. Without them, it's difficult to determine what exactly went wrong based on just the message provided. Could you share the relevant logs so we can troubleshoot this more effectively? Thank you

@TheophileDiot TheophileDiot self-assigned this Mar 3, 2025
@TheophileDiot
Copy link
Member

I think I know what happened, we haven't implemented a "restart" function in the scheduler, this may be the issue. Try stopping the scheduler and starting it again as a temporary fix.

@TheophileDiot
Copy link
Member

I spoke fast, my bad, I'll keep digging this issue.

@TheophileDiot
Copy link
Member

@thelittlefireman, have a look at #2041. I'm guessing this is more or less the same issue. I'll send the steps to fix the problematic file in a few minutes 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working next minor
Projects
None yet
Development

No branches or pull requests

2 participants