whitedwarf

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by whitedwarf

  1. I have found this fix in another thread: Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run. Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.
  2. Since last update I have the same error as you: Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log. I think the update broke something but I have no idea what.
  3. Ah yes, it was as simple as that. Thanks
  4. Hello, I tried it as well and got the same issue & same log. Let me know if you need other info for the debug.
  5. Don't know if it will help but I have the IP of my unraid server and the domain name of my nextcloud instance (nextcloud.mydomain.com) in the trusted domains. I would suggest you change that back and try to solve the other error.
  6. @eubbenhadd That sounds messy. Have you tried to update directly from unraid command shell with the following command ? docker exec -it nextcloud updater.phar
  7. First time I hear about this functionality, but it looks like my consumer grade modem has it. It's a shame you have to change it again.
  8. Very strange. I had issues before upgrading (I was still on a 18.x version). The application tab was empty and I got the same message as you when trying via occ command. But it was solve with the update. Hopefully everything is in order now.
  9. Ok I disabled the app before upgrading to 20.0.6 and enabled it afterwards without any issue.
  10. I was about to upgrade when I saw your message. Were you able to solve the issue and have TOTP working back as normal ?
  11. I have the same impression. It's probably more related to the reverse proxy setup. REllU, did you make sure all the related dockers are using the same "network type" (called proxynet in the video done by Spaceinvaderone) ?
  12. FYI I just successfully reinstalled the OnlyOffice integration with nextcloud. I was getting an error when trying to connect to the Onlyoffice server in nextcloud. Looking at the OnlyOffice docker log I found out that it was due to a certificate error. Finally I was able to solve it by following these steps: 1. Open the console on the container 2. browse to /etc/onlyoffice/documentserver/default.json 3. Set 'rejectUnauthorized' to false Maybe it could solve your issue as well.
  13. I followed this guide which is very complete. You can find the configuration file for Authelia as well as for the NginxProxyManager at the top and the page. https://github.com/ibracorp/authelia Just tell me if you need more info, I'll gladly share.
  14. Nextcloud is a fantastic cloud storage with lots of options (I also use it to sync my agenda & contacts with my phone) but the office integration is too bad IMO. I spent hours trying to setup the integration of Collabora or OnlyOffice with my Nextcloud docker. I even got OnlyOffice working for a moment but then I updated a docker or changed something somewhere and it was over. I have not been able to make this integration work anymore. Instead of hitting my head against a wall I installed the CryptPad docker. OnlyOffice is integrated natively and you can easily import an existing document and export it when modified without creating an account. If you create an account you can benefit form its encrypted file storage but it is limited to compatible files only (you cannot use it to store something else than "pads"). In the end I could not find an ideal solution but I am quiet happy with that setup: nextcloud as a cloud service and CryptPad as a document editor.
  15. I just wanted to give a positive feedback as I was able to install the docker on my server and to import 21k pictures & videos. For me the main missing feature is the lack of authentification. Basically anyone having access to your network can openly browse your pictures. To secure it I installed the Authelia docker, which works well with NginxProxyManager. It took me some time (had a short night afterwards ) but it is now secured and works flawlessly.
  16. The issue is gone for me as well. Looks like there was an issue with the bios of my motherboard but everything went fine after I updated it.
  17. The description on how to run it is not accurate anymore but it's pretty easy: 1 . Open a terminal and create the folder and sub-folder mkdir mnt/user/appdata/tor-relay mkdir mnt/user/appdata/tor-relay/config 2. Create the config file by opening it with nano nano mnt/user/appdata/tor-relay/config/torrc 3. Copy-paste the configuration information from here https://github.com/DarkIsDude/tor-server#tor-configuration and change whatever you want there. 4. Save the file and start the docker
  18. Got the same error as you today. Did you manage to find what was the source of this error ?
  19. Thanks man. I had the same issue as you and didn't realize it was as easy as enabling the option in the proxy host configuration !
  20. Not sure that will help but, as far as I have seen, deleting the container does not mean its parameters are deleted. To be sure you are on a clean basis you should ssh and delete the "appdata/Medusa" folder after deleting the container. Of course you will have to configure it again ... but hopefully for the last time.
  21. It was working yesterday evening but I get an "ERR_CONNECTION_REFUSED" again this morning. I don't know which plugin is causing this issue but it's very annoying. I will try to delete them one by one to find the guilty...
  22. Here is how I got my server running again, there are probably better ways but that can maybe help someone else. 1. Boot in safe mode 2. Make a copy of the /boot/config/plugins folder (with a .bak extension) 3. Delete the content of the plugins folder 4. Reboot normally 5. Install the community app plugin via the link found on this forum 6. Install the essential plugins 7. Restore the /boot/config/plugins content for the reinstalled plugins After that my docker containers were not recognized properly (no shortcut to WebUI). I solved that easily: 1. Make a copy of the /mnt/user/appdata folder 2. Reinstalled the containers in "next next next" mode 3. Stop the containers 4. Restore the /mnt/user/appdata folder 5. Start the containers again I still don't understand why my server could not boot properly and why deleting all the plugins solved the issue, so if you have any idea you are welcome.
  23. Hi all, I updated unRAID to the latest version (6.8.1) and rebooted without issue. Yesterday I shutdown my server and since then it does not work properly. The web GUI is not reachable (connection refused), my docker containers are off as well as the smb shares but I can SSH using putty. I have tried to boot in safe mode and I am able to start the array and then to run my docker containers, use the smb shares, etc. This issue already happened last time I updated unRAID and I had to re-create my USB flash and to reinstall all the plugins and docker containers... Is there a way to uninstall or disable the plugins on next boot so that i can reinstall them properly ? Or is there anything I should try before starting to install everything again ? Thank you in advance for your help
  24. Updated with no issue. I really like the new look and feel. Great job !