Still blocked on this. Without resolution it's not looking like AF remote repos will be of much use to our organization. We've also tried a test instance of AF 4.x and it shows the same issue.
I've tried testing various levels of the https://packages.elastic.co/ directory hierarchy with AF's remote repo "test" button. The only one that AF accepts as legit is the top level URL itself. However, this is rejected by yum itself: and, when that AF remote repo is queried by yum, it too fails: For comparison, here's a very specific repo baseurl that works for yum but is rejected by AF's test button with a 404 error: I went ahead and added the remote repo with the same URL as above anyway and tried it: *Given this new info that shows a specific 403 error rather than the 404 error exposed by the test button, a fresh google shows what may be the issue*: https://www.jfrog.com/jira/browse/RTFACT-7966?focusedCommentId=37388&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-37388 Unsure what next steps are. I will try contacting the elastic.co folks. Thanks for any tips here, Brett -- View this message in context: http://forums.jfrog.org/Problems-connecting-to-remote-YUM-package-repositories-tp7581046p7581065.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
