Wong

Members
  • Posts

    62
  • Joined

  • Last visited

Posts posted by Wong

  1. image.png.9214a4d6ea1d2db445fc4ecfc7d27b4a.png

    image.thumb.png.41fdacad1f9ffdfc6a849dd98d92221a.png

     

    History: I recently converted my cache_sata pool to ZFS but only a single drive. I have added a new SSD to my cache_sata pool and it auto-mirror it. During mirror process, I accidentally stopped the array and unselected the new SSD from the pool from the Main tab as I was unaware the mirror as already running. After that, I allow it to mirror and it has completed successfully. However, ZFS Master stated my ZFS pool is DEGRADED. and my two cache_sata drive is unmountable. Though all this error appear, my docker and array are working normally. Please assist to advise on how remove the umountable error and the DEGRADED status without destroying my cache data.

     

    Im still very new to ZFS, so any advise posted, please assist to show the exact command for me to run. Thank you in advance for the helps.

  2. On 10/28/2022 at 1:57 AM, Wong said:

    image.thumb.png.d458760a1b049cd33e37f56f08505275.pngI am getting postgresql issue with only office docker. Although the docker able to start, I cannot connect to nextcloud. Anyone facing the same issue? Anyone could you share or have any idea what I can do?

     

    Just a record for anyone in the future encounter similar issue as me. I manage to solve it.

    Step 1: Remove the existing onlyoffice docker and it's image. Make sure to also delete onlyoffice file inside the appdata share.

    Step 2: Reinstall the onlyoffice docker. As of 15/11/2022, the docker template had one small issue. Credit to @eyesfit. Please edit the Database path as shown in below. image.thumb.png.5dfec507254ecd5978fecc7c34521fca.png

     

    Step 3: Remember to save or edit your secret keys. Then click apply.

    Step 4: Copy your cert.crt, cert.key and fullchain.pem from your nginx manager or swag to the /mnt/user/appdata/onlyofficeds/Data. Do not create a cert folder and put in there. This will cause your OnlyOffice to failed to start due to nginx config error.

    Step 5: Rename your cert.crt to onlyoffice.crt , cert.key to onlyoffice.key , fullchain.pem to dhparam.pem .

    Step 6: Do not follow the Spaceinvader video regarding the nginx template. Use the latest documentserver template in your nginx manager or swag. And adjust accordingly to your domain.

    Step 7: Restart docker for everything related. DONE! you good to go with the latest version. 

     

    Please give a like my comment if it help you! thanks

  3. My cache drive is almost full. So I recently added new SSD to my unraid and use it as a additional cache drive, and named cache pool as "cache_sata". 

     

    I configurate to move all my existing file such as appdata and etc to "cache_sata". I configurate my existing cache to the "Prefer" into the "cache_sata" and invoked mover to move everything. Everything including the docker image moved perfectly, except my appdata share. Please have a look of the screenshot of what I mean. It got split into two regardless if I have forced to "Prefer" to "cache_sata" only. Some appdata content still and currently getting modified in both cache pool.

     

    Before upgrade, I have an existing ssd drive, was named cache pool as "cache". However, after invoked the mover, I only renamed the existing SSD drive from "cache" to "cache_nvme". 

    image.thumb.png.3a9d78bd0aabf2cbad56d98c56586d63.png

    Not sure if this help. Is for your reference.

    image.png.3ab670648cd0e2df9178b2672fdadb27.png

     

    Now I want to move all my appdata content to only "cache_sata" only. Anyone could suggest what I can do?

    • Upvote 1
  4. Anyone here having some issue loading the only office when opening a document in nextcloud? Mine keep buffering very long before open my document. And most of the time, it buffer indefinitely. However, if I clear browser cache or uses incognito, it load without any issue. I uses Brave browser. 

  5. I have manage to passthrough GPU but how can I passthrough the onboard microphone so that I can just plug my headphones into the audiojack and get an audio input on my windows.

     

    Below are my IOMMU group for reference. I can see my intel audio devices are not in its onw IOMMU group. So is not possible to passthrough the onboard soundcard? If is not possible to separate the group. It is possible if I just buy a "usb to female audio jack adapter" into one of the usb port, then plug my headphone into the adapter, and passthrough as a usb devices. Will that work?

     

    image.png

  6. Have anyone successfully reverse proxy this docker using swag provided qbittorrent subdomain conf. file? If anyone could help me see if I did any mistake to the swag conf. file.

    image.thumb.png.4a10f1cd6b0c5aa34f8b787b1f293a69.png

     

    ## Version 2021/05/18
    # make sure that your dns has a cname set for qbittorrent and that your qbittorrent container is not using a base url

    server {
        listen 443 ssl;
        listen [::]:443 ssl;

        server_name qbit.*;

        include /config/nginx/ssl.conf;

        client_max_body_size 0;

        # enable for ldap auth, fill in ldap details in ldap.conf
        #include /config/nginx/ldap.conf;

        # enable for Authelia
        #include /config/nginx/authelia-server.conf;

        location / {
            # enable the next two lines for http auth
            #auth_basic "Restricted";
            #auth_basic_user_file /config/nginx/.htpasswd;

            # enable the next two lines for ldap auth
            #auth_request /auth;
            #error_page 401 =200 /ldaplogin;

            # enable for Authelia
            #include /config/nginx/authelia-location.conf;

            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app binhex-qbittorrentvpn;
            set $upstream_port 8585;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

            proxy_set_header Referer '';
            proxy_set_header Host $upstream_app:$upstream_port;
        }

        location ~ (/qbittorrent)?/api {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app binhex-qbittorrentvpn;
            set $upstream_port 8585;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

            rewrite /qbittorrent(.*) $1 break;

            proxy_set_header Referer '';
            proxy_set_header Host $upstream_app:$upstream_port;
        }

        location ~ (/qbittorrent)?/command {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app binhex-qbittorrentvpn;
            set $upstream_port 8585;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

            rewrite /qbittorrent(.*) $1 break;

            proxy_set_header Referer '';
            proxy_set_header Host $upstream_app:$upstream_port;
        }

        location ~ (/qbittorrent)?/query {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app binhex-qbittorrentvpn;
            set $upstream_port 8585;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

            rewrite /qbittorrent(.*) $1 break;

            proxy_set_header Referer '';
            proxy_set_header Host $upstream_app:$upstream_port;
        }

        location ~ (/qbittorrent)?/login {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app binhex-qbittorrentvpn;
            set $upstream_port 8585;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

            rewrite /qbittorrent(.*) $1 break;

            proxy_set_header Referer '';
            proxy_set_header Host $upstream_app:$upstream_port;
        }

        location ~ (/qbittorrent)?/sync {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app binhex-qbittorrentvpn;
            set $upstream_port 8585;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

            rewrite /qbittorrent(.*) $1 break;

            proxy_set_header Referer '';
            proxy_set_header Host $upstream_app:$upstream_port;
        }
    }

     

  7. 1 hour ago, JorgeB said:

    Several issues, but first please reboot and post the complete diagnostics after array start.

    Hi, thanks for the reply. After I rebooted, everything goes back to normal. I was worrying if I reboot, my file would get corrupted after reading some old forum about cache drive been full. But clearly, it wasn't the case. 

     

    For future reader, this issue arrive when I was transferring a single big file into my cache drive without realising my cache drive is full, which cause an internal error in my Unraid server. After I invoke the Mover, my cache drive is clear up. Then, I rebooted my server. It all went back to normal operation.

  8. I am not sure what is the issue here. All my docker stop working. And everytime I try to restart it, it gave me this error code 403. I read some forum said is the log file is too full or something. Can anyone help me with this? I attached the system log file below. Let me know if there any other log file you want to see through command line. Just a headups, I am not good with command line.

    image.thumb.png.a4def06eaa2b9ff5c1903c03500e0339.png

    tower-syslog-20210116-0743.zip

  9. 6 minutes ago, skois said:

    You probably tried to execute the command on the unraid's terminal.
    This command is to be runned bu the nextcloud container. So, 
    click on the NC docker and click console. Run the mentioned command there

    Your feedback solved my problem. Yeah I was running on the Unraid terminal instead of the docker console. Thanks for the helps!!! 

    • Like 1
  10. 3 minutes ago, skois said:

    The command is in the first line of the warning...
    occ db:add-missing-primary-keys

     

    Also this have nothing to do with the updater errors you got on the updater.
    On this version NC made some changes in the database, and need to add some primary keys :)

    Thanks for the quick reply, you guys are awesome. I am still quite bad at terminal command. I just copy and pasted the command line just now, it stated command not found. Could you list down all the command line I should execute? Thanks.

  11. When I install the docker by nunofgs, I got the following errors. Is it because it cannot detect my 3D printer? I am using Creality Ender-3.

     

    docker: Error response from daemon: error gathering device information while adding custom device "/dev/ttyACM0": no such file or directory.

    image.thumb.png.73923124af0e3cf6ebcb2d0e00be1a12.png

    This is my template input.image.thumb.png.1951f8a8e2f74e243d775a1fb0e36470.png