Features Failed to activate. TypeError: Failed to fetch
-
After updating to latest version, I can’t activate or deactivate any features. It always keeps saying “failed to activate. TypeError: Failed to fetch”.
-
Could you try the following:
- Open the dashboard page.
- Open your browser console
- Click on the Network tab
- Refresh the page.
- If you see any lines in red inside the browser console, click on them. A new panel should appear on the right.
- Click on the “Response” tab in that new panel.
- Copy the message displayed there.
- Paste it here.
- If no red lines appeared in the browser console, click on the “Console” tab of the browser console.
- Copy any errors displayed there, and paste them here.
When i clicked on response tab, It said unable to show response data. Anyway, Here are the errors appeared in consol:
JJQMIGRATE: Migrate is installed, version 1.4.1 /wp-admin/admin.php?page=jetpack#/settings:1 Mixed Content: The page at 'https://www.mydomain.com/wp-admin/admin.php?page=jetpack#/settings' was loaded over HTTPS, but requested an insecure resource 'https://www.mydomain.com/wp-json/jetpack/v4/connection/url/'. This request has been blocked; the content must be served over HTTPS. /wp-admin/admin.php?page=jetpack#/settings:1 Fetch API cannot load https://www.mydomain.com/wp-json/jetpack/v4/connection/url. Redirect failed. /wp-admin/admin.php?page=jetpack#/settings:1 Mixed Content: The page at 'https://www.mydomain.com/wp-admin/admin.php?page=jetpack#/settings' was loaded over HTTPS, but requested an insecure resource 'https://www.mydomain.com/wp-json/jetpack/v4/module/notes/active/'. This request has been blocked; the content must be served over HTTPS. /wp-admin/admin.php?page=jetpack#/settings:1 Fetch API cannot load https://www.mydomain.com/wp-json/jetpack/v4/module/notes/active. Redirect failed.
Fetch API cannot load https://www.mydomain.com/wp-json/jetpack/v4/connection/url. Redirect failed.
This seems to indicate issues with your site’s HTTPS setup. Could you go to Settings > General in your dashboard, and check that you use HTTPS for both your site address and your WordPress address?
Hey,
I found the problem. My htpps setup is 100% OK. I’m using wp rocket caching plugin installed and it has 3 mu plugin for 3 different reasons. One redirect http to https. Anyway, When i just deactivated wp rocket, I found jetpack is working fine. When i activate it, Jetpack works OK but doesn’t allow me to enable / disable any features by showing: Failed to fetch error.- This reply was modified 8 years, 1 month ago by Hasibul Kabir.
That’s interesting. We haven’t had any other other reports from WP Rocket users so far.
Could you make screenshots of your WP Rocket settings, and post them here, so I can try to reproduce the problem?
You can use a service like https://snag.gy/ to share your screenshots here.
Thanks!
Hi,
Here are the configuration screenshots
https://snag.gy/IXV3G1.jpg
https://snag.gy/QktK18.jpg
https://snag.gy/wUz1ri.jpg
https://snag.gy/7q0Pye.jpgand here are the MU plugins: https://drive.google.com/drive/folders/0Bw44Pb1XK4b3VDlWVXZBb3duaDg?usp=sharing
These HTTP -> HTTPS redirections are interesting. What happens if you remove them for a bit? Does that help?
No. I found the problematic MU plugin. It is wprocket-slash which fixes trailing slash at the end of the link. I disabled this plugin and jetpack is working fine. But, Jetpack earlier versions work fine with this MU plugin.
Jetpack earlier versions work fine with this MU plugin.
Jetpack previously didn’t use the WordPress REST API to get information about module status. I suspect the trailing slash plugin interferes with the REST API queries, but only on specific server configurations and permalink structures.
I tried adding the trailing slash rules on one of my test sites, but it didn’t cause any issues.
Could you let me know what your permalink structure is?
Thanks!
Yes. Here it is: /%postname%/
Thank you. That’s fairly standard, and I can’t reproduce the issue with this permalink structure either.
Could you tell me more about your server setup, and the different plugins you use on your site right now?
Thanks!
Perhaps, I’m using another plugin called “JSON API” to work with my android app. Do you think it can cause conflicts?
Here are my plugin list:
Ad Inserter
Akismet
Clef
Comments – wpDiscuzContact Form 7
Featured Images in RSS w/ Size and Position
Jetpack by WordPress.com
JSON APIMyThemeShop Theme/Plugin Updater
NextScripts: SNAP Pro Upgrade Helper
NextScripts: Social Networks Auto-Poster
Permalink Redirect
Social Warfare
TinyMCE Advanced
User Role Editor
VaultPress
WP Review Pro
WP Rocket
WP Smush Pro
WP Subscribe Pro
WPMU DEV Dashboard
Yoast SEO PremiumI’m using Linode cloud VPS. It has following configurations:
PHP 7
Nginx & Apache 2.4I’m also installed memcached here.
2 of those plugins seem like they could be involved in the issue:
- JSON API
- Permalink Redirect
Permalink Redirect, in particular, seems like it could conflict with some of the mu-plugins you installed with WP Rocket. I also believe some of the Permalink Redirect features are now available in Yoast SEO. You might be able to get rid of that old plugin now that you use Yoast SEO.
I tried installing both plugins on my test site, and I didn’t get any issues though. Could you copy the contents of the
.htaccess
file, and paste it here?Thanks!
I use serverpilot to manage my server. I can reproduce it in my another website with wp mu plugins.
Here are my .htaccess:
# Redirect http to https RewriteEngine On RewriteCond %{HTTPS} !on RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] # BEGIN WP Rocket v2.8.14 # Force trailing slash RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_URI} !(.*)/$ RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1/ [L,R=301] # Redirect http to https RewriteEngine On RewriteCond %{HTTPS} !on RewriteCond %{SERVER_PORT} !^443$ RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] # END https redirect # Redirect non-www to www RewriteEngine On RewriteCond %{HTTP_HOST} ^45\.33\.28\.237$ [NC,OR] RewriteCond %{HTTP_HOST} ^xtremerain\.com [NC] RewriteCond %{HTTP_HOST} !^www\. [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.xtremerain.com/$1 [L,R=301] # Use UTF-8 encoding for anything served text/plain or text/html AddDefaultCharset UTF-8 # Force UTF-8 for a number of file formats <IfModule mod_mime.c> AddCharset UTF-8 .atom .css .js .json .rss .vtt .xml </IfModule> # FileETag None is not enough for every server. <IfModule mod_headers.c> Header unset ETag </IfModule> # Since we’re sending far-future expires, we don’t need ETags for static content. # developer.yahoo.com/performance/rules.html#etags FileETag None # Send CORS headers if browsers request them; enabled by default for images. <IfModule mod_setenvif.c> <IfModule mod_headers.c> # mod_headers, y u no match by Content-Type?! <FilesMatch "\.(cur|gif|png|jpe?g|svgz?|ico|webp)$"> SetEnvIf Origin ":" IS_CORS Header set Access-Control-Allow-Origin "*" env=IS_CORS </FilesMatch> </IfModule> </IfModule> # Allow access to web fonts from all domains. <FilesMatch "\.(eot|otf|tt[cf]|woff2?)$"> <IfModule mod_headers.c> Header set Access-Control-Allow-Origin "*" </IfModule> </FilesMatch> <IfModule mod_alias.c> <FilesMatch "\.(html|htm|rtf|rtx|txt|xsd|xsl|xml)$"> <IfModule mod_headers.c> Header set X-Powered-By "WP Rocket/2.8.14" Header unset Pragma Header append Cache-Control "public" Header unset Last-Modified </IfModule> </FilesMatch> <FilesMatch "\.(css|htc|js|asf|asx|wax|wmv|wmx|avi|bmp|class|divx|doc|docx|eot|exe|gif|gz|gzip|ico|jpg|jpeg|jpe|json|mdb|mid|midi|mov|qt|mp3|m4a|mp4|m4v|mpeg|mpg|mpe|mpp|otf|odb|odc|odf|odg|odp|ods|odt|ogg|pdf|png|pot|pps|ppt|pptx|ra|ram|svg|svgz|swf|tar|tif|tiff|ttf|ttc|wav|wma|wri|xla|xls|xlsx|xlt|xlw|zip)$"> <IfModule mod_headers.c> Header unset Pragma Header append Cache-Control "public" </IfModule> </FilesMatch> </IfModule> # Expires headers (for better cache control) <IfModule mod_expires.c> ExpiresActive on # Perhaps better to whitelist expires rules? Perhaps. ExpiresDefault "access plus 1 month" # cache.appcache needs re-requests in FF 3.6 (thanks Remy ~Introducing HTML5) ExpiresByType text/cache-manifest "access plus 0 seconds" # Your document html ExpiresByType text/html "access plus 0 seconds" # Data ExpiresByType text/xml "access plus 0 seconds" ExpiresByType application/xml "access plus 0 seconds" ExpiresByType application/json "access plus 0 seconds" # Feed ExpiresByType application/rss+xml "access plus 1 hour" ExpiresByType application/atom+xml "access plus 1 hour" # Favicon (cannot be renamed) ExpiresByType image/x-icon "access plus 1 week" # Media: images, video, audio ExpiresByType image/gif "access plus 1 month" ExpiresByType image/png "access plus 1 month" ExpiresByType image/jpeg "access plus 1 month" ExpiresByType video/ogg "access plus 1 month" ExpiresByType audio/ogg "access plus 1 month" ExpiresByType video/mp4 "access plus 1 month" ExpiresByType video/webm "access plus 1 month" # HTC files (css3pie) ExpiresByType text/x-component "access plus 1 month" # Webfonts ExpiresByType application/x-font-ttf "access plus 1 month" ExpiresByType font/opentype "access plus 1 month" ExpiresByType application/x-font-woff "access plus 1 month" ExpiresByType application/x-font-woff2 "access plus 1 month" ExpiresByType image/svg+xml "access plus 1 month" ExpiresByType application/vnd.ms-fontobject "access plus 1 month" # CSS and JavaScript ExpiresByType text/css "access plus 1 year" ExpiresByType application/javascript "access plus 1 year" </IfModule> # Gzip compression <IfModule mod_deflate.c> # Active compression SetOutputFilter DEFLATE # Force deflate for mangled headers <IfModule mod_setenvif.c> <IfModule mod_headers.c> SetEnvIfNoCase ^(Accept-EncodXng|X-cept-Encoding|X{15}|~{15}|-{15})$ ^((gzip|deflate)\s*,?\s*)+|[X~-]{4,13}$ HAVE_Accept-Encoding RequestHeader append Accept-Encoding "gzip,deflate" env=HAVE_Accept-Encoding # Don’t compress images and other uncompressible content SetEnvIfNoCase Request_URI \ \.(?:gif|jpe?g|png|rar|zip|exe|flv|mov|wma|mp3|avi|swf|mp?g|mp4|webm|webp)$ no-gzip dont-vary </IfModule> </IfModule> # Compress all output labeled with one of the following MIME-types <IfModule mod_filter.c> AddOutputFilterByType DEFLATE application/atom+xml \ application/javascript \ application/json \ application/rss+xml \ application/vnd.ms-fontobject \ application/x-font-ttf \ application/xhtml+xml \ application/xml \ font/opentype \ image/svg+xml \ image/x-icon \ text/css \ text/html \ text/plain \ text/x-component \ text/xml </IfModule> <IfModule mod_headers.c> Header append Vary: Accept-Encoding </IfModule> </IfModule> # END WP Rocket # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
- The topic ‘Features Failed to activate. TypeError: Failed to fetch’ is closed to new replies.