If you are in this situation, it might be for several reasons.
You are behind a company proxy or firewall. Make sure that the ports 80 and 43554 are open.
You are using an old version of Node.js or PM2. Make sure you are using at least Node.js v0.11.x or higher (node v0.12.x or iojs v.2.x is recommended). Make sure you are using the latest version of PM2 https://github.com/Unitech/PM2/releases.
You have concurrent PM2 sending data to the same bucket with an identical server name.
Make sure you have only one PM2 instance launched
ps -aux | grep PM2
Refresh your connection to Keymetrics.
pm2 interact stop then
pm2 interact start. Also don’t forget to refresh the dashboard itself, it might help sometimes.
If the buttons are disabled, make sure that the
Local changes and
Local commit indicators are green.
If you get a warning
Not authorized when trying to perform such actions, it means you have not the admin privileges in this bucket.
If none of the above happens, but the precedure just hangs, make sure you have a recent version of Node.js as well as the latest version of PM2.
Also, your repository should not ask for a password input (it means you must clone it via ssh), try typing
git remote update manually in the folder and see if it asks for a password or not.