Jump to content

luxinliang

Members
 View Profile  See their activity

  • Posts

    19

  • Joined

  • Last visited

 Content Type 

Posts posted by luxinliang

    [Solved] The Unraid server is unreachable from outside your network

    in Connect Plugin Support

    Posted

    16 minutes ago, ljm42 said:

    If port forwarding is working, then it is likely a DNS issue.

     

    Open a web terminal and type: 

    php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -v

     

    Paste the result in here. You can write "hash.unraid.net" instead of your actual hash if you want, and you don't need to include the externalport. Here is mine: 

    root@Monster:~# php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -v
Request:
{
    "internalip": "10.0.0.70",
    "internalport": "443",
    "internalprotocol": "https",
    "internalhostname": "hash.unraid.net",
    "plgversion": "2021.08.30.1204",
    "remoteaccess": "yes",
    "servercomment": "Monster server",
    "servername": "Monster",
    "externalport": "[removed]",
    "externalprotocol": "https",
    "externalhostname": "hash.unraid.net"
}
Response (HTTP 200):
[]
success

     

    Then, type this (use your actual hash, not "hash"): 

      ping www.hash.unraid.net

    does it resolve to the IP address that is listed on the My Servers settings page, where it says "Remark: your WAN IPv4 is .... "? 

     

    Please upload your diagnostics (from Tools -> Diagnostics) as well

    I wondered if it was because of the flash drive changing which may change the hash value too.

     

    So I deleted all the .pem files in config/ssl/, then reboot and re-provisioned the certificate file. After that, this issue solved.

    [Solved] The Unraid server is unreachable from outside your network

    in Connect Plugin Support

    Posted

    Hi, I installed this plugin a few days ago, and the remote access worked fine.

     

    But recently, I've changed my flash drive and re-installed this plugin, then the server couldn't reach my unraid server

    image.png.3db0a48b7e77344355e9a13429615c48.png

     

    But I've set up my router's port forwarding correctlly. And the tcping tool can open the outer port 1443 (using cellphone hot spot).

    773270304_2021-08-31085230.jpg.ad45fd28c15bdabb3ba1b80976f65866.jpg

     

    And I can also use the https protocol and ip with 1443 port to remotely open the management web (using cellphone hot spot).

    1786500087_2021-08-31085347.thumb.jpg.bd080af926e4e22ec9354d2ef228d2ec.jpg

     

    So can anyone help me with the official remote access?

    image.thumb.png.cc6cd8d1b43a5e89ae33e5b66438836f.png

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    5 minutes ago, ich777 said:

    This is very unlikely that you get such a huge perfomance boost with QSV.

     

    Also keep in mind that even if you enable throttling in Jellyfin that it doesn't work because they disabled it in general because it caused trouble with HW acceleration.

     

    Hardware transcoding is really hard to measure with applications like Emby/Jellyfin/Plex, in my oppinion the only real benchmark is how many simultaneous streams you can encode without stuttering.

    Ok, I'll watch it out, thx for sharing. Also, this is a great docker project😘.

    • Like 1

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    14 minutes ago, ich777 said:

    Because it's basically the same and has no real advantage/disadvantage.

     

    The only disadvantage from QuickSync is that it's proprietary and if Intel decides to depricate certain CPU architectures, like it happened lately in the Media Drivers, then QuickSync isn't working anymore like it happened for my test sytem J3xxx series and I wondered why in my Container QuickSync doesn't work anymore after switching my Container to the newest version, where on my i5-10600 system it worked flawlessly now I'm back on VAAPI on both systems. ;)

    I see, in my system, when using QSV to transcode hevc videos, it can achieve up to 30 fps more than VAAPI, but the cpu usage is also 10%-20% more.

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    1 hour ago, ich777 said:

    Never use the same folder for two instances of anything if it's a cache or working directory...

     

    Don't know exactly which permissions the original Jellyfin container uses but my containers never run as root by default.

     

    So it is now working?

    Got it! It is working right now, thx for your help!

    BTW why you recommend to use VAAPI transcoder instead of QSV?

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    5 minutes ago, ich777 said:

    What didn't work? What where the exact steps that you did? Hope you don't downloaded it from the CA App because that would overwrite you local template.

     

    I tested it now on my system and I can't reproduce this issue.

    Everything is generated just fine, found a few issues on the Jellyfin Github issue tracker with the same issue but they are all open ond not solved. Looks like to me that is specific to a few installations from users, even the official Jellyfin container has that issue.

     

    If you've enabled the iGPU VAAPI should always work, I would always recommend to use VAAPI instead of QuickSync.

    A buddy from me has the same system with my Jellyfin container running and I've told him that he should keep am eye on it if he has the same error if he add files.

    Well, re-add the container can't eliminate the errors. Also both VAAPI and QSV transcoder work fine, just the images issue.

     

    6 minutes ago, ich777 said:

    Do you use the same folder for both instances from Jellyfin on your system?

     

    Have you reset the permissions on unRAID or changed disks or something like this?

    Has the cache disk enough space on it?

     

    As said above can't reproduce this issue, even not on my second test system.

    Yes, I did use the same folder for both of them, and after creating the cache folder in another disk it worked properly.

     

    I think the whole thing is a simple access permissions thing and sorry for taking up your time.

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    2 hours ago, ich777 said:

    This is really strange... I'm not experiencing this issue.

    Can you try to delete the container entirely (but don't delete the folders for the container on the host) and then add it back with the button "Add Container" ont he bottom on the Docker page and choose the template from the drop down, so nothing has to be configured again.

     

    Do you use a hardware transcoder?

     

    This error indicates that something is wrong with the extraction from an image from the video file...

    Hi again, I may find the solution.

     

    I noticed that an error said the cache folder denided to write, so I deattached the cache folder which passed to the docker and deleted "--volume /mnt/cache/jellyfin-cache:/cache". Then everything is back to work, I can grab the images! After that, I also tried to modify the cache folder's permission or create another one, but none of them worked.

     

    I think it is a bug, and somehow the original jellyfin don't come across this cache folder issue.

    • Like 1

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    2 hours ago, ich777 said:

    This is really strange... I'm not experiencing this issue.

    Can you try to delete the container entirely (but don't delete the folders for the container on the host) and then add it back with the button "Add Container" ont he bottom on the Docker page and choose the template from the drop down, so nothing has to be configured again.

     

    Do you use a hardware transcoder?

     

    This error indicates that something is wrong with the extraction from an image from the video file...

    BTW my cpu is intel J4105 with UHD Graphics 600

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    2 hours ago, ich777 said:

    This is really strange... I'm not experiencing this issue.

    Can you try to delete the container entirely (but don't delete the folders for the container on the host) and then add it back with the button "Add Container" ont he bottom on the Docker page and choose the template from the drop down, so nothing has to be configured again.

     

    Do you use a hardware transcoder?

     

    This error indicates that something is wrong with the extraction from an image from the video file...

    I did try to re-add the container, but that didn't work.

    And I also try using the QSV, VAAPI and none hardware transcoder, while ffmpeg still throw the same error in all of them.

    [Support] ich777 - Jellyfin AMD/Intel/Nvidia [DEPRECATED]

    in Docker Containers

    Posted

    9 hours ago, ich777 said:

    This is a well known issue with Emby and also Jellyfin, sometimes the pictures can't be fetched.

     

    I think this is happening only for a few movies/series or am I wrong?

     

    What do you mean exactly with original Jellyfin?

    Thx for your reply. The original jellyfin means the docker image jellyfin/jellyfin.

     

    In fact, the container based on your docker image can't get any episodes' images (not just a few) and keep throwing errors "MediaBrowser.MediaEncoding.Encoder.MediaEncoder: ffmpeg image extraction failed for file" and “MediaBrowser.Providers.TV.EpisodeMetadataService: Error in Screen Grabber”.

     

    When using the docker image jellyfin/jellyfin with same version 10.7.6 don't come across this problem. I even try setting the same parameters and passing the same config, cache, media folders for both of them, while the original jellyfin works fine, your jellyfin still pops out the same errors.

     

    Can you help me with that?

    lost VM manager's configs and can't automatically start it after unsafe reboot

    in VM Engine (KVM)

    Posted

    11 hours ago, JorgeB said:

    That's very strange, like mentioned the VM settings (not the VM XL) are stored on the flash drive, once store, and they are now, it should never revert back, don't remember seeing this issue before.

    Actually, this issue is similar to the post beside the reverting thing, maybe he didn't change the default settings.

     

    I guessthis issue might be ralative to the array or the docker service or both. I'm still during my trial, after each unsafe power cycle, the connection to the offical certification server is somehow later than normal (also the network is not stable in my area), same with the array, thus the VM manager won't start automatically trigering some bugs to revert the settings.

     

    Or  docker service is boot up earlier than VM service, I also notice when manually start the service after power failure there might be chance unabling to do that, it said "libvirt.img is in use". Turns out, a docker container called "jellyfin" is using it, but I have never passed the libvirt.img folder to docker.

     

    So the whole thing is quite weird to me.

     

×
×
  • Create New...