DaanSelen
DaanSelen
Essential security can be handled by going into the container itself, but you are right. i need to setup some auto building. For your issue I think I have a...
@hoggatt just pushed a new Docker Image version, can you test with that?
> > @hoggatt just pushed a new Docker Image version, can you test with that? > > Works now with my config! Logs look good. > > Is there a...
> > Essential security can be handled by going into the container itself, but you are right. i need to setup some auto building. For your issue I think I...
@hoggatt it took long... but here it is: https://github.com/donaldzou/WGDashboard/pull/437 Persistency among updates works not through symlinks which makes the WGDashboard files latest every time the image is built. Also with...
Have you tested on the new version?
I'd like to help but can you perhaps show some configuration options if possible? And if you get any response at all?
> ``` > [2024-10-07 00:42:27 +0300] [9511] [INFO] Handling signal: term > [2024-10-07 00:42:57 +0300] [9511] [ERROR] Worker (pid:9513) was sent SIGKILL! Perhaps out of memory? > [2024-10-07 00:42:57 +0300]...
Regarding the service itself, you can check the `journalctl -u wg-dashboard.service -f`. But weird that that happends. Can you if you don't have a big installation reinstall everything, including the...
@quantuumsnot do you still encounter this?