latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

About: Armand Minnie

Sorry, I've not written a description yet. I'll get to it soon!


Topics I'm Subscribed To

Viewing topic 1 (of 1 total)
Topic Count Last Reply
Auto upgrade of Pro fails

By:  armandminnie in: Community Forum

voices: 4
replies: 18

3 years, 10 months ago  Armand Minnie

Viewing topic 1 (of 1 total)

My Latest Replies (From Various Topics)

Viewing 9 replies - 1 through 9 (of 9 total)
Author Replies
Author Replies
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.

Posted: Thursday Feb 21st, 2013 at 9:17 am #42718

IP is 50.22.11.31 – again, thanks for your help and patience

Posted: Tuesday Feb 19th, 2013 at 11:50 am #42489

Here is Site5.com’s reply:
It appears that the server swain is blocked by s2member.com:

root@swain [~]# telnet s2member.com 80
Trying 199.168.174.42…
^C
root@swain [~]# host s2member.com
s2member.com has address 199.168.174.42
root@swain [~]# csf -g 199.168.174.42

Chain num pkts bytes target prot opt in out source destination
No matches found for 199.168.174.42 in iptables

If I connect from another server, it works just fine:

[cselzer@core ~]$ telnet 199.168.174.42 80
Trying 199.168.174.42…
Connected to 199.168.174.42 (199.168.174.42).
Escape character is ‘^]’.

I recommend that you contact s2member to see if they might have placed a block?

Posted: Tuesday Feb 19th, 2013 at 9:23 am #42478

Thank you. I will contact them.

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: 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 6:43 pm #42361

info is on the way via private contact

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: 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??

Viewing 9 replies - 1 through 9 (of 9 total)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.