awilderaid

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by awilderaid

  1. 6 hours ago, Froberg said:

    What's with the trusted_proxies line?

    Saw it posted somewhere while I was trying to find a fix for this. Just looked into it now, no idea what the 'letsencrypt' setting is supposed to be as it takes IP addresses. That's now fixed to read:

    'trusted_proxies' => 
      array (
        0 => '10.0.0.30',
        1 => '127.0.0.1',
        2 => '192.168.255.10',
      ),

    But no dice. Removing it completely also doesn't work. 

  2. 6 hours ago, Froberg said:

    As I set this up a few months ago I might actually be of use here.

    Assuming you set up the proxy-part correctly, maybe you're missing some steps in the owncloud config. (i.e. forcing https, maybe..)

    Check your config.pgp and ensure the following lines are present:

    
      'overwrite.cli.url' => 'your.domain.goes.here',
      'overwritehost' => 'your.domain.goes.here',
      'overwriteprotocol' => 'https',

    (substitute your own domain, of course.)


    You also need to make sure that the Nginx Proxy Manager and the NextCloud container is on the same ip address.

    Hi all,

    I'm having trouble getting Nextcloud setup with NPM, all I get is a 502 Bad Gateway. My Nextcloud config has:

    'trusted_domains' => 
      array (
        0 => '10.0.0.30:4039',
        1 => 'cloud.domain.com',
      ),
      'trusted_proxies' => ['letsencrypt'],
    
      'overwrite.cli.url' => 'https://cloud.domain.com/',
      'overwritehost' => 'cloud.domain.com',
      'overwriteprotocol' => 'https',

    and my NPM and Dockers are set out in the images. I've also tried with both dockers just set in the standard bridge network, but no dice. Any help would be greatly appreciated!

    details.png

    NPM details. Custom Locations is blank.

    ssl.png

    NPM SSL. Advanced is blank. 

    nextcloud.png

    npm.png

  3. On 6/19/2019 at 4:47 PM, awilderaid said:

    Hi all, this is a followup to my original post here of UD "dropping out" and showing 0B with my mellanox connectx-2 NICs. It's continued over the past few weeks intermittently. I've attached diagnostics from 3 occasions, the most recent being today, each set being downloaded a minute or so after Emby (or Plex) started stuttering and UD showed 0B.

    highgarden-diagnostics-20190612-0152.zip 66.41 kB · 1 download highgarden-diagnostics-20190612-0703.zip 65.17 kB · 1 download highgarden-diagnostics-20190619-1529.zip 74.72 kB · 2 downloads

    Has anyone been able to figure this out? I've tried a different NIC, a different cable, and moved the PCI slot the NICs are in on both servers and made no progress. Is there a way to monitor Samba or spit out some logs for it to see if that's maybe crashing and causing the issue? 

  4. On 5/30/2019 at 10:45 PM, awilderaid said:

    I haven't touched either server since posting this and tried to get the issue to reoccur and upload diagnostics. Everything now seems to be working perfectly, no stuttering, Emby's transcoding buffer stays between 2 and 3 minutes, UD shows accurate size/used/free information. My thought was that maybe SMB or NFS was giving up, and UD might have been involved. In any case, hopefully it doesn't happen again, but if it does I'll upload diagnostics as soon as. Cheers!

    Hi all, this is a followup to my original post here of UD "dropping out" and showing 0B with my mellanox connectx-2 NICs. It's continued over the past few weeks intermittently. I've attached diagnostics from 3 occasions, the most recent being today, each set being downloaded a minute or so after Emby (or Plex) started stuttering and UD showed 0B.

    highgarden-diagnostics-20190612-0152.zip highgarden-diagnostics-20190612-0703.zip highgarden-diagnostics-20190619-1529.zip

  5. 4 minutes ago, dlandon said:

    The size information showing as 0B is because it is taking too long and UD eventually gives up trying to determine the size so the UI is not totally frozen.  It sounds like a network issue.  It would help if you could post diagnostics for us to look at.

    I haven't touched either server since posting this and tried to get the issue to reoccur and upload diagnostics. Everything now seems to be working perfectly, no stuttering, Emby's transcoding buffer stays between 2 and 3 minutes, UD shows accurate size/used/free information. My thought was that maybe SMB or NFS was giving up, and UD might have been involved. In any case, hopefully it doesn't happen again, but if it does I'll upload diagnostics as soon as. Cheers!

  6. Hi,

     

    I have a pair of mellanox connectx-2 NICs, each in an unraid server. The first unraid server is a file server, the second a transcoding server. The NICs are plugged into each other - the file server having an IP of 192.168.11.1, the transcoding server an IP of 192.168.11.2. An iperf3 between them shows they're connected and have a good speeds happy days.

     

    I've the tried to mount the media share on the file server with unassigned devices. It initially shows up, displaying size, used, and free space. I turn on the docker service, fire up the Emby docker (being sure that the path to the media share has an access mode of RW/Slave) and try to play some media. Immediately there's buffering. Looking at the share in unassigned devices I now find the information for size, used, and free space all read 0B. Clicking on the mount point (to load the file list) takes a long time to load, but does eventually load, however the size information still shows 0B. 

     

    I've tried both NFS and SMB, Plex, and Jellyfin, and different mount point names. I've tried restarting and reinstalling UD. The system log and Emby's logs show nothing, and I was unable to find any specific logs for UD. 

     

    Any help would be greatly appreciated! 

    Screenshot from 2019-05-30 19-37-02.png

    Screenshot from 2019-05-30 19-35-30.png