Websites returning blank page with no error or anything

Customer Support Customer Only Discussion
1

I have a client on web8 that has many of their domains returning a blank page. No errors, just a blank page:

www.sleepyblogger.com
www.jamestippins.com
www.celebritypicturesandnews.com

I have checked from different browsers and computers and get the same. Can someone else confirm if they get the same result when going to one of these. I have submitted a ticket, but it hasn’t show up yet… not sure if it is caught in spam again.

Help Jodo

2

They are blank, I have made Tanmaya aware.

3

Quick update… my different firefox versions showed a blank page… in IE it shows:

The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.

4

Just wanted to add that I have the same problem on web8 as well.

ETA: I actually had this problem at around 5AM today (6 Feb). And I can still access my FTP.

5

All of these sites are Wordpress 2.1 sites… even mine is showing nothing.

However if I call phpinfo.php which is in my site it does load up. I thought maybe there was a php issue, but if phpinfo.php works then it can’t be just a php issue.

6

These are working now for me.

7

Now can someone tell me why they were not working so I can intelligently respond to the client. I know you didn’t work on it Stephen so hopefully Tanmaya can respond.

In the ticket I put in for this they simply said:

These domains are working fine with both IE and firefox. Can you check it again and let us know if you still getting problem with firefox.

I really need to know the resolution when they fix things.

Thanks

8

Ha! Same here… my sites that were down were also Wordpress 2.1 sites.

9

we’ll let you know once we know what caused this issue

10

In the ticket they said there was a configuration problem. Not sure what changed or what configuration problem since things were working all along until about an hour ago.

11

The problem happened with some newly compiled module. We have to disable them for now and will enable only once we are sure it is going to work fine altogether.