DC_Interstellar

I believe so... I just barely got a AMD Ryzen 7 5800x today and it gave me that same error. I was using an old i5-3570k and the temps were showing.

I'm running Adguard on my server as well. On your docker containers when you click on the globe, it will direct you to http://192.168.1.15:3000/. You will need to remove port 3000 from your web address so it's only showing http://192.168.1.15. For example, mine is showing http://192.168.0.2:3000. But if I remove the 3000 and just access http://192.168.0.2. I'm able to access the GUI.

Unraid Docker Container - OnlyOfficeDocumentServer - "The file size exceeds the limitation set for your server" error I'm currently running the OnlyOfficeDocumentServer VIA Docker App through the Community Applications store. I'm using OnlyOffice through Nextcloud, which is working until I open up a large PowerPoint file. I'm receiving an error saying "The file size exceeds the limitation set for your server. Please contact your Document Server admin for details" I found other articles that you need to edit your default.json file located underneath /etc/onlyoffice/documentserver/default.json. However... The docker container that Installed via the Community Applications store did not create a default.json file underneath the documentserver. Do I need to create a default.json file and add a Path to it? Is this the correct default.json? If so is there any documentation on what variables I need to change for my needs? https://github.com/ONLYOFFICE/server/blob/master/Common/config/default.json References: https://www.reddit.com/r/OnlyOffice/comments/ue15s1/how_to_increase_file_size_limit_on_docker_version/ https://forum.onlyoffice.com/t/the-file-size-exceeds-the-limitation-set-for-your-server/4888

So, you’re saying you will not go into the go file & add the short script that’ll take you a couple seconds? If you can’t do that. Then okay. Not be rude or anything, we can’t help you if don’t add it in. All of us were able to get working & it’s great! I, myself, suggest adding it in, but again. It’s up to you if want to or not.

Changed Status to Closed

Closing issue

/boot/config/go Best if you do this change directly into your Unraid GUI

Changed Status to Solved

Perfect! That worked!! Thank you so much @bonienl and the Unraid development team for all the hard work ya'll put in!! Marking issue as resolved. Closing it in a couple of days from now.

UPDATE: v6.12.1 was just barely released to fix the SMB issue. Retesting to confirm that after reboot of the Unraid Server that the "go" file code will allow the "Include listening interfaces" in Settings>Network Settings to work and stay the same without manually editing it every time the server restarts.

Changed Status to Retest

I am not. I'm currently running the stable release version. I was just talking to @bonienl on the bug report "[6.12.0] TAILSCALE: SMB, SSH, AND GUI UNABLE TO CONNECT" that I created. bonienl informed me there will be fix for the SMB in the next release. However, I added the code that was provided to go into the 'go' file. See below, this is what my 'go' file looks like: #!/bin/bash # Start the Management Utility # reload services after starting docker with 20 seconds grace period to allow starting up containers event=/usr/local/emhttp/webGui/event/docker_started mkdir -p $event cat <<- 'EOF' >$event/reload_services echo '/usr/local/emhttp/webGui/scripts/reload_services' | at -M -t $(date +%Y%m%d%H%M.%S -d '+20 sec') 2>/dev/null EOF chmod +x $event/reload_services /usr/local/sbin/emhttp & This did not work for me when I restarted the array. Docker services and auto start is setup correctly. Did I enter the code correctly?

Interesting… It might be my coding? To double make sure of myself. This is what I currently have in my “go” file. Please correct me if the coding is incorrect. #!/bin/bash # Start the Management Utility # reload services after starting docker with 20 seconds grace period to allow starting up containers event=/usr/local/emhttp/webGui/event/docker_started mkdir -p $event cat <<- 'EOF' >$event/reload_services #!/bin/bash echo '/usr/local/emhttp/webGui/scripts/reload_services' | at -M -t $(date +%Y%m%d%H%M.%S -d '+20 sec') 2>/dev/null EOF chmod +x $event/reload_services /usr/local/sbin/emhttp &

I’ve added this code above the emhttpd in the go file # reload services after starting docker with 20 seconds grace period to allow starting up containers event=/usr/local/emhttp/webGui/event/docker_started mkdir -p $event cat <<- 'EOF' >$event/reload_services #!/bin/bash echo '/usr/local/emhttp/webGui/scripts/reload_services' | at -M -t $(date +%Y%m%d%H%M.%S -d '+20 sec') 2>/dev/null EOF chmod +x $event/reload_services

Alrighty, I made the changes to the docker service & autostart for Tailscale container. It did start the container successfully. However, it’s still denying me to use SSH & the GUI. Unless I delete the tailscale0 then re-add it back in, then it works. I’ll be looking forward for the next release for SMB! Thank You!