Server Version#: 1.15.2.793
Player Version#:
I recently reinstalled my PLEX and I started to re-scan everything.
I am keeping getting the error “Error issuing curl_easy_perform(handle): 28”.
And during the scan the whole plex cannot obtain the server settings.
The scanning is not completing
I know something gets wrong. Please help me to look at the logs to see what’s going wrong.
Thank you.
I am using 10G network and to turn off jumbo frames, it will reduce the speed of transfer for the large files. Is there any way to let the feature enabled and to use PLEX?
Otherwise, I will turn off and I will reinstall the package. I will then post the logs for your checking. Thank you.
Unless you know precisely what you’re doing, jumbo frames make an absolute mess.
I have 10 Gb here. Pulling 1.2 GB/sec over it on regular MTU is not a problem.
If you really need that much bandwidth, you have bigger issues.
I just disabled jumbo frame. I deleted the old package and installed the new one.
Please help to check whether there are any other errors.
Did you only uninstall Plex in Package Center or did you perform a full uninstallation?
A full removal entails:
what I am seeing implies the previous metadata / configuration was never removed.
I have a synology RS18017xs. I setup a link aggregation with 2 X 10G on the Lan network and I am using a 2 x 10G network card for a client computer, connected by a netgear 10G-base-t switch. Without enabling MTU to 9000, my transfer speed is on average 120MB/s. To enable MTU to 9000, I can transfer at around 500MB/s.
I am quite reluctant to disable this…this will make the 10G card completely useless.
I did the step 1 and 2…didn’t go to step 3.
I have 36 libraries to re-install if go to step 3.
I was not aware some of the errors may require go that step.
I will delete the folder if that will assist.
Please reply to confirm. Thx again for your prompt reply.
If you are only able to get 120 MB/sec from the Synology, the problem is not your network.
I have a simple DS1815+ with 4x 1 GbE, aggregated and it will deliver 468 MB/sec to my 10 GbE QNAP.
I submit you have a completely different problem and it’s not at the physical network layer.
What protocol is being used to transfer the files with?
What are the client link speeds?
Here are 6 individual - 1GbE clients writing to the 10 GbE host.
I would like you to do the following to address the scanning issue.
Stop Plex
Control Panel - Shared Folders - Verify user Plex has permission to read the media shares you will be using.
Open the Plex share in File Station (Give your username permission if you don’t see it)
Rename Library to Library.keep
Start Plex
It will create a new instance. This is expected (your original is safe)
Give it a test name (“TEST”) so it can easily be deleted later.
Add your smallest media share to it.
Finish creating the library and then proceed to the Dashboard
If this fails to start matching media., I would like to see the logs:
A. Settings - Server - Troubleshooting - Download Logs
B. Attach that ZIP file here.
I have Raid 6 for 12 seagate enterprise SATA Disks on the NAS rs18017xs. I stored some movies on that volume (“Movie Volume”). I have another RAID 6 on the linked unit and I stored some tv series on that volume (“TV Volume”). I have another RAID 6 for the same brand disks on the NAS DS3615xs (“Backup Volume”) I have a windows 10 desktop client drive mapping the Movie Volume, TV Volume and Backup Volume. I have CIFS connection and once I copy paste the files among the volumes and transfer speed on all the volumes is about 120MB/s.
And thoughts on the issue?
Yep… have a few thoughts.
Windows is your bottleneck. SMB 3.0 to be specific.
While windows might do SMB 3.1 or even higher, Synology is stuck at SMB 3.0
This limits you really badly to the practical limit of about 35 MB/sec on a 1 GbE link. It’s a horrifically bad protocol and only SMB 3.1 can really help out.
Just to check the boxes, here is how I have SMB configured even though I don’t use it ( I am entirely NFS )
You are correct that Jumbo frames will help a bit with SMB 3.0 (35 MB/s/session max) for bulk tranfers but wow. A great deal of pain for so little gained when 1500 MTU on SMB 3.1+, NFS or AFS screams along at wire speed.
This is Synology’s weakness. We confirmed it with a DS3617 having run into the exact same problems you are now.
This having been said, Let’s figure out the file scanning and what else is ailing it.
When you get the logs of scanning that first section, Please attach.
Thank you.
I eventually understand after I used synology for a few years; no matter how hard I invested the network infrastructure…
I did have similar setting as yours.
BTW, you mentioned NFS and my bottleneck is windows. Will my experience greatly improve if I use file station and NFS not the windows mapping?
Thx.
I now attach the logs.
I found one thing for you to address.
In your DNS resolver, add plex.direct as an allowed private domain exception.
This will keep it from kicking out DNS rebinding errors.
Local devices will see the server as “Nearby” quicker / readily.
Mar 24, 2019 15:07:16.803 [0x7ffabab7d700] ERROR - Error issuing curl_easy_perform(handle): 7
Mar 24, 2019 15:07:16.804 [0x7ffabab7d700] WARN - HTTP error requesting GET https://101-190-49-211.79a2021296054186be24e8c5b28e3fd6.plex.direct:22693 (0, No error) (Failed to connect to 101-190-49-211.79a2021296054186be24e8c5b28e3fd6.plex.direct port 22693: Connection refused)
Mar 24, 2019 15:07:16.812 [0x7ffabae6b700] ERROR - Error issuing curl_easy_perform(handle): 35
Mar 24, 2019 15:07:16.812 [0x7ffabae6b700] WARN - HTTP error requesting GET https://192-168-1-179.79a2021296054186be24e8c5b28e3fd6.plex.direct:32400 (0, No error) (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 192-168-1-179.79a2021296054186be24e8c5b28e3fd6.plex.direct:32400 )
Mar 24, 2019 15:07:16.812 [0x7ffb5a840700] ERROR - Error issuing curl_easy_perform(handle): 35
Mar 24, 2019 15:07:16.812 [0x7ffb5a840700] WARN - HTTP error requesting GET https://172-17-0-1.79a2021296054186be24e8c5b28e3fd6.plex.direct:32400 (0, No error) (OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 172-17-0-1.79a2021296054186be24e8c5b28e3fd6.plex.direct:32400 )
Also, Please remember to give this new test instance your Cert info (PKCS12)
I didn’t understand this, in particular DNS resolver and Cert info. Could you please expand a bit more of your instructions? Thx.
Do you have a proxy in use?
If not, you need to go to the router and add the Private Domain exception for plex.direct
OR disable DNS rebinding protection (this is NOT advised… it’s dangerous to be without it)
CURLE_COULDNT_CONNECT (7)
Failed to connect() to host or proxy.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others
Until Plex can start making connections to Plex.tv and the metadata. It will scan but it will not retrieve any data.
I don’t use proxy but I use ubiquiti usg router.
I did some research online. Some says to add set service dns forwarding options rebind-domain-ok=/plex.direct/
I am struggling to find the place to add. Not sure whether you may tell me…
I’m sorry but I use pfSense.
Your best source of an answer there is either their forums or support manuals
