PhD05

Yeah i do have object cache functioning – but i did test the process of deactivating and removing a different plugin and it just worked.

I also installed the wp-cli tools and it was reporting ‘error deactivating plugin’, then the next line says plugin deactivated.. (even though it didnt show that online).

But, then after about an hour – it was marked as deactivated.. so maybe something in the cache was hanging on to it.. but just seemed odd since other plugins were able to be removed no problems.

In any case – this is now removed

I am also getting this notice when DEBUG is enabled in wp-config.php

as frustrating as this issue is – i have moved VPS’s and my site is running on a new server – and its working now.. i think it may have been related to SNI (i have multiple ssl sites running off that vps with difference certificates)

I really dont know 100% – but its working on the new server and i can connect it successfully.

this is the jetpack info from the debug page..
everything in site health, and jetpack debug page reports 100% clean and ok checks.

### jetpack ###

site_id: false
ssl_cert: No
time_diff: false
version_option: 9.1:1606090993
old_version: 9.1:1606090993
public: Private
master_user: No master user set.
current_user: #1 adminuser
tokens_set: None
blog_token: Not set.
user_token: Not set.
version: 9.1
jp_plugin_dir: /path/to/wordpress/wp-content/plugins/jetpack/
plan: free
protect_header: false
full_sync: {"started":"Thu, 01 Jan 1970 00:00:00 +0000","finished":"Thu, 01 Jan 1970 00:00:00 +0000","progress":[],"config":[]}
sync_size: undefined
sync_lag: 0 seconds
full_sync_size: undefined
full_sync_lag: 0 seconds
idc_urls: {"home":"https:\/\/www.dizzidecalz.com.au","siteurl":"https:\/\/www.dizzidecalz.com.au","WP_HOME":"","WP_SITEURL":""}
idc_error_option: false
idc_optin: true
cxn_tests: All Pass.

The url is https://www.dizzidecalz.com.au

I had also submitted info via that form previously about 4 days ago – but had no reply just yet from there as I assumed because I’m using the free plan there is no support apart from here – but without being able to install and test it I can’t commit to a plan if it’s not going to work

• This reply was modified 4 years, 4 months ago by PhD05.
• This reply was modified 4 years, 4 months ago by PhD05.

further information:
site health is 100% clear, jetpack debug reports a-ok

the only error we see is the curl 52 error, and then on the jetpack debug page it says cannot validate security token

all the curl tests (demo.hello etc) i have seen online all give me the correct output and xmlrpc seems to be functioning as expected.

a fresh install of wordpress and jetpack (alone) – still gives me this error (curl 52)