Daniel Hååvi

Hey @AnorakArturo, thanks for the report. Yes, this is useless, and as explained in #814, should not happen anyway and anymore.

The UI should not automatically start at boot. Did you maybe enable that yourself?

Great. The Notifier should show up in the tray icon though. Can you check if the process shown in the screenshot is actually running?

Are you using multiple user accounts at the same time as in #854?

Does it work without the 0/0 routing? I remember this being a source of problems - because of the packet marks used by wg-quick.

Nothing changes when you switch release channel. It just downloads some new resources. They are only applied when you restart. If you can reproduce, please provide debug info.

Hey @boistordu, thanks for reporting this. `htop` shows the core service using a lot of resouces. Please copy the debug information in the settings _while experiencing the issue_ and paste...

You can open `http://127.0.0.1:817/api/v1/debug/core?style=github` in your browser. You can just paste the full thing here, it will format correctly. Please be reminded to do this _while experiencing the issue_.

Thanks for hanging in there and doing your best to get us the debug data. > sorry if I'm being rude I understand this can be frustrating, still I would...

> backend through a browser doesnt work that well which renders the debug process when your process is running into a loop Even with high CPU usage, delivering the interface...