Can't publish HTTP (Full Version)

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



Message

bdannels -> Can't publish HTTP (12/17/2004 21:06:56)

Hello:

I am in the process of moving my site to a new server and cannot publish my site using FP2002 HTTP. My original site is still up and running, have not moved my domain till I get the new one working. The NEW server has 2002 server ext. installed, they have also reinstalled them. The HTP error message is: Unable to open http://65.254.59.194/~bdannels/ (1) no ext (2) out of service (3) proxy.......... etc.

I did get the site up using a 3rd party FTP software BUT there are problems with the navagation structure that I need to fix and upload it with FrontPage.

When I try to open the web in FrontPage I put the URL in http://65.254.59.194/~bdannels/ and get : The folder http://65.254.59.194/~bdannels/ isn't accessible?

If I put the same link in Windows Explorer it opens the site.

Any help with this would be greately appreciated.
I am pulling out what little hair I have left :)

Tks.
Bill



BobbyDouglas -> RE: Can't publish HTTP (12/17/2004 21:13:49)

Have your host try publishing via FP. If they can publish, then you know you are doing something wrong.



Larry M. -> RE: Can't publish HTTP (12/17/2004 21:28:37)

quote:

When I try to open the web in FrontPage I put the URL in http://65.254.59.194/~bdannels/ and get : The folder http://65.254.59.194/~bdannels/ isn't accessible?


bdannels,

This isn't a URL, it's an IP. Do Publish web site files to the web site (http://www.yoursite.com) - don't FTP which will corrupt the extensions and overlook critical aspects of the navigation structure (as you've already determined).



bdannels -> RE: Can't publish HTTP (12/17/2004 22:03:01)


Well: :)


If http://65.254.59.194/~bdannels/ isn't a URL and I haven't moved my domain name (agisolutions.com) yet because I want to get this site up and working first. How do I upload my new site with FrontPage?

Tks.
Bill



BobbyDouglas -> RE: Can't publish HTTP (12/17/2004 22:14:25)

You should be able to use an IP address to publish via FrontPage. There might be issues with this down the road when you try to access the website via your domain- I haven't seen it before, but the way the FP Extensions are configured, they might enter the serverIP instead of your domain name inside of the configuration files.

If you follow what I said in the 2nd post, you might figure out what the problem is.



bdannels -> RE: Can't publish HTTP (12/17/2004 23:13:43)

Hello again:

I tried to FTP the files to ftp://65.254.59.194 and got a error message saying: The following pages in your web site contain link or nav bars that use new formating options(It then gave a list or all my pages that have Nav bars) and basically said if I wanted the nav bars yo work, publish to a server that has the latest server ext. on it. My new server has 2002 ext.

Tks.
Bill



BobbyDouglas -> RE: Can't publish HTTP (12/17/2004 23:29:15)

Yeah, that is what happens when you FTP.



Kitka -> RE: Can't publish HTTP (12/18/2004 0:57:52)

quote:

This isn't a URL, it's an IP


Larry, I have often used FrontPage to publish to an IP address before I change the name servers for the domain name, so the site is 100% ready to view as soon as it starts propagating. The process usually works very well.

Bill, using ftp for a site that has FPSE installed, can break (corrupt) the extensions. You might need to reinstall the extensions (if you have access to the Control Panel) or ask your ISP/host to do it for you.

When the extensions have been reinstalled try again to publish with FrontPage and let us know the exact error message you get and the process you used.



Larry M. -> RE: Can't publish HTTP (12/18/2004 7:27:22)

quote:

Larry, I have often used FrontPage to publish to an IP address before I change the name servers for the domain name, so the site is 100% ready to view as soon as it starts propagating. The process usually works very well


Kitka,

I need to learn something here. My hands were slapped by one host (CETLink) years ago for doing this same thing - vaguely remember something to do with two sets of files being maintained on their UNIX server - one for the IP, the other for HTTP. Didn't understand why, just haven't done it since.

So, if I understand you correctly instead of designing a new site as a subweb (to the designer's site) publishing files to the new web client's host IP is better because (1) they are "hidden", (2) they will propogate when the DNS change is made and (3) server space and bandwidth on the designer's site remains in tact. Right?

I gather you agree that once the site is active the IP shouldn't be used and the integrity of FP Extensions are probably an issue in bdannels case.



bdannels -> RE: Can't publish HTTP (12/18/2004 10:43:08)

OK, heres where I am at now....

My Host uses Cpannel, I have 2 choices, reinstall or uninstall
I selected reinstall see message received below.

------------------------------------
Attempting to install FrontPage extensions...

Starting install, port: 80.

Created: 16 Dec 2004 02:45:58 -0000
Version: 5.0.2.2634
Server extensions already installed on port 80.
Reverting to upgrade.

Starting upgrade, port: 80.

Created: 16 Dec 2004 02:45:58 -0000
Version: 5.0.2.2634
Chowning Content in service /.
Port 80: Upgrade completed.
Upgraded Version: 5.0.2.2634.

Starting chown, port: 80, web: "/".

DocumentRoot: "/home/bdannels/public_html"
Setting Password
Frontpage passthough auth enabled!


FrontPage extensions are currently: installed
----------------------------------------

Then I Loaded FP 2002, clicked on publish web, In the publish destination box I put http://65.254.59.194/~bdannels/ , clicked on OK and got this error message:

Unable to open http://65.254.59.194/~bdannels/
Server error: The web server "http://65.254.59.194" does not appear to have the FrontPage server ext. installed. Possible causes: (1) The webserver may not have the Server Extensions installed.
(2) Server may be temp out of service
(3) If you are connecting through a proxy server, settings may be incorrect
(4)A error might have occurred on the server.
---------------------------------------------
This is the same error message I got on day one, when they activated my account with the Extensions installed.
---------------------------------------------

Thanks again
Bill



Larry M. -> RE: Can't publish HTTP (12/18/2004 12:21:49)

quote:

This is the same error message I got on day one, when they activated my account with the Extensions installed


Bill,

http://www.dnswiz.com/fptype.asp shows:

WWW Site: http://65.254.59.194/~bdannels/
Port: 80
Server Software: This Web Server Does Not Disclose Identity
FrontPage Extensions: NO

It's possible extensions have only been installed to the IP root directory, not the subweb ~bdannels/ although this goes counter to my experience in this area. As to ~bdannels/, I've never seen a tilde used in a path statement before and wonder if this could contribute to your problem as well. Perhaps renaming would help? Worth a try.

Sorry, out of ideas at this point. Hopefully others more knowledgeable than I can step in here.



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

Larry - Whether it is an IP address used, or a URL used, they are effectively the same thing. DNS is used to mask an IP. DNS relates to an IP, without IP address, you wouldn't have domains.

Bill - REMOVE the extensions, allow ten to twenty minutes for this process to clear, then install the FPSE again, and again, allow ten to twenty minutes for the server to clear out the task, then try and connect to the server...

PS I didn't post this fer nuffin ya kno...

<edit>

Just checked my servers, and you should be connecting to:

http://65.254.59.194/ and then login as bdannels

My servers are setup in a similar way....

Larry - Nice try fella [;)]
</edit>



bdannels -> RE: Can't publish HTTP (12/18/2004 13:16:23)


>Just checked my servers, and you should be connecting to:
>http://65.254.59.194/ and then login as bdannels


If I click on the address you listed above it will NOT take me to my site

I don't understand, maybe it's ME trying to upload the site in the wrong area.

Based on the info listed below how should I enter the HTTP publish location in FrontPage?
---------------------------------------------


ACCOUNT INFORMATION:

Plan: Special
Domain: agisolutions.com
IP Address: 65.254.59.194
IP URL: http://65.254.59.194/~bdannels/

* You must place your files in the public_html folder and name your main page index.html

FTP INFORMATION:

Host: 65.254.59.194
Username: bdannels
Password: llibbill

Thanks Again
Bill



Giomanach -> RE: Can't publish HTTP (12/18/2004 13:23:55)

1) Remove the FTP login details
2) Just do as I say, it will work



Larry M. -> RE: Can't publish HTTP (12/18/2004 15:37:41)

quote:

Larry - Nice try fella


Dan,

Thanks ... but no cigar by a long shot. Right?

I think I need to stay off the Server Issues Forum[8D]

Regards,



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

Larry...the only way to learn is to make mistakes, and it is something that happens to everyone....we can't do anything bout it...

Hang about...you may learn something from me[img]http://php-net.net/images/smiles/icon_biggrin.gif[/img]



bdannels -> RE: Can't publish HTTP (12/18/2004 18:53:10)

quote:

the only way to learn is to make mistakes


I make enough for all of you guys [:)]

Question: What do I enter for the domain address so that I can check the FP server ext. on my server?

I thought I tried every possible way, (with www without www) could not get a response.

Thanks again
Bill
-----------------------------

http://www.dnswiz.com/fptype.asp shows:

WWW Site: http://65.254.59.194/~bdannels/
Port: 80
Server Software: This Web Server Does Not Disclose Identity
FrontPage Extensions: NO



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

I suggest you read this:

http://www.frontpagewebmaster.com/m-242682/tm.htm




bdannels -> RE: Can't publish HTTP (12/18/2004 20:04:29)

Dan:

Thanks for the link.

I want to thank you and the others for all your patience and help.

I just got a reply back from support on my new server. They said I can not http up load untill my domain name resolves See Below

Thanks again
Bill

--------------------------------------------------
Hello,

Frontpage extensions are enabled and installed by default. Therefore, once your domain name has resolved, you can easily publish your website via HTTP. Please see the following document and demo for further clarification.

Again, you will want to wait until your domain name has resolved.



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

quote:

- vaguely remember something to do with two sets of files being maintained on their UNIX server - one for the IP, the other for HTTP.

Sounds like nonsense to me! The domain name resolves to the IP address when the name servers are pointing to it. So the IP and domain name are actually one and the same thing. There should not be two sets of files on the server if you published to both.

quote:

... Right?

Yes! Plus, when you are simply transfering an existing site from one server to another, it means that it is fully functional when the first visitor arrives after propagation has commenced.

quote:

I gather you agree that once the site is active the IP shouldn't be used

Hmmm, I use the domain name after propagation, but I can't see that continuing to use the IP would cause any problems.

quote:

and the integrity of FP Extensions are probably an issue in bdannels case.

Correct! [:)][;)]

Bill, good luck with publishing when the NS have resolved. I find your host's advice strange, given that I have published to IP addresses successfully (on Unix servers) numerous times in the past, but I guess I don't know much.



bdannels -> RE: Can't publish HTTP (12/18/2004 22:00:58)

I told them I didn't buy into what they were saying. BUT

My Mother told me,

never argue with a SERVER!

Thaks again

Bill



dpf -> RE: Can't publish HTTP (12/19/2004 8:12:21)

quote:

My Mother told me,

never argue with a SERVER!
lol



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

Dan:

I am at my wits end on this, my domain name has ben resolved/changed to my NEW server. I don't think everything is working correctly and I am NOT smart enough to tell if I am correct.

The server support people are getting very short with me at this point, not sure what to do next. Maybe everything os OK and I just don't understand what's going on.

Question (1) If it says that my domain name is resolved to 65.254.59.194 Should I be able to get to my site by typing in
http://agisolutions.com OR http://65.254.59.194/ ? are they not the same?

Question (2) Is there anyway "http://agisolutions.com" is still going to my old server or looking like it's going to my old server?

Question (3) When I uploaded my files to the NEW server I uploaded then to "http://65.254.59.194/~bdannels/" do I have to I have to delete them and publish them to "http://agisolutions.com"?

Thank you for any input you can give my to get through this.

Bill




Giomanach -> RE: Can't publish HTTP (12/19/2004 10:43:56)

Bill

I ran a whois search on the domain agisolutions.com, and the IP returned as: http://168.144.31.234/

the current details are:

quote:

Website Title: Parking Permits, Parking Hang Tags, Hard Hat Stickers, Custom Decals, Parking Tags, Static Cling Decals and Roll Labels
Meta Description: Supplier of custom printed labels and decals. Specializing in parking permits, hang tags, hard hat decals and roll labels.
Meta Keywords: hard hat stickers, parking hang tags, custom decals, parking tags, hard hat decals, parking permits, static cling decals, parking decals, parking hang tag, roll labels, static cling stickers, reflective decals, custom window decals, parking permit
Response Code: 206
SSL Cert: *.softcomca.com expires in 108 days
DMOZ Directory: United_States
DMOZ Title: AGI Pressure Sensitive Products Inc.
DMOZ Description: Supplier of pressure sensitive labels and decals, including foil and die cut labels, and laser sheets.
Server Type: Microsoft-IIS/6.0
IP Address: 168.144.31.234 (ARIN & RIPE IP search)
IP Location: - Ontario - Toronto - Softcom Technology Consulting Inc
Record Type: Domain Name
Monitor: Monitor or Backorder
Wildcard search: 'agisolutions' or 'solutions' in all domains.
Other TLDs:
.com .net .org .info .biz .us
X [5 available domains]
Name Server: NS3.SOFTCOMCA.COM NS4.SOFTCOMCA.COM
ICANN Registrar: TUCOWS INC.
Created: 06-aug-1999
Expires: 06-aug-2005
Status: ACTIVE


Who are you hosted with?



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

http://ace-host.net/



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

Never heard of 'em[:D]

Have you tried contacting your old host and asking them to release the domain? It is still resolving to the old IP address



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

Dan:

No, I thought it was automatic, they sent me the link to change
my host.

Will contact them now, thanks for the heads up

Bill



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

Dan:

I just got this back from my NEW host.

I was confused before NOW I am really Confused!!

Can I be at two places at the same time?

I just checked with my Wife ...... she says NO :)
-----------------------------------------------------------
Time to look up agisolutions.com A record
Generated by www.DNSstuff.com at 18:33:52 GMT on 19 Dec 2004.
Searching for agisolutions.com A record at a.root-servers.net Got referral to F.GTLD-SERVERS.NET. [took 45 ms]
Searching for agisolutions.com A record at F.GTLD-SERVERS.NET. Got referral to ns87.securenet-server.net. [took 101 ms]
Searching for agisolutions.com A record at ns87.securenet-server.net. Reports an answer.

Record is:


Domain Type Class TTL Answer agisolutions.com. A IN 14400 65.254.59.194 agisolutions.com. NS IN 14400 ns87.securenet-server.net. agisolutions.com. NS IN 14400 ns88.securenet-server.net. ns87.securenet-server.net. A IN 4156 65.254.59.195 ns88.securenet-server.net. A IN 146861 65.254.59.196




dpf -> RE: Can't publish HTTP (12/19/2004 14:08:56)

quote:

I just checked with my Wife ...... she says NO
though they often expect it!



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

Dan:

My email is bouncing back to me now :(

Permanent Failure: 550-"The_recipient_cannot_be_verified.


---------------------------------------------------
Updated Info, from my OLD SERVER
---------------------------------------------------
Greetings,

The name servers around the world may not have fully updated yet.

I check on our end and the domain isn't resolving to us.

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

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

Reply from 65.254.59.194: bytes=32 time=33ms TTL=50
Reply from 65.254.59.194: bytes=32 time=33ms TTL=50
Reply from 65.254.59.194: bytes=32 time=33ms TTL=50
Reply from 65.254.59.194: bytes=32 time=33ms TTL=50
-----------------------------------------------------------------------

I guess I just wait, .......... wait for what?

4, 8, 12 hours, 1 or 2 days? All this down time this is costing me money!

Please pass me the bottle, again :)

Thanks again
Bill




Page: [1] 2   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.09375