Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The encoded file <b>/usr/local/cwpsrv/htdocs/admin/index.php</b> has expired #2

Closed
snRNA opened this issue Apr 4, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@snRNA
Copy link

snRNA commented Apr 4, 2023

Hi there, i followed your instructions. but when i finally finished the steps . I try to connect to cwp. https://xxx.xx.xx.xx:2031 , I got server 500 in response.
I checked the log from cwp, PHP message: PHP Fatal error:
The encoded file /usr/local/cwpsrv/htdocs/admin/index.php has expired. in Unknown on line 0"
How did you try to avoid this and make cwp could be used ?

@monsieurDuke
Copy link
Member

Hi there, i followed your instructions. but when i finally finished the steps . I try to connect to cwp. https://xxx.xx.xx.xx:2031 , I got server 500 in response. I checked the log from cwp, PHP message: PHP Fatal error: The encoded file /usr/local/cwpsrv/htdocs/admin/index.php has expired. in Unknown on line 0" How did you try to avoid this and make cwp could be used ?

I haven't encounter that specific error actually. could you show me the snippet of the logs? and also is the error occurred from the part of the downgrade CWP section?

here is my index.php's md5 hash if you wanted to compare it

fe1bc27fd70f157bdd0f758bc3e99c5a  index.php

i'm also going to check on my end if the setup.txt is still capable on the current version (was tested on 0.9.8.1150)

@monsieurDuke monsieurDuke reopened this Apr 5, 2023
@monsieurDuke monsieurDuke pinned this issue Apr 9, 2023
@monsieurDuke
Copy link
Member

Ow I actually just found the workaround. It seems like each CWP's previous version got their own End-of-Life timeline. Which in this case for version 0.9.8.1146, is probably start from the first April of 2023

So what you wanted to do is actually revert the system clock to at least around March 2023. So for the testing purposes, I use timedatectl set-time to January 2023 in .bashrc file, so it wouldn't be a problem on further sessions

$ cat /root/.bashrc
...
timedatectl set-time 2023-01-01
service cwp-phpfpm restart & wait
service cwpsrv restart & wait
service cwpsrv-phpfpm restart & wait
$ source /root/.bashrc
Redirecting to /bin/systemctl restart cwp-phpfpm.service
[1]+  Done                    service cwp-phpfpm restart
Redirecting to /bin/systemctl restart cwpsrv.service
[1]+  Done                    service cwpsrv restart
Redirecting to /bin/systemctl restart cwpsrv-phpfpm.service
[1]+  Done                    service cwpsrv-phpfpm restart

That should do the trick for me. Thanks for the heads up, I really appreciate it 👌

@monsieurDuke monsieurDuke added the bug Something isn't working label Apr 9, 2023
@monsieurDuke monsieurDuke changed the title the index.php has been expired The encoded file <b>/usr/local/cwpsrv/htdocs/admin/index.php</b> has expired Apr 9, 2023
@monsieurDuke
Copy link
Member

No actually dont put it in the .bashrc lol, I kept failing on the remote access since it keeps restarting. Just use the command manually

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants