I have done a review of the server logs tonight looking for any trace of this…  We have quite a bit of activity on the server at this time (also checked 1, 2 and 3 hours different in case timezone delta) but no signs of 503 errors from our server… 

I also verified that sock-doc.com IP is not blocked… 

I also verified that there have been zero accesses to the server from that IP…  I still suspect that the request is never making it to the server and being blocked by a firewall or security app…  Ours do not show any sign of your IP or domain being blocked….

believe you checked with your host and verified our domain is not black listed, right?  sorry, didnt read back…

and actually, the definition of 503 really does mean the request doesnt make it to the server…  so wouldnt expect to see in our logs…  but if truly a 503, it should be server wide and at this time, we are chugging along…

I also checked some other logs to see if the server generated 503 errors (though they are not recorded in access logs)… and there is a handful, but infinitesimal small number…  and unfortunately, no timestamps…

so continuing to research, but a bit puzzled…  many, many api requests honored just fine today (and every day)…

Thanks Mr. Papa – what more could I do on my end? My other site on the same server works fine. But creating a new sock-doc site doesn’t allow me to update, just like my current site. Really odd.

same server?  same IP or different?  any chance php 7 in use?

We’re using PHP Version 5.4.45.

Same server. Same IP. sock-doc.com and drgangemi.com are the two sites. 

I setup a test site with a fresh WordPress install and nothing installed except the Forum plugin, and I got the same error. That domain is test.sock-doc.com.

Sorry @mr-papa didn’t make it to the forums last night. But he did send me a log dump that I have been looking through. Bearing in mind, as I have said before, this is far form my area of expertise – I do have one other question.

In the portion of the log I am looking at there are 9 calls from ‘sock-doc.com’. Of these, 8 were successfully resolved with a status of 200 being returned. One, however, did result in a 503 (a plugin download request I think it probably is). But this – in all fairness along with some of the other success ones – came from the url ‘ss.sock-doc.com’.

Can you explain the difference between the two request url’s?

The ‘ss’ version was during our site rebuild which as completed early July. It was soon after this that we were unable to complete the upgrade of Simple Press Forum. My designer, who has been helping me figure this out (and posting this) says that they just copied and pasted everything from one to the other so nothing should have happened on our end.

Curious…. the ‘ss.’ prefixed url appears repeatedly in these logs taken a day or so ago, Not that I think that this is the cause of your problem but if they have no relevance it would be nice to eradicate the calls.

unless the xml was from non ss and the download was from ss… that is, switch in middle… didnt seet hat in logs, but the ss was much more predominant…

didnt believe it was related to php version but about out of ideas so it was straw grasp…

so when yours failed with 503, there was dozens of success in the immediate area…  just not sure why the 503…

I was testing the updates from the “ss” site while making changes. I didn’t want to break the live site.

I just tried updating (within 5 minutes of this post) the Forum plugin and all the plugins. I get the same response every single time.

The update process is starting. This process may take a while on some hosts, so please be patient.

Updating Plugin Admin Bar (1/5)

Updating Plugin Editor TinyMCE Rich Text (2/5)

Updating Plugin File Uploader with Plupload (3/5)

Updating Plugin Subscriptions (4/5)

Updating Plugin Watches (5/5)

All updates have been completed.

We are not doubting your failures! We have had our own hosting company looking into it as well as spending much time trawling logs and settings. The simple truth is that we do handle hundreds of these requests every day and these failures are very rare.

There are still diagnostics and research going on but I am not feeling too confident that we are going to find any trouble our end. And that, of course is partly because of what I just said… the rarity of such failures.

Is there any update on this? Thank you.

afraid not… have found nothing wrong on the server… and especially with the release of 5.6.3 and a couple dozen plugin updates, we have gotten many, many updates…

we continue to look at it…  and we even made a couple of real minor tweaks to reduce load on the api site to make sure its not getting overloaded… but would have to have 5.6.3 (as would other users) to make any difference…

So is there anything else my developer can check on our end here? It’s odd that it happened with a site rebuild but they see nothing wrong or changed so I don’t know what to do next. I can update manually to 5.6.3 I guess if I need to go that route.

Thanks.

I honestly can not suggest anything to try your end although I will leave it to Mr Papa to comment if he can think of anything. But I believe from what he has said this end we do not have anything else we can check as far as we know. Downloads, updates and access to our control files seem to be going very smoothly I am afraid.

We continue to look at it… I perused the logs this weekend for more hints and data with the release but going very smoothly.

Of course, not denying your issue…it’s just a one off…and frankly we are developers not server admits.  So if your developers have any thoughts we are happy to hear them.

Long thread, but did you provide your server IP (not your ISP IP) so we can verify it’s not blocked?