Home › Forums › Community Forum › Auto upgrade of Pro fails
This topic contains 18 replies, has 4 voices. Last updated by Armand Minnie 3 years, 10 months ago.
Topic Author | Topic |
---|---|
Posted: Friday Feb 8th, 2013 at 9:25 am #41203 | |
|
|
The auto upgrade fails with the message “Upgrade failed. Connection failed ( please try again ).” Retrying does no good. |
List Of Topic Replies
Author | Replies |
---|---|
Author | Replies |
Posted: Friday Feb 8th, 2013 at 2:30 pm #41218 | |
|
|
download the zip, unzip it on your hard disk and FTP it to your server. HTH |
|
Posted: Friday Feb 8th, 2013 at 5:51 pm #41225 | |
|
|
That was easy. Thanks. |
|
Posted: Wednesday Feb 13th, 2013 at 10:04 pm #41634 | |
|
|
OK, I just upgraded to V130213 and the same problem happened again with the same solution. Seems like something that does not get updated automatically needs to be updated and using the latest zip file doesn’t do it. Of course I can keep doing this but I’d like to repair the problem instead. Any suggestions?? |
|
Posted: Friday Feb 15th, 2013 at 3:27 am #41797 | |
![]() |
|
Thanks for reporting this important issue.What are the permissions set to on your /wp-content/ directory please? So far I’ve been unable to reproduce this, but if we duplicate your permission structure, perhaps we can get to the bottom of this. Also, who is your hosting provider please? Thanks! |
|
Posted: Friday Feb 15th, 2013 at 8:53 am #41871 | |
|
|
The permissions on those directories are all 0755. My provider is site5.com. I have another site on a different server with them also using s2member and it updates fine. I just tried to update to v130214 and it failed. I have not yet updated the s2member-pro files manually if there is anything you want to look at. I can leave it like that for a while. |
|
Posted: Monday Feb 18th, 2013 at 2:40 pm #42312 | |
![]() |
|
Thanks for your reply :-)Thank you. If you would like to submit a Dashboard login for me, I will run diagnostics for you. I just tried to reproduce this locally but I was unable to. If we can run diagnostics, perhaps we can tell you more. Please see: s2Member® » Private Contact Form |
|
Posted: Monday Feb 18th, 2013 at 6:43 pm #42361 | |
|
|
info is on the way via private contact |
|
Posted: Monday Feb 18th, 2013 at 9:10 pm #42387 | |
![]() |
|
Details received. Thank you!So this site is live, correct? Also, I see this site is already running the latest release of s2Member. Did you update this manually I presume? Thanks! I just want to get a handle on things before we attempt any tests for you. |
|
Posted: Monday Feb 18th, 2013 at 10:16 pm #42396 | |
|
|
yes, site is live but not used very much – a small club. Yes, had to update manually because login went away without pro. |
|
Posted: Monday Feb 18th, 2013 at 10:58 pm #42404 | |
|
|
got a message that server would be rebooted tonight some time – just a heads up. |
|
Posted: Tuesday Feb 19th, 2013 at 2:33 am #42444 | |
![]() |
|
Thanks for your reply :-)We’re going to run some tests now. Please stand by for a second notification that we have completed the tests. |
|
Posted: Tuesday Feb 19th, 2013 at 3:20 am #42447 | |
![]() |
|
Thanks for your patience.Testing completed. Your installation remains up-to-date. We discovered a connection issue on your server. It appears that your server has a firewall or a possible misconfiguration that is preventing outbound connections to our update server at: http://www.s2member.com. All attempts to make an HTTP connection from your server to http://www.s2member.com fail with timeouts.
You will need to contact your hosting company about this please. |
|
Posted: Tuesday Feb 19th, 2013 at 9:23 am #42478 | |
|
|
Thank you. I will contact them. |
|
Posted: Tuesday Feb 19th, 2013 at 11:50 am #42489 | |
|
|
Here is Site5.com’s reply: root@swain [~]# telnet s2member.com 80 Chain num pkts bytes target prot opt in out source destination If I connect from another server, it works just fine: [cselzer@core ~]$ telnet 199.168.174.42 80 I recommend that you contact s2member to see if they might have placed a block? |
|
Posted: Thursday Feb 21st, 2013 at 2:18 am #42657 | |
![]() |
|
Thanks for the follow-up :-)What is your server’s IP address please? I will verify this with FireHost® (our hosting company). |
|
Posted: Thursday Feb 21st, 2013 at 9:17 am #42718 | |
|
|
IP is 50.22.11.31 – again, thanks for your help and patience |
|
Posted: Thursday Feb 21st, 2013 at 10:42 am #42737 | |
![]() |
|
Thanks for the follow-up :-)We have a request in for this to be investigated. I’ll follow-up as soon as I hear back :-) |
|
Posted: Saturday Feb 23rd, 2013 at 6:23 pm #43072 | |
|
|
I ran your Server Scan program and it reported a checksum error “Warning[WARNING] Plugin Directory Checksum (s2member-pro)”. I uploaded a completely new s2member-pro folder and now the checksum error is gone but I don’t know if it will make any difference to the automatic update. Maybe some kind of security issue? I do use Filezilla. |
This topic is closed to new replies. Topics with no replies for 2 weeks are closed automatically.