Hello,
I am using Page Safe @joeworkman to password protect my husband’s popular drawing webinars. However, purchasers are having a very hard time opening the locked page. They type in the code and the lock turns green and unlocks, and then it goes back to being an unlocked lock.
It may be a PhP problem. I use Siteground hosting. I have manually set the PhP from 8.1.0 to 8.0.10 to 7.4.23 . A few weeks ago, 7.2.34 was working but now there’s a warning in Siteground that 7.2.34 is soon to be depracated.
If one version of PHP works with your host but another does not, that most likely your host probably doesn’t have the correct package is enabled. If you find the PHP error los in the server, they would probably have the information that we need.
Pagesafe is working OK for me on my Chillidog host using PHP v7.8 and v8.1.
I did have an issue just as you describe a few weeks ago when Chillidog was conducting some testing with PHP, however, this only lasted for a couple of hours and then it was all back to normal.
I would suggest that if Pagesafe was working with Siteground using v7.2 and it stops working with 7.4 and 8.1 then it is a host issue? Have you highlighted the issue with your host and can you demonstrate to them that it works in 7.2 but not a higher version?
PHP 8.1 hasn’t been officially released yet. They’re still testing it, it’s currently in the ”release candidate” stage (RC2 currently about a week ago). I wouldn’t be using it for a production site quite yet.
The most current official version is PHP 8.0.10, and the highest version 7 available is PHP 7.4.22.
You’ll need to contact the hosting company and find out if they have error logging enabled, if not how do you enable it, and find out the location of the error logs.
You can also try using Joe’s server info stack and try to figure out what is different when you use 7.2.23 and the later releases. That would be the hard way.
Something is different in the host’s PHP configurations between versions other than just the update of PHP.
2021-09-20 16:08:48 UTC [apache][core:info] [pid 21082] [client 95.87.27.146:42826] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/favicon.ico, referer: https://sabinhowardwebinars.com/
2021-09-20 15:43:42 UTC [apache][core:info] [pid 79494] [client 67.250.168.145:57576] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/favicon.ico, referer: https://www.sabinhowardwebinars.com/
2021-09-20 15:34:45 UTC [apache][core:info] [pid 68635] [client 94.197.196.24:50414] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/favicon.ico, referer: https://sabinhowardwebinars.com/
2021-09-20 15:30:36 UTC [apache][core:info] [pid 48057] [client 66.249.72.38:35506] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/ads.txt
2021-09-20 12:23:23 UTC [apache][core:info] [pid 76393] [client 34.214.125.14:34188] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/favicon.ico, referer: http://sabinhowardwebinars.com/favicon.ico
2021-09-20 11:49:47 UTC [apache][core:info] [pid 19156] [client 128.199.177.229:38182] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/favicon.ico, referer: Enter the passcode to login
2021-09-20 11:18:27 UTC [apache][core:info] [pid 74777] [client 54.236.1.13:34092] AH00128: File does not exist: /home/u331-uaapqxpazhr0/www/sabinhowardwebinars.com/public_html/Classes/StructureAnatomyHead/
Dear @joeworkman , I don’t know what to say to Siteground about the PhP, they told me that their managed PHP was changed from 7.3 to 7.4. I switched it manually to 8.0.1 and that page safe stack isn’t working. The password is accepted and the lock turns green and then it’s an unopened lock again. Please help!
I’m getting lots of unhappy emails from paying customers.
Can you please tell me another stack that might work? This one doesn’t. Thanks.
Traci, if you are the only person that Pagesafe isn’t working for - it’s fine for me right now on a number of sites - then I’d guess that it isn’t something that Joe will be able to fix. I’d still suggest it’s the host that is the issue.
Pagesafe version updates. If you are not running the latest version, check for updates in RW, update Pagesafe and then republish the page with Pagesafe (Right click and Republish page)
Sadly, those are the server “access” logs, not the “error” logs. However, I suspect that there are no errors being generated at all. Something similar happened with customers on Chillidog recently. @barchard was able to fix it pretty quickly. I am not sure what exactly the problem was though. From what I could remember it was some sort of server side caching problem.
Maybe he could chime in here and give you a clue as to what you could ask your host.
If you want to message me the URL to a page with a passcode, I can give it a look.
cPanel has added some additional features for spending up sites via a cache, yes, but SiteGround has dropped cPanel (most likely due to pricing) and opted to build their own hosting interface:
Unfortunately, my experience or guidance there would be irrelevant to resolving your Page Safe issue on SiteGround. I could, however, help you migrate to Chillidog
I got your login details. The behavior that I am seeing is exactly what Greg is describing. Page Safe is working but the browser is sending a cached version of the page instead.
When you go to a page with Page Safe, it checks to see if you have already logged in. If you have not, it provides the login page instead of the page contents. Your host is caching this login page in order to page things faster. Once you type in the password, PageSafe authenticates and refreshes the page. Once this happens, PageSafe verifies you have logged in again and should display the content. However, since the host has cached the login screen, it’s never even getting the chance to fetch the content, the login page is getting served up from the cache.
