Here you can find information on problems and issues raised on Grav forum and in the Slack Chat room that occur frequently enough that we thought we would save time and list the problem and the relevant solution in one easy to find location.
Problem: The GPM cannot be reached, and you get this error in the Admin panel
First, make sure PHP has cURL and OpenSSL installed. You can check this in the Admin panel, in Configuration -> Info. You should see a "OpenSSL" section with
OpenSSL support: enabled. Same for cURL, a section with
cURL support: enabled.
Then, check your permissions.
If after all the above you are still getting issues connecting with GPM, we have noticed that on some servers (mostly local machines running Windows), there are issues verifying the SSL certificate of getgrav.org, even though it is A Rating.
To work around this problem, we have added a new system config
system.gpm.verify_peer that is enabled by default. Set it to false and try again.
If at this point it's still not working, get in touch, or report back if you were pointed here via chat/forum.
Also, check the CLI command is working, by opening a SSH connection to the server and running
bin/gpm index and check if it's just inside Admin that you get this error, or in the command line too.
Problem: When accessing the Admin-plugin's interface, the page will not scroll
Solution: There are several reported causes of this, but the most common solutions are the following.
/admin, for example:
Inside Admin sometimes a "Fetch Failed" red popup might appear. If it happens once in a while, do not worry as it might simply mean a connection issue.
But if it shows up every time, an issue some users run into is
mod_security blocking Grav's network requests.
This can be solved by finding and disabling the rules that are raised, which depending on the configuration of mod_security, might be different from case to case.
If you are running your own server, a guide on how to do this can be found in http://www.inmotionhosting.com/support/website/modsecurity/find-and-disable-specific-modsecurity-rules, otherwise just contact your hosting provider and illustrate the problem.
Related issue: admin#951