RE: Can't publish HTTP (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

Giomanach -> RE: Can't publish HTTP (12/19/2004 16:18:18)

Should take no longer than 48 hours to resolve internationally...



Kitka -> RE: Can't publish HTTP (12/19/2004 17:56:19)

Bill,

I know how frustrating it is waiting for it to resolve, we went through a tense situation recently where we moved our primary domain (the one with all our important email addresses) and for my colleague (on the same ISP as me but living 300kms away) , it was bouncing between the old and new IP for about 5 days. Sometimes he could get his email, sometimes a couple of hours later, he couldn't. Yet it resolved fully for me within 24 hours or less. Our ISP said that there must have been a caching problem somewhere upstream and all we could do is wait.

I just did a ping and here is the result - still pointing at the old IP:

C:\Documents and Settings\Kitka>ping agisolutions.com

Pinging agisolutions.com [168.144.31.234] with 32 bytes of data:

Reply from 168.144.31.234: bytes=32 time=250ms TTL=114
Reply from 168.144.31.234: bytes=32 time=235ms TTL=114
Reply from 168.144.31.234: bytes=32 time=250ms TTL=114
Reply from 168.144.31.234: bytes=32 time=250ms TTL=114

Ping statistics for 168.144.31.234:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 235ms, Maximum = 250ms, Average = 246ms

If you are in a hurry, editing your hosts file could be a good solution, so you can at least publish with FP. Are you confident about such things? It is only text.



bdannels -> RE: Can't publish HTTP (12/19/2004 19:33:12)

Kitka:

Thanks for the support.

I sure don't understand how it's listed on the old server and the new server, depending on where you look?

I emailed Tech Support about 3 hr. ago:

The files that I FTP uploaded there 2 days ago are corrupt

I emailed the Host and asked them if they needed to be deleted or what.

Have read conflicting info on exactly where to upload the site.

2 says agisolutions.com, 1 says they must be put in the dir public_html

I have emailed the question to the server, no response as of yet. :(


>If you are in a hurry, editing your hosts file could be a good solution,
so you can at least publish with FP.
>Are you confident about such things? It is only text.

That sounds good, but I haven't got a clue as to go about doing that.

I have a guy who said he could copy my files from my old server to my new server.

I think he is going to do that, not sure when. He dosen't use FrontPage, don't know if that
is a issue if he is just doing a copy?

Thanks again (They say it's all easy once you know how, still haven't got there yet.)

Bill



Kitka -> RE: Can't publish HTTP (12/19/2004 20:01:48)

Bill,

At this point, the following is what I would do:

On your computer:
1. Edit your hosts file to point at new IP
2. Reboot (essential!)


On your new server:

1. From within Control Panel, delete all files and directories in public_html, other than the original defaults.
2. Uninstall the FPSE, then reinstall.
3. Publish using FrontPage.
4. Cross fingers and toes [;)][:D]



Kitka -> RE: Can't publish HTTP (12/19/2004 20:17:45)

quote:

I sure don't understand how it's listed on the old server and the new server, depending on where you look?


Simple - the NS have been cached in some places, and can sometimes take days to renew.

quote:

That sounds good, but I haven't got a clue as to go about doing that.

It is quite easy when you know where to find it and the syntax to use. PM me if you'd like some help.

quote:

I have a guy who said he could copy my files from my old server to my new server.

I think he is going to do that, not sure when. He dosen't use FrontPage, don't know if that is a issue if he is just doing a copy?


To do that, he would have to be using FTP - which IS an issue as it will most likely corrupt the FPSE. Personally, I would not do it.



Kitka -> RE: Can't publish HTTP (12/19/2004 20:35:51)

quote:

Have read conflicting info on exactly where to upload the site.
2 says agisolutions.com, 1 says they must be put in the dir public_html


Both are correct. If you use FrontPage to publish to agisolutions.com, it will automatically place your files in public_html. It is only if you are using FTP, that knowing the exact destination directory is important.



bdannels -> RE: Can't publish HTTP (12/19/2004 21:24:07)

Kitka:

I just got this back from tech support:

Yes delete the files then upload again.
The public_html folder is the place you want to upload to.

Looks like you are right on target. :)

Will give it a shot.

>From within Control Panel, delete all files and directories in >public_html, other than the original defaults.

Hope I can tell the original files from my files.

Thanks again

Bill




bdannels -> RE: Can't publish HTTP (12/19/2004 23:08:53)

Kitka:

I deleted all the files that I thought I should, removed the FPSE then reinstalled them.
Then I did a FP Publish by way of HTTP, got a server not support ASP pages error, told it to continue.

Went to agisolutions.com, all my FrontPage Navigation buttons are missing. I then deleted everything and uploaded the files by way of FTP, same results. ( Iknow I should NOT do this but I had try something else)

When I have my home page open in the browser I select "Edit in FrontPage" it opens the home page in FrontPage edit mode, and all the buttons are there .

Going to bed now, at my wits end.

Thanks
Bill
Tried to use one of my ASP pages and got this:
Method Not Allowed
The requested method POST is not allowed for the URL /SampleRequest.asp.
--------------------------------------------------------------------------------
Apache/1.3.33 Server at www.agisolutions.com Port 80



Page: <<   < prev  1 [2]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.09375