Bug report (and possible solution): Download issues via Native Access

aetdeep

G'day NI team,

Just wanted to pass on something that may be affecting other users. I have spent a few hours and multiple reinstalls and restarts trying to get Native Access working to download my software.

I decided to check in my network (UniFi) to see if there was anything being flagged and, it turns out, your User-Agent is being flagged by Ubiquiti as "Potential Risk". I think the aria2 library you are using is also used by some trojans - I have attached the warnings below.

The products downloaded instantly once I whitelisted my Mac's IP.

I'm not familiar with the aria2 library but I have experience with web scrapers and similar - perhaps overriding the default User-Agent string to remove any reference to aria2 would be beneficial and save people a lot of headache, especially those who don't have access to their network like I do.

tl;dr follows:

Bug: Native Access 2 being flagged as potential risk due to User-Agent and traffic blocked in UniFi networks.

Possible solution: Change User-Agent in the software.

Please find attached the threat report below:

reffahcs

This has come up a few times before and I don't think NI is going to re-do their content delivery platform. Making an exception for Aria 2 is probably the easiest route, other people have suggested a VPN.

https://community.native-instruments.com/discussion/16352/my-native-access-download-failed-problem-solved-ni-should-probably-look-into-this

aetdeep

https://community.native-instruments.com/discussion/comment/125846#Comment_125846

Unless they are applying strict UA rules server-side, it has nothing to do with their CDN, just the app. Could be wrong but, assuming the "new" UA string was "nativeaccess2" for example, they just need to override the base one using the "-U"/"--user-agent" option for their aria2 constructor.

On the CDN side, it's one of the most basic access control things to allow/disallow a specific UA (e.g. Googlebot).

I would assume NI wouldn't want to be flagged as a "potential risk" and it's really a pretty simple fix.

Matt_NI

@aetdeep Welcome to our community and thank you so much for taking the time to sharing all of this with us. Your post was shared with our team and they are investigating your suggestion. I'll share more information about a fix when I hear more 🙌