Hi there everyone!
Thanks for your patience in this matter 
@stan_he I鈥檓 really sorry for you feeling frustrated, please note that Jitpack is a 3rd party tool and thus outside of our hands, the issue is not really ours to fix (you can actually see on Jitpack鈥檚 github repo a number of recent discussions about this, such as this one: Origin Connection Time-out 路 Issue #3973 路 jitpack/jitpack.io 路 GitHub)
We have already contacted them and are waiting for their response, so we can only try and find workarounds in the meantime.
The reason your build works locally is because your computer already has the gradle cache dependencies downloaded, but since our Virtual Machines are created and destroyed in every single build, they do not amass the collection of dependencies over the years the way a physical computer does. If you were to delete your local gradle cache, you would experience the same issues locally as you do on Bitrise 
BUT! It seems that currently a workaround could be to add a www in the repo URL in the Gradle file:
maven { url "https://www.jitpack.io" }
So please try and see if this works 