Forum Moderators: phranque

Message Too Old, No Replies

Can anybody help me solve a mystery

blocked website

         

pick

11:56 pm on Mar 13, 2005 (gmt 0)

10+ Year Member



I own a website recently developed by a freelance programer, however, I cannot pull up my site from my computer even though I have confirmed that the site is up with my host (and friends) and I can access every other site on the web? I pinged the site and it is reaching my host no problem but I keep getting page cannot be found. How is this possible?

Is it possible my PHP programmer to blocked my IP until final payment is received (which is in the mail as of yesterday)? Can that be done?

HughMungus

12:45 am on Mar 14, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Sure it can be done. How do you know the index.php (or whatever) file is in the directory?

pick

1:03 am on Mar 14, 2005 (gmt 0)

10+ Year Member



Thanks, I don't know. As a non-programer, all I know is that I cannot access the site for more than 20 or so min at a time before it becomes no longer accessable to me. I shut everything down, reboot my router and modem and sometimes I am able to access it again for 20 min or so before I lose it again.

jorj

6:28 am on Mar 14, 2005 (gmt 0)

10+ Year Member



I've laugh when I read your messages. Interesting ideea. As a rule, the php scripts cannot be truly protected other than by using an encoder (as Zend). Still, I do not encourage anyone un-protecting someone else's scripts because the developer may have let holes in his script only he knows about.

As a funny story: I was looking through a payment script for making an ideea about their protection and ..surprise: there was implemented a secondary hidden password giving admin rights, same password for all their scripts. A search on the net was enough to find few of their customers and I logged into their accounts in no time. Once again : this was a payment script (like paypal) - pretty scary , huh?

PimenovVV

10:33 am on Mar 14, 2005 (gmt 0)

10+ Year Member



My guess is that your site have something like SessionTimeout=20 (by default) and when this time spends - your session lost some "essential" server-side-variables (like Session(something)), which your "free-lancer" used so that whithout them it doesn't work...
Give him this my hint - and he will correct it (adding SessionTimeout=60 or more).
:0)