CommonDominator

I am sorry to post on someone else post. My ticket was opened on march 29th at 10:59 under "Download issues" on this forum. However since this morning, I was able to download 3 files of 200+ Mb. Changed nothing. I checking bigger files now. As a comment to help Daltoneb who seems affected by a slow line like my terrible rural line. This problem only occurs on a premium account. I did several traces and they had always time-out after entry "reliance-mrs.cdn77.com [84.17.32.178]" regardless of the ISP used.

I open my own "ticket" on march 29th with 2 full traces. No answer yet...

Same problem here. I didn't try a huge file as most download failed after 60Mb. Tried almost all Nexus servers across the globe, 3 different ISP and an android device. Download failure in MO2 or manual mode. Only on my Premium account. I was able to download failed files without problem using a non premium test account ...

EDIT This a PREMIUM issue. Same config and same file download perfectly with a non premium test account. aAlso pause/resume corrupt the file. Downloading small files ok but failed on 100Mb+ files. MO2 give error "connection closed (2)" and retry or in manual using Edge hard stop with error "Couldn't download - Network error". Using my Premium account and CDN, Chicago, Amsterdam or Miami servers. No other concurrent network activity. Country: Canada ISP: Bell (slow land line), BELL (mobile phone on LTE) and Fido (mobile phone on LTE) Download tests (Bell) CDN: 420 kb/s (03-1.3 Mb/s BELL LTE) Chicago: 430 kb/s Singapore: 430 kb/s Amsterdam: 420 kb/s Small file: 34 Mb, ok https://cf-files.nexusmods.com/cdn/1704/34523/CleverCharff's%20Fort%20Dawnguard%202K-34523-1-1-1586463370.7z?md5=iEgwX4Pq-nkDaYhA-D9O_Q&expires=1617040595&user_id=35368020&rip=70.30.156.176 Large file: 104mb, failed after 50-70 mb on Chicago, Amsterdam, Singapore https://cf-files.nexusmods.com/cdn/1704/34523/CleverCharff's%20Fort%20Dawnguard%204K-34523-1-1-1586463232.7z?md5=hLhEIpE1rcEUMK5tFolLQg&expires=1617040700&user_id=35368020&rip=70.30.156.176 TRACE WITH BELL LAND ---------------------------------- C:\WINDOWS\system32>tracert files.nexus-cdn.com Tracing route to files.nexus-cdn.com [185.246.209.245] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1] 2 7 ms 7 ms 7 ms 10.11.23.233 3 * * * Request timed out. 4 * * * Request timed out. 5 13 ms 13 ms 13 ms tcore4-montreal01_39.net.bell.ca [64.230.36.86] 6 12 ms 12 ms 12 ms dis3-montreal01_0-6-0.net.bell.ca [64.230.94.131] 7 26 ms 29 ms 22 ms tcore4-montreal01_1-10-0-1.net.bell.ca [64.230.94.130] 8 27 ms 20 ms 22 ms 64.230.78.138 9 19 ms 19 ms 19 ms bx9-newyork83_1-0-0.net.bell.ca [64.230.79.81] 10 22 ms 21 ms 21 ms reliance-mrs.cdn77.com [84.17.32.178] 11 * * * Request timed out. 12 32 ms 32 ms 32 ms unassigned.cdn77.com [185.229.188.85] 13 34 ms * 34 ms unn-185-246-209-245.datapacket.com [185.246.209.245] Trace complete. C:\WINDOWS\system32> C:\WINDOWS\system32>ping 185.246.209.245 Pinging 185.246.209.245 with 32 bytes of data: Request timed out. Reply from 185.246.209.245: bytes=32 time=35ms TTL=53 Reply from 185.246.209.245: bytes=32 time=34ms TTL=53 Reply from 185.246.209.245: bytes=32 time=34ms TTL=53 Ping statistics for 185.246.209.245: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 34ms, Maximum = 35ms, Average = 34ms TRACE USING BELL MOBILE IN LTE -------------------------------------------------- C:\WINDOWS\system32>tracert files.nexus-cdn.com Tracing route to files.nexus-cdn.com [185.246.209.245] over a maximum of 30 hops: 1 3 ms 2 ms 3 ms 192.168.42.129 2 52 ms 28 ms 26 ms 10.4.172.129 3 66 ms 37 ms 35 ms 10.55.174.10 4 54 ms 31 ms 36 ms 10.55.167.5 5 98 ms 54 ms 37 ms 10.55.65.217 6 39 ms 28 ms 44 ms 10.4.244.102 7 55 ms 29 ms 28 ms 10.4.244.113 8 40 ms 35 ms 38 ms 10.55.65.220 9 58 ms 69 ms 43 ms 10.55.65.44 10 44 ms 63 ms 42 ms tcore4-montreal02_bundle-ether11.net.bell.ca [64.230.91.138] 11 69 ms 75 ms 73 ms tcore3-newyorkaa_hundredgige0-8-0-0.net.bell.ca [64.230.79.142] 12 74 ms 68 ms 75 ms bx9-newyork83_1-0-0.net.bell.ca [64.230.79.81] 13 43 ms 36 ms 46 ms reliance-mrs.cdn77.com [84.17.32.178] 14 * * * Request timed out. 15 108 ms 75 ms 76 ms unassigned.cdn77.com [185.229.188.81] 16 90 ms * * unn-185-246-209-245.datapacket.com [185.246.209.245] 17 * 88 ms * unn-185-246-209-245.datapacket.com [185.246.209.245] 18 55 ms * 82 ms unn-185-246-209-245.datapacket.com [185.246.209.245] Trace complete. C:\WINDOWS\system32>ping 185.246.209.245 Pinging 185.246.209.245 with 32 bytes of data: Reply from 185.246.209.245: bytes=32 time=98ms TTL=47 Request timed out. Reply from 185.246.209.245: bytes=32 time=81ms TTL=47 Reply from 185.246.209.245: bytes=32 time=63ms TTL=47 Ping statistics for 185.246.209.245: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 63ms, Maximum = 98ms, Average = 80ms C:\WINDOWS\system32> EDIT ---- Failed also using an android tablet but works using a non premium test account ! Very very annoying. I would cancel my premium subscription if it was not paid for 6 months only in a effort to help this excellent site as i can't use the bandwidth on my slow rural line !

Same problem. Downloading small file ok but failed on 100Mb+ files. Stop and restart with MO2 error "connection closed (2)" or in manual using Edge stop with error "Couldn't download - Network error". Using my Premium account and CDN, Chicago or Miami servers. https://cf-files.nexusmods.com/cdn/1704/46629/Nitro%20BBLS%20Girls-46629-1-1-1615235113.7z?md5=cEdKwdIF4ALMP6ldtxhA9w&expires=1615767626&user_id=35368020&rip=70.30.159.7 Microsoft Windows [Version 10.0.19041.867]© 2020 Microsoft Corporation. All rights reserved. Tracing route to files.nexus-cdn.com [185.246.209.245]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1] 2 10 ms 5 ms 9 ms 10.11.23.233 3 * * * Request timed out. 4 * * * Request timed out. 5 14 ms 12 ms 12 ms tcore4-montreal02_45.net.bell.ca [64.230.36.82] 6 10 ms 9 ms 10 ms dis53-montreal02_hundredgige0-10-0-0.net.bell.ca [64.230.91.21] 7 23 ms 20 ms 20 ms tcore4-montreal02_1-14-0-0.net.bell.ca [64.230.91.20] 8 21 ms 20 ms 20 ms tcore3-newyorkaa_hundredgige0-8-0-0.net.bell.ca [64.230.79.142] 9 16 ms 17 ms 16 ms bx9-newyork83_1-0-0.net.bell.ca [64.230.79.81] 10 18 ms 18 ms 17 ms reliance-mrs.cdn77.com [84.17.32.178] 11 29 ms 29 ms 30 ms vl1106.chi-cs1-core-1.cdn77.com [138.199.0.6] 12 30 ms 30 ms 29 ms unassigned.cdn77.com [185.229.188.81] 13 31 ms * 31 ms unn-185-246-209-245.datapacket.com [185.246.209.245] Trace complete.

Yes. I have over 437 ESPFE in my load order ! Mostly patches, armor mods (all converted) and followers (most converted). Some are just placeholder for quest entries but I push my luck by converting also scripted mods when they don't rely heavily on GetFormFromFile functions and check the result. I am tracking now a potential persistence problem (faction/dialog/?) with my converted SleepForMeNow mod. I am interested if other modders have similar problems.

ESPFE (ESP with ESL flag) are quite useful to lower your load count and simplify patches management. However, there are several issues reported with them including the famous CELL bug (temporary references lost when ESPFE cells are modified). I recently encountered a new issue with persistence, registered keys are not preserved between game load. The workaround is simple but I suspect other persistence issues could exists. Does anyone know other persistence issues or strange behavior associated with ESPFE ?