Dear All,
I often have trouble validating my CSS, because the server seems to disappear suddenly - as in, "Could not connect to remort server" (Opera's message to me) - moments after it's been working.
Other times, it loads very slowly and hesitantly, but then will work for a short time.
And sometimes, it works without problems.
Does anybody else have this experience? I'm on the West Coast of Canada, if that makes any difference.
Fri, 28 Jan 2005 06:12:09I've never had any trouble with it. Perhaps it is your local internet connection...domain name servers and all that nonsense.
Originally posted by Triumph
I've never had any trouble with it. Perhaps it is your local internet connection...domain name servers and all that nonsense.
I know as much about domain name servers as I do about CSS <hehe> - head spinning again. But I'm not too bad a parrot, and I could and will check with my ISP - I could ask them if there's a problem "resolving the domain name" (I just made up that phrase in quotes - does it make sense? <haha!>)
I suppose I could try a different browser, too; I'm using the current Opera for Windows (on XP, SP2). I have FireFox, for instance. I like Opera better <g>.
Fri, 28 Jan 2005 06:34:43Originally posted by CarolW
I could ask them if there's a problem "resolving the domain name" (I just made up that phrase in quotes - does it make sense? <haha!>) It makes sense to me.
I should use it around company and see if anyone knows what I'm talking about.It is probably Apache failing so you get the could not resolve domain error
I had been having this problem lately as well
Until we recompiled Apache
you need to talk to your host that is where the problem lies
Good luck!Originally posted by BeachSide
It is probably Apache failing so you get the could not resolve domain error
I had been having this problem lately as well Until we recompiled Apache
you need to talk to your host that is where the problem lies
Good luck!
Thanks, Beachside. Really appreciate your reply!
I strongly doubt it's my host. It's a small, local company, with extremely attentive service to customers, and very careful work on their service altogether. However, I did mention the problem to them, in our local forums, and they suggested I try Traceroute, which they provide.
I can't make Traceroute work fully, and wonder if I'm blocking an outgoing trace with my ZoneAlarm Pro firewall. I had been using the free version, was given the Pro version, and haven't taken the time to study it - too busy trying to make my web site <g>.
Maybe I should look into it further (study? <g>), but - I am able to bring up the CSS Validation Service much of the time. It' just inconvenient when I can't. Dropping a hint to my ISP never hurts, though! Probably they can't do much about it now, as they're doing various major revampings, so my wish would be low priority, unless they perceive some kind of problem with resoloving domain names (heh; more Carol-learning-jargon). I'm not hearing cmpolaints from other customers; also, they do an awful lot of resolving domain names, so perhaps it's specific to the CSS Validation service?
Sun, 30 Jan 2005 10:06:43Your site validates, 4.01 Transitional and no error or warning found in the css.
Congratulations!Originally posted by Fang
Your site validates, 4.01 Transitional and no error or warning found in the css.
Congratulations!
Fang, were you referring to my site? If so, thanks! But that was one thing I did know, because I put nothing on my site till it's validated <g>. Well, once or twice, I've done so with a CSS, just because I couldn't reach the validation service, but then I'd validate it shortly afterwards. And I do test it on my local machine before posting.
Sun, 30 Jan 2005 18:25:05Originally posted by Triumph
It makes sense to me.
I should use it around company and see if anyone knows what I'm talking about.
Triumph, I omitted to thank you for the nice little validation that I might actually be learning something! (I am. Just that it will take me a while to pull things together, but it's nice to make a little sense sometimes <blush>).
Sun, 30 Jan 2005 18:31:03
Edit: forgot to say: I love your particular sense of humor!Update report and probable thread-end <g>:
I worked - or is that played? - late last night, and the CSS Validator was right there, all the time, no problems.
Because I've noticed patterns in how accessible the validation service is to me, I suspect that at certain times of day, the servers are heavily loaded, and-or being attended to by those who maintain them. So I don't have to solve my TraceRoute problem yet <hehe>
Mon, 31 Jan 2005 07:21:09
I often have trouble validating my CSS, because the server seems to disappear suddenly - as in, "Could not connect to remort server" (Opera's message to me) - moments after it's been working.
Other times, it loads very slowly and hesitantly, but then will work for a short time.
And sometimes, it works without problems.
Does anybody else have this experience? I'm on the West Coast of Canada, if that makes any difference.
Fri, 28 Jan 2005 06:12:09I've never had any trouble with it. Perhaps it is your local internet connection...domain name servers and all that nonsense.
Originally posted by Triumph I've never had any trouble with it. Perhaps it is your local internet connection...domain name servers and all that nonsense.
I know as much about domain name servers as I do about CSS <hehe> - head spinning again. But I'm not too bad a parrot, and I could and will check with my ISP - I could ask them if there's a problem "resolving the domain name" (I just made up that phrase in quotes - does it make sense? <haha!>)
I suppose I could try a different browser, too; I'm using the current Opera for Windows (on XP, SP2). I have FireFox, for instance. I like Opera better <g>.
Fri, 28 Jan 2005 06:34:43Originally posted by CarolW
I could ask them if there's a problem "resolving the domain name" (I just made up that phrase in quotes - does it make sense? <haha!>) It makes sense to me.
I should use it around company and see if anyone knows what I'm talking about.
It is probably Apache failing so you get the could not resolve domain errorI had been having this problem lately as well
Until we recompiled Apacheyou need to talk to your host that is where the problem lies
Good luck!
Originally posted by BeachSide It is probably Apache failing so you get the could not resolve domain error
I had been having this problem lately as well
Until we recompiled Apacheyou need to talk to your host that is where the problem lies
Good luck!
Thanks, Beachside. Really appreciate your reply!
I strongly doubt it's my host. It's a small, local company, with extremely attentive service to customers, and very careful work on their service altogether. However, I did mention the problem to them, in our local forums, and they suggested I try Traceroute, which they provide.
I can't make Traceroute work fully, and wonder if I'm blocking an outgoing trace with my ZoneAlarm Pro firewall. I had been using the free version, was given the Pro version, and haven't taken the time to study it - too busy trying to make my web site <g>.
Maybe I should look into it further (study? <g>), but - I am able to bring up the CSS Validation Service much of the time. It' just inconvenient when I can't. Dropping a hint to my ISP never hurts, though! Probably they can't do much about it now, as they're doing various major revampings, so my wish would be low priority, unless they perceive some kind of problem with resoloving domain names (heh; more Carol-learning-jargon). I'm not hearing cmpolaints from other customers; also, they do an awful lot of resolving domain names, so perhaps it's specific to the CSS Validation service?
Sun, 30 Jan 2005 10:06:43Your site validates, 4.01 Transitional and no error or warning found in the css.
Congratulations!Originally posted by Fang
Your site validates, 4.01 Transitional and no error or warning found in the css.
Congratulations!
Fang, were you referring to my site? If so, thanks! But that was one thing I did know, because I put nothing on my site till it's validated <g>. Well, once or twice, I've done so with a CSS, just because I couldn't reach the validation service, but then I'd validate it shortly afterwards. And I do test it on my local machine before posting.
Sun, 30 Jan 2005 18:25:05Originally posted by Triumph
It makes sense to me.
I should use it around company and see if anyone knows what I'm talking about.
Triumph, I omitted to thank you for the nice little validation that I might actually be learning something! (I am. Just that it will take me a while to pull things together, but it's nice to make a little sense sometimes <blush>).
Sun, 30 Jan 2005 18:31:03
Edit: forgot to say: I love your particular sense of humor!Update report and probable thread-end <g>:
I worked - or is that played? - late last night, and the CSS Validator was right there, all the time, no problems.
Because I've noticed patterns in how accessible the validation service is to me, I suspect that at certain times of day, the servers are heavily loaded, and-or being attended to by those who maintain them. So I don't have to solve my TraceRoute problem yet <hehe>
Mon, 31 Jan 2005 07:21:09