Orchestrator Installation Failed

i was trying to install orchestrator with the second method (script method) and i had this issue:

One of the configured repositories failed (rapid7_insightconnect_stable),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=rapid7_insightconnect_stable ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable rapid7_insightconnect_stable
        subscription-manager repos --disable=rapid7_insightconnect_stable

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice

        yum-config-manager --save --setopt=rapid7_insightconnect_stable.skip_if_unavailable=true

failure: repodata/repomd.xml from rapid7_insightconnect_stable: [Errno 256] No more mirrors to try.
https://packagecloud.io/rapid7/insightconnect_stable/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 302 - Found
→ Contact Rapid7 support and include the error message and installation log.
→ The full install log can be found at /tmp/r7install.log.

Has someone faced the same problem?
Thanks for any feedback.