This is probably due to Gabble using the user's configured network proxy. Perhaps the reporter could verify that their proxy settings are correct, and try disabling their proxy to see if that helps.
This is probably due to Gabble using the user's configured network proxy. Perhaps the reporter could verify that their proxy settings are correct, and try disabling their proxy to see if that helps.