Jump to content

pervin_1

Members
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

3 Neutral

About pervin_1

  • Rank
    Advanced Member

Recent Profile Visitors

660 profile views
  1. No solution tbh. I am stuck perhaps. We are going to figure this out, eventually. Let me know if you come up with any news or a solution. Would appreciate it!
  2. I also received this message the first time when I tried to TRIM the NVMe drive ( ADATA SX8200 480GB, relatively new SSD) connected directly to the MOBO's M.2 port — using as a cache drive. I upgraded to the latest 6.7 Stable a few days ago, never seen this message before. Diagnostics attached. Thank you! tower-diagnostics-20190609-2320.zip
  3. Anybody have any idea why DuckDNS docker works 99% of times, it always succeeds updating my IP address, but when my internet goes down ( IP change overnight ), it fails to update my address with the usual message something went wrong please check your settings. The only to fix it is to restart the docker; then it works again. I would appreciate any help. Thank you in advance!
  4. Does anybody have any idea why I am getting this message after upgrading MariaDB 10.3.15 today? Was running Nextcloud 15. Updated to the latest Nextcloud 16, the same error "Error occurred while checking server setup" is still persisting. edit: It had nothing to do with my setup or Maria DB. Checked the logs after, it turns out the Nextcloud.com was down. And that was causing the issues. Because part of the security scan is an online connection to their servers. All good Now!
  5. follow up to my own post: this is the most relevant information I came across today, cannot guarantee its gonna work, but gave it a try, fingers crossed, will post results shortly. Apparently, my problem started back in July, not in Oct. as I stated in the above. link Also, you can try to disable the NIC flow control and NIC offload using the plugin tips and tricks to ensure persistence after reboots, otherwise use ethtool and user scripts to make it persistent.
  6. Oct 13 12:19:25 Tower kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang: Oct 13 12:19:25 Tower kernel: TDH <0> Oct 13 12:19:25 Tower kernel: TDT <8> Oct 13 12:19:25 Tower kernel: next_to_use <8> Oct 13 12:19:25 Tower kernel: next_to_clean <0> Oct 13 12:19:25 Tower kernel: buffer_info[next_to_clean]: Oct 13 12:19:25 Tower kernel: time_stamp <127739b72> Oct 13 12:19:25 Tower kernel: next_to_watch <0> Oct 13 12:19:25 Tower kernel: jiffies <12773aa80> Oct 13 12:19:25 Tower kernel: next_to_watch.status <0> Oct 13 12:19:25 Tower kernel: MAC Status <80083> Oct 13 12:19:25 Tower kernel: PHY Status <796d> Oct 13 12:19:25 Tower kernel: PHY 1000BASE-T Status <3c00> Oct 13 12:19:25 Tower kernel: PHY Extended Status <3000> Oct 13 12:19:25 Tower kernel: PCI Status <10> Oct 13 12:19:27 Tower dhcpcd[1696]: br0: probing for an IPv4LL address I have been getting this error since Oct. 5th-6th and it was apparently unnoticed until today when my server became unresponsive, no GUI or SSH access, ethernet interface was down? Maybe, here is the picture of the monitor with the above message: Had to use a monitor to see what's happening, so far so good, Dockers and VMs were running just fine along with other services. But the above problem caught my eyes, thinking it's related. Diag. zip file is attached to this post down below. Thanks in advance!!1 tower-diagnostics-20181013-1219.zip edit: checked the syslog going back to July 2018 and it turns it started back then.
  7. did the instructions, check it down below link
  8. done, check the post down below and pass on the information if you could to help others!!!! link
  9. How to setup collabora online with Nextcloud behind reverse proxy, 3 steps: -Letsencrypt nginx conf file -Collabora docker configuration -Installing collabora app under admin account in nextcloud web page The key is to use another domain name for the collabora docker and nginx conf file. Meaning, if you have used cloud.* in letsencrypt nextcloud.subdomain.conf, then you gonna have to use office.* in you server directive of the collabora.subdomain.conf. ----First, let's create the collabora.subdomain.conf file in /mnt/user/appdata/letsencrypt/nginx/proxy-confs (assuming you are using the Unraid UI terminal and linuxserver letsencrypt docker). Put this code in above-created conf file: upstream collada-office { server your_local_unraid_server_adresss:9980; } server { listen 443 ssl; server_name office.example.com; include /config/nginx/ssl.conf; # static files location ^~ /loleaflet { proxy_pass https://collada-office; proxy_set_header Host $host; } # WOPI discovery URL location ^~ /hosting/discovery { proxy_pass https://collada-office; proxy_set_header Host $host; } # Main websocket location ~ /lool/(.*)/ws$ { proxy_pass https://collada-office; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_read_timeout 36000s; } # Admin Console websocket location ^~ /lool/adminws { proxy_buffering off; proxy_pass https://collada-office; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_read_timeout 36000s; } # download, presentation and image upload location ~ /lool { proxy_pass https://collada-office; proxy_set_header Host $host; } } ---Second, Go to your Unraid docker tab and edit the collaroba docker and make sure it looks like in the screenshot: ---Third, Install the collabora app under the admin account in Nextcloud account and use this down below: Restart all 3 dockers, NextCloud , Letsecncrypt, and Collabora_Online, everything should be up and running. BTW office.example.com should be also pointing to your home server, just like nextcloud.example.com domain. Good luck!!!!
  10. Sorry was away for a while, I see that you replied to my comment back in Sep. If you are interested, I am willing to write a tutorial with instructions and commands get it to work. PM me please and I will post the instructions here, it's kinda long
  11. Had the same problem after doing a reverse proxy setup, had to tweak some settings here and there. Are you using Collabora docker like me?
  12. Have you found the solution yet? I checked this link to get an idea how to fix it, but I got confused even more at this link
  13. Hey, thank you for the instructions. I am also trying to setup Nextcloud with a reverse proxy in conjunction with Letsencrypt, everything works, except the Collabora. Can you share your settings, please? So confused. Thanks!!!
  14. Exactly, I can't pass the controller unfortunately, I have 4 SATA ports on MB with single controller, passing an entire controller means, passing all my drives. I can possibly use my SATA expansion card to pass it to the VM, it will solve the problem. VM image is another issue, I have seen some posts regarding TRIM command inside of VM and how to set it up to make sure VM reports unused space to host. Good post (although a little unrelated) link edit: I thought you would be interested in this article link https://serverfault.com/questions/896448/qemu-trim-and-discard-on-a-physical-ssd-device It's pertinent to my issue, too bad I am no longer interested in this option anymore, I am not gonna be able to test it as of this moment. Ended up passing the entire controller by adding a dedicated PCI SATA HBA card to the motherboard. Thank you anyway!!!
  15. That's what's I figured, gotta do some testing to see if it works, these are just assumptions for now, will post results later. Thank you!!