From a9b8ef94a2725c69498a8d975729b76abaf5b713 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miroslav=20=C5=A0ediv=C3=BD?= Date: Mon, 31 Mar 2025 19:35:55 +0200 Subject: [PATCH] docs browser is not starting with persistent profile. --- webpage/docs/troubleshooting.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/webpage/docs/troubleshooting.md b/webpage/docs/troubleshooting.md index 1b0152b7..14b978a6 100644 --- a/webpage/docs/troubleshooting.md +++ b/webpage/docs/troubleshooting.md @@ -244,6 +244,28 @@ To fix this, you can either remove the conflicting Docker network or change the } ``` +### Browser is not starting with persistent profile {#browser-profile-not-starting} + +If you are using a persistent profile like `google-chrome` shown below, and the browser is not starting (you see a black screen), it may be because the profile is corrupted or not mounted correctly. + +```yaml title="docker-compose.yaml" +volumes: +# For google-chrome +- /data:/home/neko/.config/google-chrome +``` + +Possible reasons are: +- The profile is corrupted, which can happen if the container is not stopped properly. Browsers should be able to recover from this, but it may not work in some cases. +- The profile is not mounted to the correct path. Make sure that you are mounting the profile to the correct path in your `docker-compose.yaml` file. +- The profile is not owned by the correct user. Make sure that the profile is owned by the `neko` user in the container. You can check this by running the following command: + +```bash +# Check the owner of the profile +docker exec -it ls -la /home/neko/.config/google-chrome +# To change the owner +docker exec -it chown -R neko:neko /home/neko/.config/google-chrome +``` + ### Common server errors {#common-server-errors} ```