• Resolved Piia

    (@piia)


    Hi there

    I just installed and activate gzip-plugin. When I go to Tools / GZIP Compression, I get this:

    Oops! Something went wrong. It could be that you are on a local development environment, or that we couldn’t contact checkgzipcompression.com

    When I go checkgzipcompression.com and put my URL, it checks and then I get “GZIP is not enabled”

    Dubug info:

    isApache: 1 (Apache)
    enabled:
    enabled-htaccess:
    plugin: 1.1.7

    my url is https://www.tarhuri.fi and I use Human theme

    I read your anser to christianbouce (4 days ago): “Could you try without checking the extra box for using compression for images etc.?”

    Can you please tell me where I find this “extra box”?

    Thank you!
    Piia

Viewing 15 replies - 1 through 15 (of 26 total)
  • Plugin Contributor ericmulder

    (@ericmulder)

    Hi Piia,

    It seems that the plugin can’t connect to checkgzipcompression, which seems to be strange. I’ll did some checks with your domain and it seems to be working.
    Could you try checking again? And if it doesn’t work, I’ll push an plugin update to do some extra checks.

    Eric

    Thread Starter Piia

    (@piia)

    Dear Eric

    Thanks for your quick responce. Unfortunally nothing helped. I unloaded the plugin, upload the plugin again and I get the same “Oops…” and same dubug-info.

    Looking forward to get to test an updated plugin, cause my site is soooo slow…

    Regards,
    Piia

    Plugin Contributor ericmulder

    (@ericmulder)

    Just a quick note as I can have a look into this only next week, check out my other plugin (WP Takeoff). Because for making the site faster you will need caching and image optimizing, good luck ??

    Eric

    Thread Starter Piia

    (@piia)

    Hi

    I’ll check that out on the weekend!

    Best,
    Piia

    I am getting the same “oops” message. Have you fixed this Piia? Tx

    Plugin Contributor ericmulder

    (@ericmulder)

    Could you try and update to version 1.1.8? And send me the debug data? That should give me some more info about what goes wrong…

    Thread Starter Piia

    (@piia)

    Hi Eric
    I updated to version 1.1.8 and now the debug data says:

    isApache: 1 (Apache)
    enabled:
    enabled-htaccess:
    plugin: 1.1.8
    error: WP_Error Object
    (
    [errors] => Array
    (
    [http_request_failed] => Array
    (
    [0] => cURL error 35: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
    )

    )

    [error_data] => Array
    (
    )

    )

    Plugin Contributor ericmulder

    (@ericmulder)

    Thanks, this helps a lot! It turns out https://checkgzipcompression.com/ is having some connection problems. I’ll push an update in the coming days to fix this. Keep you posted!

    Plugin Contributor ericmulder

    (@ericmulder)

    Hi Piia,

    I’ve made a new version which should solve this problem. Could you remove the plugin from wordpress, and upload the following test version?

    https://www.dropbox.com/s/py9oi4sj23qu1py/gzipcompression.zip?dl=0

    Eric

    There is no plugin in that zip folder

    Plugin Contributor ericmulder

    (@ericmulder)

    Hmm, could you try this link?

    https://www.dropbox.com/s/r4eybdngys4toak/check-gzip-compression.zip?dl=1

    Just upload the zip file to wordpress via plugins > add new

    Got the same error: Oops! Something went wrong ?? It could be that you are on a local development environment, or that we couldn’t contact checkgzipcompression.com

    Plugin Contributor ericmulder

    (@ericmulder)

    Thanks for the help, and the patience. Could you send me the debug info?

    Hi, your colleague BD Brown has sent me to this thread.
    I’m having the same problem on a few sites – live sites.
    The dropbox link to the updated zip file doesn’t work – maybe you still have the problem.

    See debug info:

    isApache: 1 (Apache/2.2.15 (CentOS))
    enabled:
    enabled-htaccess:
    plugin: 1.1.9
    error:

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Oops! Something went wrong…’ is closed to new replies.