Still having the problem. Also, I can’t get the address off the back-end either. It’s too short.

This requires me to come here and download the plugin every time.

can you send me the IP of your ISP account via PM?  I can make sure the firewall/security stuff on our server hasnt blocked you…

not sure what you mean by admin url is too short??

Same Here.. Only on docsplace.org the other site updates fine. CloudFlare anycast dns 141.101.126.182

over to @mr-papa to check the server although I can’t think of any reason there should be these sort of blocks.

If you’re still using HostGator for your vps host, I bet there are a bunch of blocked IP’s.

I’m not sure since we have a virtual private server but it revolves to this IP for the moment.

162.253.150.91

This is the address which is not complete.
https://simple-press.com/download-manager.php?id=724…
It would simplify things if I could copy the failed address every time to download as FidoSysop suggested with the plugins earlier. 🙂

The new process to get the plugin is slightly cumbersome.

where did you get the url from?  for core, the id will change every time, but the url is correct, just has the … on it for some reason… truncate after the id (ie 724)…

plugins are a bit different…

That IP traces to Santa Rosa, CA…  I have removed any blocks (uknown if there was) from that IP… so might be worth a another try…

Same old deal here.. Was able to download and manually update.

Strange that WordPress reports all updates have been completed.

Fiddler, who are you using for a host?

I’m using Arvixe

Thanks for white-listing my IP Mr Papa, but it didn’t work now either.

It loads fine using the URL. Thanks for pointing out that the … should be left out. That saves me some time downloading the plugin. 🙂

not sure why it would directly, but not from within the wp updater…  but something to think about…  and curious what the ‘rest of the url’ might be…  possible something on your site is adding something to the url?

Exactly. 🙂 I’m always able to download the plugin to my computer first.

Maybe I’m not thinking straight but when I take the actual address of the upgraded file I’m loading it on my computer, not the servers. At this point it looks like your server denies the download from Arvixe.

I’ll contact Arvixe to see if they can figure out why. The funny thing is that all other plugin updates work.

Usually I just ftp upload the zipped file into the proper directory, then use cPanel file manager to uncompress the archive. But yesterday I tried the SP plugin uploader. Got some kind of error message but forgot to screenshot it.

There is one other user having this issue and I am going to link his topic here and visa versa so perhaps we can use one thread for this, This would the  better one. The other topic is at: https://simple-press.com/support-forum/sp5-general-topics/simple-press-update-to-5-5-10-build-13317-fails/page-2/#p155510

Perhaps I can clarify a few things here although please bear in mind that personally I am out of my comfort zone when getting into server behaviour…. but here goes.

1. Nobody is suggesting that this is a problem with your website or another plugin.
2. it is NOT an uncommon problem although it is most usually seen when a server is under demand pressure. This is not the case or it would have cleared.
3. Of all of our users you three guys seem to be the only ones seeing this which still begs the question is there anything your setups have in common.
4. There is a world of difference between using the WordPress updater to make a call to our server for an update as opposed to simply entering the update URL into a browser address bar. The first is passed via your web server as a part of your website processing. The latter does not go anywhere near your website and almost certainly does not go through your web server either. So because it works one way has no bearing at all on it not working the other.
5. I still suggest that your host support is contacted simply to ask if they know of any reason why the url is failing. And it needs the whole url. It could be that they have put something in place, for example, that does not like the query var being passed and reject it. (see note 6)
6. And just because the WordPress updater displays what appears to be a Server Unavailable (503) error condition, without being able to replicate it it is hard to know what return data WP is actually getting – so we can not say with any certainty it really IS a 503 code. Although it probably is but this needs to be borne in mind.
7. And leading on form there, the third person with this issue has looked at their server error logs and found no trace of an actual 503 event.

There has to be a common denominator shared by your three. We simply need to find it…

Copy that YS.

I don’t see this as a big issue at all since updating is still relatively easy. Since this error is only happening to a small percentage of users I can’t see a reason for you to invest much time into solving the problem. I’ll let you know when updates on the back-end are successful, also, I did contact my host and will let you know if they have anything constructive to say. 🙂