[Solved] PHP with problem in openvms.eu.org

[ballagyr]

Hello, this my domain is having problems with PHP, I noticed that the "info.php" file does not return any information, I found that the problem is not the version used, PHP just stopped working. I checked the other domains and the problem only affects "openvms.eu.org".

I would like you to take a look, thank you!

[MoneyBroz]

This support request is being escalated to our root admins.

[Krydos]

Try setting your NS records to ns1.heliohost.org and ns2.heliohost.org

[ballagyr]

15 hours ago, Krydos said:

Try setting your NS records to ns1.heliohost.org and ns2.heliohost.org

This site has always been on CloudFlare and it worked, I checked if there was an IP change and found that this is not the case.

PS: I'm going to disable CloudFlare temporarily to see if the problem isn't with them.

Edited Friday at 09:30 PM by ballagyr

[Krydos]

5 hours ago, ballagyr said:

PS: I'm going to disable CloudFlare temporarily to see if the problem isn't with them.

Yeah, that's exactly why I suggested it. Refusing to disable Cloudflare is like refusing to try a different power strip when your computer isn't working. Start by ruling out the easiest stuff to test.

I renamed your .htaccess to .htaccess-disabled to disable it and PHP on your site works fine now.

https://openvms.eu.org/phpinfo.php

You need to fix whatever errors you have in your .htaccess file.

[ballagyr]

I ran all the tests, changed the NS and everything seemed normal, the problem was not with CloudFlare, since even after changing to HelioHost's NS, I still had problems accessing "Wackowiki" that was installed there, strange that only php info had started working again, before it returned a blank screen. I don't know why "Wackowiki" had stopped working or the cause, but I didn't want to waste time with that and removed it. I have a backup of the content, so I decided to do everything again from scratch.

[Krydos]

8 minutes ago, ballagyr said:

I ran all the tests, changed the NS and everything seemed normal, the problem was not with CloudFlare, since even after changing to HelioHost's NS, I still had problems

Yeah, that's why I determined that Cloudflare wasn't the problem.

8 minutes ago, ballagyr said:

I don't know why "Wackowiki" had stopped working or the cause

I already told you the issue was in the .htaccess. When I renamed the .htacess file to disable it php started working again.

[ballagyr]

1 hour ago, Krydos said:

Yeah, that's why I determined that Cloudflare wasn't the problem.

I already told you the issue was in the .htaccess. When I renamed the .htacess file to disable it php started working again.

By renaming the htaccess you made PHP work again, but I must clarify that before all this, PHP worked and Wackowiki worked, everything worked, just as I had left it. But something happened in the meantime that I was away that made everything stop working. Furthermore, I had only changed the NS from CloudFlare to HelioHost, because you suggested I do so and I took this opportunity to test CloudFlare, which is normal.

The problem has been resolved, but we have not yet discovered the cause, which would be more important to know how to proceed in the future.

[ballagyr]

One curious thing about that htaccess that I forgot to mention is that it was part of Wackowiki, so it certainly isn't the cause of the problem. Because I checked later when you told me you renamed it to disable it, so to be sure, I renamed it back and php info continued to work. This just raises more questions, because I don't know what caused the problem or how it was actually fixed. It just happened...

[Krydos]

10 minutes ago, ballagyr said:

This just raises more questions, because I don't know what caused the problem or how it was actually fixed. It just happened...

I renamed .htaccess to enable and disable it several times, and each time I enabled it PHP started showing blank white pages for everything, and when I disabled the .htaccess file PHP files would start working again. I didn't bother to look inside the .htaccess file because I try to focus on providing support for our servers, not support for code issues. I came to the conclusion that it was a code issue, not a server issue, so I marked this topic as solved. Not sure why the issue started in the first place. We definitely didn't mess with your files so either

1. You edited it.
2. The software itself caused the issue due to some bug.
3. Some third party got access.

[ballagyr]

The htaccess provided by Wackwiki was kept original. Therefore, there is no way I could have caused the problem myself, it simply occurred while I was away. Because all I did was install Wackowiki, configure it and close it in maintenance mode, in the following days I had logged in several times with maintenance mode activated. All I can say about what happened is that I had a problem, which was somehow resolved, but the cause is still unknown, this is unfortunately still a fact.

Anyway, I appreciate your attention, few people bother to do this.

[ballagyr]

You can close the topic, there is nothing more to be said. Thanks!