windiz

Members
  • Posts

    5
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

windiz's Achievements

Noob

Noob (1/14)

2

Reputation

  1. I upgraded 6.12.2 -> 6.12.3 and webgui has been up over 7 days now. 6.12.2 didn't survive this long even once. Still too early to say if problem is solved or not. And many other posters wrote that update didn't solve the problem so I'm not too confident yet. Strange thing is that my other unraid server is still on version 6.12.2 and it hasn't crashed once. It has been running 30 days now. I'm expecting to webgui and whole server to stay up for 365 days as in earlier versions which is my normal maintenance interval and time to do yearly boot and dust cleaning. After that I can say problem solved 🙂.
  2. I haven't yet updated to 6.12.3. Since everything is working except webui and it's laborious to shut all services down on VMs and to start them up again. Strange thing is that I have another unraid server which has almost identical config and is in same network than the server which has webui crashing. I upgraded unraid version for both of them at the same time but that server 2 has been running without webui crashing since update. Difference between them is that unraid server 1 is the "main" server with more containers and also VMs but the server 2 is just file storage. I don't know if that has anything to do with the problem. Unraid server 1 (the one with webui crashing): Containers: elasticsearch piwigo endlessh netdata diskover mariadb mysql Plex deluge Plugins: community.applications.plg - 2023.07.03 (Up to date) dynamix.active.streams.plg - 2023.02.19 (Up to date) dynamix.cache.dirs.plg - 2023.02.19 (Up to date) dynamix.file.integrity.plg - 2023.03.26 (Up to date) dynamix.system.temp.plg - 2023.02.04b (Up to date) file.activity.plg - 2023.06.15 (Up to date) fix.common.problems.plg - 2023.04.26 (Up to date) open.files.plg - 2023.06.12 (Up to date) tips.and.tweaks.plg - 2023.07.05 (Up to date) unbalance.plg - v2021.04.21 (Up to date) unRAIDServer.plg - 6.12.2 user.scripts.plg - 2023.03.29 (Up to date) VMs: 3 VMs running Unraid2 (stable): Containers: netdata Plugins: community.applications.plg - 2023.07.21 (Update available: 2023.07.03) dynamix.file.integrity.plg - 2023.03.26 (Up to date) fix.common.problems.plg - 2023.04.26 (Update available: 2023.07.16) unassigned.devices.plg - 2023.07.04 (Update available: 2023.07.16) unassigned.devices-plus.plg - 2023.04.15 (Up to date) unbalance.plg - v2021.04.21 (Up to date) unRAIDServer.plg - 6.12.2 user.scripts.plg - 2023.03.29 (Update available: 2023.07.16) VMs: No VMs
  3. Okay it was just a good luck. Woke up this morning again to see webgui has crashed (http error 500). It worked about 4 days. I didn't have webgui open at browser this time and still crashed so that doesn't seem to trigger crash. And as I wrote earlier I don't have IPv6 enabled so that shouldn't also be issue. Again there wasn't anything other special at syslog than that "exit status 255 from user root php" repeated at 1 hour interval which I mentioned at earlier post. Maybe I just need to rollback version for now.
  4. For me this bug seems to be related for unraid webgui tab being open too long (Chrome). Normally I have my computer open 24/7 and also unraid webgui tab open at browser. This haven't been issue until upgrading to 6.12.2. After this upgrade I experienced webgui crash twice. On my server it seems not to be related to IPv6 because I've always had IPv4 only setting. I couldn't get webgui back although I killed nginx and tried to restart and reload it and also tried to restart and reload php but it didn't make any difference. Otherwise everything worked normally, VMs and dockers kept running and smb shares worked and I could connect to server by ssh. I could get to unraid login screen if I cleared cookies but after login I just got http error 500. Only way to get webgui back was to restart whole server. Only common log entry before both crashes was this, it was repeated at 1 hour interval until I noticed webgui crash and rebooted: I don't know if that is cause or just effect after webgui has been crashed or is it any way related to issue but that was on log before both crashes and I haven't seen that after those crashes. Now I've kept unraid webgui tab closed at browser when not operating and webgui has been up +24 hours. Let's see if it's just good luck.
  5. Hi everyone! I'm new at the forum but I have 9 years experience of Unraid. Sorry for my bad English. FileBrowser container seems great! Basic functionality seems to be working 100%. Although I would like to add reCaptcha authentication on login. Documentation says that this can be added with this command: filebrowser config set --auth.method=json --recaptcha.key site-key --recaptcha.secret private-key I tried to run this command on Unraid terminal but it always returns timeout: root@192:~# docker exec -ti FileBrowser /filebrowser config set --auth.method=json --recaptcha.key site-key --recaptcha.secret private-key 2020/01/13 05:53:22 timeout I get timeout from also from other commands if trying to change config. I can't even print current config using "config cat" command. Version command seems to be working: root@192:~# docker exec -ti FileBrowser /filebrowser version File Browser v2.1.0/6ce44f7 I found this thread with same problem: https://github.com/filebrowser/filebrowser/issues/627 There is comment: "You can only either be serving File Browser or execute commands. You can't change the database while its running." So I think that to change config with commands it is needed to stop the Filebrowser first and then start it again. However I think that this can't be done since this docker container hasn't got bash/shell? My config: Host path 1 (shares): Container Path: /srv /mnt/user/filebrowser_share/ Host path 2 (database.db): /mnt/user/appdata/filebrowser/ Container Path: /db/ Config (additional mapping for .filebrowser.json): /mnt/user/appdata/filebrowser_config/.filebrowser.json Container Path: /.filebrowser.json Any help appreciated! Thanks also for great work with this docker container.