It sounds like one of the site URL options in the database, or perhaps the wp-config.php, is incorrect.
Have you looked through to confirm they are all correct?
Yep.
Though it was a fully working multi-site before the 3.9 update. so these issues occured before I even attempted any changes to the URL’s in phpmyadmin.
I was mythed that I needed to change from domain.com to http://www.domain.com in the 1st place. but this hasn’t solved the issues.
I also am unable to install plugins from wp.org on my single site, neither could I do an update to wp3.9 on the single site either. It tells me I have an SSL issue, i don’t use SSL or https on any of those site.
Downloading install package from https://downloads.wordpress.org/plugin/gallery-plugin.4.1.9.zip…
Download failed. SSL peer certificate or SSH remote key was not OK
Do you have any of the urls defined in wp config?
No, at the time my multisite had just domain.com in the Multisite defines. i changed them all in the db to use www. & in wp-config. but issues were still the same. redirect loops.
I’m currently reinstalling my multisite from scratch (it was just a sandbox testing site, so no loss to business or anything).
I wasn’t using any other defines for site_url etc.
Well I’m at about half and half – meaning half of my wordpress installations are down, and the other half, which just happens to be 3.8.3 are fine …
I was two days late loading a WP for a client, and finally got it loaded, much to her great delight, last night — Now today … THIS.
I’m working on the sites that still work to ‘not’ auto-update like they have been …
I’ve begun to download what work I can save, and I’m intending to redeploy using the 3.8.3 build until you guys up here at WP can get it together.
I can define all day long .. I can roam around in the DB all day long .. but until someone at WP decides to more thoroughly review the code, I’m not going to allow another update to happen.
I’ll lay odds that WP is missing a “;” or something dumb and simple like that that …
I’ve goofed up more WP installs and loads than I care to count over the years, and this is the first time WP, in my experience, has done the same.
Two Words
“Fix It”
Well fresh install of 3.9, created multisite.
Still getting redirects issue., can’t download plugins/themes from wp.org still.
notice on the dashboard widgets (news widget)
http://goo.gl/UK4xzi
says: RSS Error: WP HTTP Error: Too many redirects.
Ok, it loos like this is more the wp server than 3.9.
I think wp.org must now be forcing https on everything & their SSL Cert is incorrect.
root@server4069 [~]# wget https://wordpress.org
–2014-04-20 19:39:38– https://wordpress.org/
Resolving wordpress.org… 66.155.40.249, 66.155.40.250, ::ffff:67.215.65.132
Connecting to wordpress.org|66.155.40.249|:443… connected.
ERROR: certificate common name *.wordpress.org' doesn't match requested host namewordpress.org’.
To connect to wordpress.org insecurely, use `–no-check-certificate’.
Unable to establish SSL connection.
something that wp.org has done since or around the time of 3.9 release has caused this. I believe this is what is preventing me using the plugins page to automatically download plugins from wp.org & is also responsibe for the RSS https error in the dashboard widget.
However, that doesn’t explain why I get a https peer error when upgrading the local network as that uses Curl.
I think wp.org must now be forcing https on everything & their SSL Cert is incorrect.
No it’s not… I mean, yes, the https is correct, but the cert isn’t broken. What version of wget and curl and openssl are you using?
Works: GNU Wget 1.12 built on linux-gnu.
FAILS: GNU Wget 1.11.4
So bascially the issue there is your wget is old and not meshing with the version of openSSL that WP has.
openSSL is 0.98b i think, wget is 1.12 Centos 6
Why did this just suddenly start happening the last couple days? Has wp.org updated? I know the heartbleed bug caused a panic, I don’t know if wp.org was using an affected version and upgraded recently, but this just started happening around the time 3.9 was released, which is why initially the assumption was with 3.9, however we installed a 3.8.3 site and it did the same.
I don’t know for sure if wp.org was upgraded, but I’d suspect the answer is yes.
Here was our Curl test connection results from the server console terminal.
array(9) {
[“version_number”]=>
int(464896)
[“age”]=>
int(3)
[“features”]=>
int(34333)
[“ssl_version_number”]=>
int(0)
[“version”]=>
string(6) “7.24.0”
[“host”]=>
string(24) “x86_64-unknown-linux-gnu”
[“ssl_version”]=>
string(14) “OpenSSL/0.9.8b”
[“libz_version”]=>
string(5) “1.2.3”
[“protocols”]=>
array(16) {
[0]=>
string(4) “dict”
[1]=>
string(4) “file”
[2]=>
string(3) “ftp”
[3]=>
string(4) “ftps”
[4]=>
string(6) “gopher”
[5]=>
string(4) “http”
[6]=>
string(5) “https”
[7]=>
string(4) “imap”
[8]=>
string(5) “imaps”
[9]=>
string(4) “pop3”
[10]=>
string(5) “pop3s”
[11]=>
string(4) “rtsp”
[12]=>
string(4) “smtp”
[13]=>
string(5) “smtps”
[14]=>
string(6) “telnet”
[15]=>
string(4) “tftp”
}
}
Connection to: https://www.paypal.com/
string(53) “GET / HTTP/1.1
Host: http://www.paypal.com
Accept: */*
“
Connection to: https://httpapi.com/
bool(false)
Connection to: https://plus.google.com
string(54) “GET / HTTP/1.1
Host: plus.google.com
Accept: */*
“
Connection to: https://wordpress.org
bool(false)
Connection to: https://www.google.co.uk
string(55) “GET / HTTP/1.1
Host: http://www.google.co.uk
Accept: */*
“
Connection to: http://wordpress.org
string(52) “GET / HTTP/1.1
Host: wordpress.org
Accept: */*
“
Marking this as resolved.
It turns out this was some weird issue with the openDNS on the server, we changed it to use google DNS instead and it began to work.
sorry for the confusion. lot’s of coincidences all at the same, made it hard to pinpoint.
