Aceriz

Members
  • Posts

    206
  • Joined

Posts posted by Aceriz

  1. Hi all.

     

    So tonight I had to turn off my tower.  When it went to restart  it kept getting stalled on the unraid selection  page during the boot up.   Kept saying the file does not exist ..Would not go past this.  So I turned the tower off again. 

     

    I actually had a usb flash backup made from 2 days ago. As per spaceinvader video.

     

    When I use the USB creation on the local zip  of my backup to recreate the flash drive.  I keep getting stalled.. at same page but this time am  not even seeing any error or messages....

     

     

    So not sure what to do.   If I create a new usb with creation tool how will I know what drives go where.... 

     

    any help would be great.  I am happy try stuff that won't risk the data....

    And can give more info too if needed. 

     

  2. 21 hours ago, Aceriz said:

    I just updated the duplicati docker.  It had been working before. But now not working. Any one else having issues ??

    This is the log I see in for the docker....

     


    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    [s6-init] ensuring user provided files have correct perms...exited 0.
    [fix-attrs.d] applying ownership & permissions fixes...
    [fix-attrs.d] done.
    [cont-init.d] executing container initialization scripts...
    [cont-init.d] 01-envfile: executing...
    [cont-init.d] 01-envfile: exited 0.
    [cont-init.d] 10-adduser: executing...

    -------------------------------------
    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/


    Brought to you by linuxserver.io
    -------------------------------------

    To support LSIO projects visit:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------

    User uid: 99
    User gid: 100
    -------------------------------------

    [cont-init.d] 10-adduser: exited 0.
    [cont-init.d] 30-config: executing...
    [cont-init.d] 30-config: exited 0.
    [cont-init.d] 99-custom-scripts: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-scripts: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.

  3. 7 hours ago, tknx said:

    I have the same thing.  The current situation is kind of messy since it was installed song docker compose so Portainer is pretty much like “it isn’t mine” and Unraids docker manager isn’t like “not me!”   
     

    I will probably reinstall the stack in Portainer or hopefully someone will roll an Unraid docker for jitsi that works well. It would actually be nice if they were rolled into one just for convenience. 
     

    also if you are using Nginx Proxy Manager, you need to expose port 5280 on the prosody container in Portainer. 

    I wonder if you can explain how you might go about installing in portainer:?

     

    Also would this get rid of the errors seen above? as I agree with comment by @Osopolar  that my OCD does not like seeing errors or things saying they need updates. 

     

    I have tried updating via the portainer route described above. It did update by look of it. But on docker page still see the "update available." warning.. 

     

  4. 12 hours ago, OsoPolar said:

    HI Guys

    Mine works just like it says on the tin from the video

    But i am seeing some errors in Fix common problems

    Has anybody got the same errors and how do you fix them.

    Do not say hit the Apply Fix button as it does not work :)

     

    Please can you explain how to fix this issue if you have managed to fix it?

    Screenshot- 269.png

    I am also seeing this error.   Everything with the meetings appear to work.  But it is frustrating to have errors...  if you figure out how to fix let me know.  

     

    Also I am wondering  how so we update

  5. On 4/24/2020 at 10:24 PM, Aceriz said:

    Hey so I continue to have problems getting things setup past the letsencrypt part.   I think I have narrowed it down a bit... 

     

    I have noticed that in Portainer,  after I add the proxy network to each of the 4 jitsi dockers. . The dockers at times appear to be dropping the IP address.. (IE they randomly appear to be going in and out on the stack page. and also within the docker its self.  I feel this may be leading to the Letsencypt being unable to identify the upstream meet.jitsi as it tried to authenticate...  

     

    Any thoughts as to how to trouble shoot this further.  Thanks all:) :)

     

    I copy the error I get in Letsencrypt  here :

    nginx: [emerg] host not found in upstream "xmpp.meet.jitsi" in /config/nginx/proxy-confs/jitsimeet.subdomain.conf:23
    nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size

    So I continue to have ongoing issue. In troubleshooting this. I have a question for the community. 

     Are there any recommendations against having 2 separate user defined networks with  two different installs of Letsencypt.  One on each of these networks.  ie like a proxynet 1, and proxynet 2.. 

     

    I ask as I already have a letsencypt setup working with things like nextcloud, emby, open office etc.  

     

    And to troubleshoot the issue with Jitsi thinking of setting it up on it own letsencypt..With essentially nothing else. 

     

    Unless others have thoughts on why the IP keep dropping.  If you need logs or things please let me know I am happy to provide:) 

  6. Hey all,

     

    Hoping that someone can help me. I have Letsencrypt up and working for a number of dockers. With a Proxynet setup. 

     

    I am trying to configure the new Jitsi from Spaceinvader one's setup.   When I get to the point of switching over to the Proxynet for each of the jitsi dockers. The IP addresses appear to drop in and out for the dockers...  This I believe maybe an issue with the proxynet. or perhaps letsencypt.   But I am not sure... 

     

    As I wasn't sure if this was a problem with Jitsi or letsencypt I thought it best to ask

     

  7. Hey so I continue to have problems getting things setup past the letsencrypt part.   I think I have narrowed it down a bit... 

     

    I have noticed that in Portainer,  after I add the proxy network to each of the 4 jitsi dockers. . The dockers at times appear to be dropping the IP address.. (IE they randomly appear to be going in and out on the stack page. and also within the docker its self.  I feel this may be leading to the Letsencypt being unable to identify the upstream meet.jitsi as it tried to authenticate...  

     

    Any thoughts as to how to trouble shoot this further.  Thanks all:) :)

     

    I copy the error I get in Letsencrypt  here :

    nginx: [emerg] host not found in upstream "xmpp.meet.jitsi" in /config/nginx/proxy-confs/jitsimeet.subdomain.conf:23
    nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size

  8. Hey, So I have followed Spaceinvaders video to the T.   But am seeming to have problems when I hit the setting up of the Letsencrypt reverse proxy. (which I have running for a bunch of other things. thanks to Spaceinvader).  

     

    I am using __abc_.duckdns.org  subdomain that I have also added to the letsencrypt  docker edit page.    Have ensured change in the downloadable config file.  but in Letsencrypt log get the following error.. any ideas  Have renamed all the dockers in Portainer.  Which then shows up on the docker tab of unraid..  But on that page I am getting under version "unable to tell"  and the network didn't change to represent the change in portainer... 

     

    "nginx: [emerg] host not found in upstream "xmpp.meet.jitsi" in /config/nginx/proxy-confs/jitsimeet.subdomain.conf:23
    nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size"

  9. 46 minutes ago, Squid said:

    Also possible

     

     

    Thanks, 

     

    I have added the restriction memory to duplicati 3gb,  also decreased the size of the ram disk to 5gb 

    then reset the system to see if this helps out. .  . 

     

      If anyone else has ideas of why it might be filling let me know.  I am also happy to repost diagnostics or other information if it will help 

  10. 5 minutes ago, Squid said:

    Top of my head, your memory is very fragmented and the VM is unable to allocate what it needs.  A reboot should fix it, but you might want to consider limiting the memory available for Duplicati (I would think that it's a pig on resource usage)

    Hi Squid thanks for such a quick reply. 

     

    how do I go about Limiting the memory available for Duplicati?  Sorry if this seems to be an easy answer..

     

    Also not sure if it would make a difference,  But your comment made me think about a change I made like 1-2 months ago.  Where I set up a Ram-disk for plex transcoding with the following:  script found in the Plex-forum dialogue.    Do you think this might be causing it?  I set up the ram disk as I didn't want to keep using SSD for transcoding(as I had been doing for last 2 years. But happy to go back to that if it might be the cause.  

     

    #!/bin/bash
    mkdir /tmp/PlexRamScratch
    mount -t tmpfs -o size=8g tmpfs /tmp/PlexRamScratch
     

  11. Hi all, 

     

    I hope that someone might be able to help me out with coming to the bottom of a recurrent issue that I have been having over the last 1-2 weeks. I am not sure why by the Syslog has been filling incredible fast.  Never used to do this. I can't remember if I changed anything that would cause syslog to fill. 

     

    I have attached two diagnostics files.  One from just after a system reset. Then one from today where after 3 days syslog is at 60%. .

     

    I will apologize if this ends up being a stupid simple things.  I am still learning.  But hope someone can help me out. 

     

     

    rizznetunraid-diagnostics-20200321-1355.zip rizznetunraid-diagnostics-20200317-2038.zip

  12. Hey hoping someone can help.  Trying to update from 18.01-18.02  as following Spaceinvaders in docker get error at the Backup stage as following.  No matter how many times I try to retry it does not work.  Any ideas?

     

     

    Parsing response failed. <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->

  13. 4 hours ago, Aceriz said:

    Hey wondering if anyone else is having problem with their NC docker.  I had everything up and running with NC going through Letsencrypt. 

    Just finished updating the dockers and now getting the following error

    "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."

     

    Had not changed anything but updating the docker through unraid interface.. 

    Here is also my nextcloud log

     

    -------------------------------------
    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/


    Brought to you by linuxserver.io
    We gratefully accept donations at:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------

    User uid: 99
    User gid: 100
    -------------------------------------

    [cont-init.d] 10-adduser: exited 0.
    [cont-init.d] 20-config: executing...
    [cont-init.d] 20-config: exited 0.
    [cont-init.d] 30-keygen: executing...
    using keys found in /config/keys
    [cont-init.d] 30-keygen: exited 0.
    [cont-init.d] 40-config: executing...
    [cont-init.d] 40-config: exited 0.
    [cont-init.d] 50-install: executing...
    [cont-init.d] 50-install: exited 0.
    [cont-init.d] 60-memcache: executing...
    [cont-init.d] 60-memcache: exited 0.
    [cont-init.d] 99-custom-files: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-files: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.

  14. 16 minutes ago, Aceriz said:

    Hey wondering 

    Hey wondering if anyone else is having problem with their Next cloud docker/ letencrypt docker.  I had everything up and running with NC going through Letsencrypt. 

    Just finished updating the dockers and now getting the following error

    "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."

     

    Had not changed anything but updating the dockers  through unraid interface.. 

     

    I can try and post logs of things just not sure where to grab them. 

     

     

    Here is also my Nexcloud log 

     

    -------------------------------------
    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/


    Brought to you by linuxserver.io
    We gratefully accept donations at:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------

    User uid: 99
    User gid: 100
    -------------------------------------

    [cont-init.d] 10-adduser: exited 0.
    [cont-init.d] 20-config: executing...
    [cont-init.d] 20-config: exited 0.
    [cont-init.d] 30-keygen: executing...
    using keys found in /config/keys
    [cont-init.d] 30-keygen: exited 0.
    [cont-init.d] 40-config: executing...
    [cont-init.d] 40-config: exited 0.
    [cont-init.d] 50-install: executing...
    [cont-init.d] 50-install: exited 0.
    [cont-init.d] 60-memcache: executing...
    [cont-init.d] 60-memcache: exited 0.
    [cont-init.d] 99-custom-files: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-files: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.

  15. 15 minutes ago, Aceriz said:

    Hey wondering 

    Hey wondering if anyone else is having problem with their Next cloud docker/ letencrypt docker.  I had everything up and running with NC going through Letsencrypt. 

    Just finished updating the dockers and now getting the following error

    "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."

     

    Had not changed anything but updating the dockers  through unraid interface.. 

     

    I can try and post logs of things just not sure where to grab them. 

     

     

    Here is my Lestencrypt log- I did delete email and actual subdomains but have verified they are correct. 

     

    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/


    Brought to you by linuxserver.io
    We gratefully accept donations at:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------

    User uid: 99
    User gid: 100
    -------------------------------------

    [cont-init.d] 10-adduser: exited 0.
    [cont-init.d] 20-config: executing...
    [cont-init.d] 20-config: exited 0.
    [cont-init.d] 30-keygen: executing...
    using keys found in /config/keys
    [cont-init.d] 30-keygen: exited 0.
    [cont-init.d] 50-config: executing...
    Variables set:
    PUID=99
    PGID=100
    TZ=America/Halifax
    URL=duckdns.org
    SUBDOMAINS=*****List of my subdomains****
    EXTRA_DOMAINS=
    ONLY_SUBDOMAINS=true
    DHLEVEL=2048
    VALIDATION=http
    DNSPLUGIN=
    EMAIL=***my email
    STAGING=

    2048 bit DH parameters present
    SUBDOMAINS entered, processing
    SUBDOMAINS entered, processing
    Only subdomains, no URL in cert
    Sub-domains processed are: -***listed at -d mysubdomains 
    E-mail address entered: ***@gmail.com
    http validation is selected
    Certificate exists; parameters unchanged; starting nginx
    [cont-init.d] 50-config: exited 0.
    [cont-init.d] 99-custom-files: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-files: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.
    Server ready
    nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
    nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
    no field package.preload['resty.core']
    no file './resty/core.lua'
    no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
    no file '/usr/local/share/lua/5.1/resty/core.lua'
    no file '/usr/local/share/lua/5.1/resty/core/init.lua'
    no file '/usr/share/lua/5.1/resty/core.lua'
    no file '/usr/share/lua/5.1/resty/core/init.lua'
    no file '/usr/share/lua/common/resty/core.lua'
    no file '/usr/share/lua/common/resty/core/init.lua'
    no file './resty/core.so'
    no file '/usr/local/lib/lua/5.1/resty/core.so'
    no file '/usr/lib/lua/5.1/resty/core.so'
    no file '/usr/local/lib/lua/5.1/loadall.so'
    no file './resty.so'
    no file '/usr/local/lib/lua/5.1/resty.so'
    no file '/usr/lib/lua/5.1/resty.so'
    no file '/usr/local/lib/lua/5.1/loadall.so')

  16. Here is my Lestencrypt log- I did delete email and actual subdomains but have verified they are correct. 

     

    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/


    Brought to you by linuxserver.io
    We gratefully accept donations at:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------

    User uid: 99
    User gid: 100
    -------------------------------------

    [cont-init.d] 10-adduser: exited 0.
    [cont-init.d] 20-config: executing...
    [cont-init.d] 20-config: exited 0.
    [cont-init.d] 30-keygen: executing...
    using keys found in /config/keys
    [cont-init.d] 30-keygen: exited 0.
    [cont-init.d] 50-config: executing...
    Variables set:
    PUID=99
    PGID=100
    TZ=America/Halifax
    URL=duckdns.org
    SUBDOMAINS=*****List of my subdomains****
    EXTRA_DOMAINS=
    ONLY_SUBDOMAINS=true
    DHLEVEL=2048
    VALIDATION=http
    DNSPLUGIN=
    EMAIL=***my email
    STAGING=

    2048 bit DH parameters present
    SUBDOMAINS entered, processing
    SUBDOMAINS entered, processing
    Only subdomains, no URL in cert
    Sub-domains processed are: -***listed at -d mysubdomains 
    E-mail address entered: ***@gmail.com
    http validation is selected
    Certificate exists; parameters unchanged; starting nginx
    [cont-init.d] 50-config: exited 0.
    [cont-init.d] 99-custom-files: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-files: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.
    Server ready
    nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
    nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
    no field package.preload['resty.core']
    no file './resty/core.lua'
    no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
    no file '/usr/local/share/lua/5.1/resty/core.lua'
    no file '/usr/local/share/lua/5.1/resty/core/init.lua'
    no file '/usr/share/lua/5.1/resty/core.lua'
    no file '/usr/share/lua/5.1/resty/core/init.lua'
    no file '/usr/share/lua/common/resty/core.lua'
    no file '/usr/share/lua/common/resty/core/init.lua'
    no file './resty/core.so'
    no file '/usr/local/lib/lua/5.1/resty/core.so'
    no file '/usr/lib/lua/5.1/resty/core.so'
    no file '/usr/local/lib/lua/5.1/loadall.so'
    no file './resty.so'
    no file '/usr/local/lib/lua/5.1/resty.so'
    no file '/usr/lib/lua/5.1/resty.so'
    no file '/usr/local/lib/lua/5.1/loadall.so')

  17. Hey wondering 

    Hey wondering if anyone else is having problem with their Next cloud docker/ letencrypt docker.  I had everything up and running with NC going through Letsencrypt. 

    Just finished updating the dockers and now getting the following error

    "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."

     

    Had not changed anything but updating the dockers  through unraid interface.. 

     

    I can try and post logs of things just not sure where to grab them. 

     

     

  18. Hey wondering if anyone else is having problem with their NC docker.  I had everything up and running with NC going through Letsencrypt. 

    Just finished updating the dockers and now getting the following error

    "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."

     

    Had not changed anything but updating the docker through unraid interface.. 

  19. Hope that someone can help me out..  I have managed to set up Nextcloud via the Spaceinvader videos. Everything appears to be working well. 

     

    I am wanting however to setup the Clamav  Antivirus,  I have added the app for this in NC. Gone to the the settings tab in security. but I am having trouble figuring out how to configure clamav with my external docker container available on the apps tab 

    ClamAV
    tquinnelly
    Tools:Utilities, Security

     

    I have tried to add this a a daemon with links to clamav docker with added port of 3310.  

     

    but I get error of 

    [files_antivirus] Error: RuntimeException: The ClamAV module is not in daemon mode. at <<closure>> in the logs of NC. 

    Any thoughts and help would be great:) 

     

    thanks