It was working, now it isn't...

[whobutdrew]

Thanks to all of your help in my initial posts, I had my serverer up and running. I had created accounts, imported content, etc. Everything was shiny.

When the last code tour came around, I updated my code (and this is how I did it.) Ever since then, my site became a style-less, text only page, and only if I put http://www.subdomain.mydomain.tld:#### as the address (where http://subdomain.mydomain.tld worked before).

I updated my code again when the most recent code push came down, and now I don't even get that far. I have quintuple checked my DNS settings, those are all all right. What I have noticed is that if I telnet to my site address rather than via a browser, a whole slew of links appear as www.subdomain.mydomain.tld with no port specifications, despite my $DOMAIN and $SITEROOT variables being set in etc/config.pl. (Example: http://www.x-chronos.servegame.org/js/core.js)

I'm at my wits end. What happened? I can haz help?

Comments

[pne]

if I telnet to my site address rather than via a browser

You'll have to tell us some more.

"telnet www.subdomain.mydomain.tld" probably won't work, unless your HTTP server is listening in port 23 (or whatever the default telnet port was).

So I'm guessing that you did, at least, "telnet www.subdomain.mydomain.tld ####" and then spoke HTTP at the server... but what exactly did you say?

Specifically, did you say which version of HTTP you are talking? Did you include a Host: header?

I would expect something like this, for example:

GET / HTTP/1.0
Host: www.subdomain.mydomain.tld:####
User-Agent: Leet-telnet-skillz/3.14159

If you leave off the "HTTP/1.0", then I think the "Host:" header is not allowed (or expected), since HTTP 0.9 didn't define it TTBOMK. And if you leave off the Host: header, then the server won't know exactly which site you're interested in.

[whobutdrew]

I apologize about the lack of pertinent details.

I did telnet subdomain.mydomain.tld 9999. It blinked for a little while, didn't really show any signs of progress (if I was supposed to "speak HTML" here, then I didn't, as I'm used to SSH, not Telnet). When I control-c'd, I got a slew of HTML, all of the HREF tags had "http://www." as their URLs. I didn't capture it, but I will next chance I get, if it'll help.

[pne]

I did telnet subdomain.mydomain.tld 9999. It blinked for a little while, didn't really show any signs of progress

That sounds about right; telnet doesn't (in my experience) give a success message of its own when it's connected, and HTTP servers don't send a greeting the way (say) SMTP servers do. So if you've connected successfully, you'll just see nothing -- the server is waiting for you to tell it what page to serve.

if I was supposed to "speak HTML" here

Not HTML (which describes the page) but HTTP, the Hypertext Transfer Protocol (which, in this case, tells the server which page you want, and forms the first part of the server's response, telling you the response code, the content type, and a few more metadata things about the response it's sending).

If you can't speak raw HTTP, then telnetting to the HTTP server is unlikely to be useful for troubleshooting, but if you want to try it again, you can try to paste in the little snippet I provided in my previous answer.

You'll have to press Enter twice after the last line (in other words: leave a blank line after your request) so that the server knows that the request is over; you should then see a response -- some HTTP headers, followed by the page contents (i.e. HTML if you requested a web page, CSS if you requested a stylesheet, binary data if you requested an image, etc.).

[whobutdrew]

HTML, HTTP, whatever... :P

I'll try that tonight, if I can. We're going to Denver for the next week and a half for doctor's appointments (long story) so while I encourage further suggestions and recommendations, know that it'll be the end of the month before I get any relevant input back to you guys (and girls).

[whobutdrew]

Here's what I got when I entered the HTTP that you had last time.

[mark]

Have you run bin/checkconfig.pl and does it work? Are there any errors?

Did you look in the Apache error log, does it show any errors there?

When you visit your site, does it have any errors on the web page?

I don't see you saying anything about what errors you're getting, or what exactly it is (or isn't) doing right now...

[whobutdrew]

I have not run checkconfig. I will do so upon my arrival home from work today. >< That didn't occur to me at all.

I have seen no entries in my Apache error log other than it logged when I have restarted the services after each attempt at a fix.

I get no errors on the page itself, just all text, no css/style info.

Sorry for the lack of helpful info. Life ever encroaches on my plans...

[whobutdrew]

bin/checkconfig.pl --no=ljconfig

All good.

[whobutdrew]

I rebuilt my server from scratch, went through the wiki steps again, and now I'm live again.

Just wanted to let you know!