RE: Website up, then down, then up, etc.
> > > > It certainly is perplexing. > > > > > It is, isn't it? > > > > Yes. I've had similar impossible problems in the past. One time it > > turned out to be a broken network cable, and the other time it was > > just my inability to fathom the somewhat obscure way a particular > > device implemented packet filtering. Once you know what the answer > > is, you'll wonder how it took you so long to realise something so > > obvious... > > Been there, done that, got the T-shirt. :-) > I'm currently installing Apache2 on larry, the secondary FBSD > machine to see if it works from there. > That should give me a clue, and won't hurt anything at all. Well, it's working now, but I don't know why. :-0 I unplugged the Cable Modem and Router overnight while I was at work. When I got home from work this morning, I installed Apache2 on larry, and configured the router to forward to larry on port 80. No joy. I reset all the router options to the defaults, and set up the port forwarding. No joy. Later, I decided to try and bypass the router by connecting curly (the original webserver) directly to the Cable Modem. I set curly for DHCP and rebooted, but it couldn't get an IP address (I probably didn't configure it right), so I set it back the way it was originally, and rebooted. Now it's working. 22:30 UTC. Mother used to tell me, "Stop stomping around in the kitchen! I'm baking a cake, and it will fall." I'm going to walk very softly for a while. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Website up, then down, then up, etc.
> > > On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote: > > > > Hmmm... It's not the basic "look up the IP number" part as that's > > > working just fine. You don't seem to be using their (dynDNS) web > > > redirection service (ie. howse.homeunix.net resolves to > 66.168.145.25 > > > which whois reports belongs to Charter Communications). > > > Correct, I'm not. > > I can't get 'homeunix.net' as a domain using WebHop. > > Shouldn't need it anyway, things were working perfectly > without it until > > last week. > > Right. That eliminates a bunch of stuff that could go wrong. > > > > I think that dynDNS would seem to have managed to pull off their > > > datacenter move without much noticable fallout. That's pretty > > > impressive... > > > > If Charter are denying any interference with the port 80 > traffic at > > > all, then they are almost certainly correct. > > > > I think you've established that your FreeBSD box is > working correctly. > > > There's no possibility that I've hosed anything like > /etc/hosts.allow or > > one of the files that restricts connections? > > Unless you're updating hosts.allow every 5 minutes I don't see how a > mistake in that file could result in the on again, off again behaviour > you've been seeing. The same goes for any of the flat files in /etc > -- or at least, I can't think what you could possibly do to any of > them that would result in the effects you're seeing. Well, that's true, however it's completely dead now. No off and on. Points again to the router, eh? > > > So, I guess, by a process of elimination you might have a > problem with > > > your cable router/modem? Is this a device that has a > HTTP interface > > > that you can configure it with? -- since it seems to be working > > > perfectly well for all of the other ports, there must be > some reason > > > for it to do nasty things specifically to the port 80 stuff. > > > Yes, the router has a web interface for configuration. It > had been set > > to forward requests on port 80 to the webserver on port 80. > That was > > working perfectly for over a year. I've now set it to port > 8080, in and > > out, which is, of course, working. I have also enabled the > DMZ, which, > > AFAIK, places the server outside the firewall, thereby eliminating > > it...? > > Hmmm... At the moment I'd lean towards the theory that you have a > fault in your router. Does power cycling the router make any > difference? Can you get hold of a spare router you could swap in to > test if that makes a difference? I have power cycled the router and the modem, which BTW are separate pieces of hardware. No joy. I can set it back to the defaults, no problem. I'm not doing anything special with it. I *might* be able to borrow another one to test with, but it would be a different brand. That shouldn't make any difference. I have a hub I can install in place of the router. Can't remember right now whether it's 10/100 or just 10. I'll check. > > > It certainly is perplexing. > > > It is, isn't it? > > Yes. I've had similar impossible problems in the past. One time it > turned out to be a broken network cable, and the other time it was > just my inability to fathom the somewhat obscure way a particular > device implemented packet filtering. Once you know what the answer > is, you'll wonder how it took you so long to realise something so > obvious... Been there, done that, got the T-shirt. :-) I'm currently installing Apache2 on larry, the secondary FBSD machine to see if it works from there. That should give me a clue, and won't hurt anything at all. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
On Sat, Oct 25, 2003 at 05:07:31PM -0500, Charles Howse wrote: > > On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote: > > Hmmm... It's not the basic "look up the IP number" part as that's > > working just fine. You don't seem to be using their (dynDNS) web > > redirection service (ie. howse.homeunix.net resolves to 66.168.145.25 > > which whois reports belongs to Charter Communications). > Correct, I'm not. > I can't get 'homeunix.net' as a domain using WebHop. > Shouldn't need it anyway, things were working perfectly without it until > last week. Right. That eliminates a bunch of stuff that could go wrong. > > I think that dynDNS would seem to have managed to pull off their > > datacenter move without much noticable fallout. That's pretty > > impressive... > > If Charter are denying any interference with the port 80 traffic at > > all, then they are almost certainly correct. > > I think you've established that your FreeBSD box is working correctly. > There's no possibility that I've hosed anything like /etc/hosts.allow or > one of the files that restricts connections? Unless you're updating hosts.allow every 5 minutes I don't see how a mistake in that file could result in the on again, off again behaviour you've been seeing. The same goes for any of the flat files in /etc -- or at least, I can't think what you could possibly do to any of them that would result in the effects you're seeing. > > So, I guess, by a process of elimination you might have a problem with > > your cable router/modem? Is this a device that has a HTTP interface > > that you can configure it with? -- since it seems to be working > > perfectly well for all of the other ports, there must be some reason > > for it to do nasty things specifically to the port 80 stuff. > Yes, the router has a web interface for configuration. It had been set > to forward requests on port 80 to the webserver on port 80. That was > working perfectly for over a year. I've now set it to port 8080, in and > out, which is, of course, working. I have also enabled the DMZ, which, > AFAIK, places the server outside the firewall, thereby eliminating > it...? Hmmm... At the moment I'd lean towards the theory that you have a fault in your router. Does power cycling the router make any difference? Can you get hold of a spare router you could swap in to test if that makes a difference? As to what exactly the fault is, it would have to be pretty subtle to only affect traffic on port 80. The suggestion about making sure your firmware was up to date by Chris Pressey elsewhere in this thread was right on the mark. Even so, the thing could have developed a bad spot in it's memory or some such. Or you may have inadvertently turned on some peculiar feature that you really didn't want to. As I've never encountered a 'Motorola Surfboard 4-port Cable/DSL Router: SpeedStream SS2604' in real life, there's not much coherent I can suggest though. > Now I've told apache to listen on port 80, no joy. Change back to 8080, > perfect! > > It certainly is perplexing. > It is, isn't it? Yes. I've had similar impossible problems in the past. One time it turned out to be a broken network cable, and the other time it was just my inability to fathom the somewhat obscure way a particular device implemented packet filtering. Once you know what the answer is, you'll wonder how it took you so long to realise something so obvious... > Dyndns support just answered my last post to them, and basically just > explained what DNS does as a way of denying that they are at fault, and > I believe them. To quote them, "DNS is just like the Yellow Pages. > Your phone book doesn't know you are going through it, calling every > number, and subsequently start deleting entries." Yup. I think they've been eliminated from our enquiries. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
RE: Website up, then down, then up, etc.
> On Sat, 25 Oct 2003 17:07:31 -0500 > "Charles Howse" <[EMAIL PROTECTED]> wrote: > > > Yes, the router has a web interface for configuration. It had been > > set to forward requests on port 80 to the webserver on port > 80. That > > was working perfectly for over a year. I've now set it to > port 8080, > > in and out, which is, of course, working. I have also enabled the > > DMZ, which, AFAIK, places the server outside the firewall, thereby > > eliminating it...? > > > > Now I've told apache to listen on port 80, no joy. Change back to > > 8080, perfect! > > Sorry if this is a shot in the dark, but are you sure the firmware in > your router is up-to-date? Encountered a similar case once where this > was the problem, so it might be worth checking out. Thanks for the reminder to check, but I have v.1.1 release 5, and the latest version on their website is v.1.0 release 5. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
On Sat, 25 Oct 2003 17:07:31 -0500 "Charles Howse" <[EMAIL PROTECTED]> wrote: > Yes, the router has a web interface for configuration. It had been > set to forward requests on port 80 to the webserver on port 80. That > was working perfectly for over a year. I've now set it to port 8080, > in and out, which is, of course, working. I have also enabled the > DMZ, which, AFAIK, places the server outside the firewall, thereby > eliminating it...? > > Now I've told apache to listen on port 80, no joy. Change back to > 8080, perfect! Sorry if this is a shot in the dark, but are you sure the firmware in your router is up-to-date? Encountered a similar case once where this was the problem, so it might be worth checking out. -Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Website up, then down, then up, etc.
> On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote: > > > > That's good in one way: it means that your system is > actually working > > > perfectly well. Unfortunately it also implies that the problem is > > > actually somewhere in the network downstream of you. > Since it seems > > > to affect all external users equally, the problem must be > within your > > > service provider's network. The only thing you can do is open a > > > ticket with your support and pray that it gets looked at > by someone > > > with a clue. > > > > > > The on/off behaviour often means that you're interacting > with a dual > > > server system, which is possibly meant to provide > redundancy, but one > > > of the servers isn't working correctly and the load balance isn't > > > cutting out the duff machine. > > > > ARGGHHH!! > > Are you talking about my ISP (Charter Communications) or my > Dynamic DNS > > service (DYNdns.org)? > > > > I have just spoken to Charter Tech Support for the second time about > > this, and the tech assured me that they were not > 'affecting' port 80 in > > any way, nor were they using anything similar to portsentry. > > > > It seems more likely to me that the culprit is DYNdns.org, > since I have > > only been using them since about the 11th of this month, > and *also* they > > have just completed a major task - moving their datacenter. > > http://www.dyndns.org/news/status/ > > > Check out all that they did within the last 5 days. > > I have corresponded with them once and here is the gist of it: > > Hmmm... It's not the basic "look up the IP number" part as that's > working just fine. You don't seem to be using their (dynDNS) web > redirection service (ie. howse.homeunix.net resolves to 66.168.145.25 > which whois reports belongs to Charter Communications). Correct, I'm not. I can't get 'homeunix.net' as a domain using WebHop. Shouldn't need it anyway, things were working perfectly without it until last week. > I think that dynDNS would seem to have managed to pull off their > datacenter move without much noticable fallout. That's pretty > impressive... > > If Charter are denying any interference with the port 80 traffic at > all, then they are almost certainly correct. > > I think you've established that your FreeBSD box is working correctly. There's no possibility that I've hosed anything like /etc/hosts.allow or one of the files that restricts connections? > So, I guess, by a process of elimination you might have a problem with > your cable router/modem? Is this a device that has a HTTP interface > that you can configure it with? -- since it seems to be working > perfectly well for all of the other ports, there must be some reason > for it to do nasty things specifically to the port 80 stuff. Yes, the router has a web interface for configuration. It had been set to forward requests on port 80 to the webserver on port 80. That was working perfectly for over a year. I've now set it to port 8080, in and out, which is, of course, working. I have also enabled the DMZ, which, AFAIK, places the server outside the firewall, thereby eliminating it...? Now I've told apache to listen on port 80, no joy. Change back to 8080, perfect! > It certainly is perplexing. It is, isn't it? Dyndns support just answered my last post to them, and basically just explained what DNS does as a way of denying that they are at fault, and I believe them. To quote them, "DNS is just like the Yellow Pages. Your phone book doesn't know you are going through it, calling every number, and subsequently start deleting entries." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
On Sat, Oct 25, 2003 at 02:25:54PM -0500, Charles Howse wrote: > > That's good in one way: it means that your system is actually working > > perfectly well. Unfortunately it also implies that the problem is > > actually somewhere in the network downstream of you. Since it seems > > to affect all external users equally, the problem must be within your > > service provider's network. The only thing you can do is open a > > ticket with your support and pray that it gets looked at by someone > > with a clue. > > > > The on/off behaviour often means that you're interacting with a dual > > server system, which is possibly meant to provide redundancy, but one > > of the servers isn't working correctly and the load balance isn't > > cutting out the duff machine. > > ARGGHHH!! > Are you talking about my ISP (Charter Communications) or my Dynamic DNS > service (DYNdns.org)? > > I have just spoken to Charter Tech Support for the second time about > this, and the tech assured me that they were not 'affecting' port 80 in > any way, nor were they using anything similar to portsentry. > > It seems more likely to me that the culprit is DYNdns.org, since I have > only been using them since about the 11th of this month, and *also* they > have just completed a major task - moving their datacenter. > http://www.dyndns.org/news/status/ > Check out all that they did within the last 5 days. > I have corresponded with them once and here is the gist of it: Hmmm... It's not the basic "look up the IP number" part as that's working just fine. You don't seem to be using their (dynDNS) web redirection service (ie. howse.homeunix.net resolves to 66.168.145.25 which whois reports belongs to Charter Communications). I think that dynDNS would seem to have managed to pull off their datacenter move without much noticable fallout. That's pretty impressive... If Charter are denying any interference with the port 80 traffic at all, then they are almost certainly correct. I think you've established that your FreeBSD box is working correctly. So, I guess, by a process of elimination you might have a problem with your cable router/modem? Is this a device that has a HTTP interface that you can configure it with? -- since it seems to be working perfectly well for all of the other ports, there must be some reason for it to do nasty things specifically to the port 80 stuff. It certainly is perplexing. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
RE: Website up, then down, then up, etc.
> On Sat, Oct 25, 2003 at 10:58:53AM -0500, Charles Howse wrote: > > I did change the listen address to 8080 in httpd.conf and > in the port > > forward on the router, and rebooted. > > NOW IT IS WORKING! As of 10:42 CDT, which is 16:42 UTC. > > http:/howse.homeunix.net:8080 > > Is there anything else to look at, or any files to peruse? > > Running on port 8080 is _*not really acceptable for the long run*_. > > That's good in one way: it means that your system is actually working > perfectly well. Unfortunately it also implies that the problem is > actually somewhere in the network downstream of you. Since it seems > to affect all external users equally, the problem must be within your > service provider's network. The only thing you can do is open a > ticket with your support and pray that it gets looked at by someone > with a clue. > > The on/off behaviour often means that you're interacting with a dual > server system, which is possibly meant to provide redundancy, but one > of the servers isn't working correctly and the load balance isn't > cutting out the duff machine. ARGGHHH!! Are you talking about my ISP (Charter Communications) or my Dynamic DNS service (DYNdns.org)? I have just spoken to Charter Tech Support for the second time about this, and the tech assured me that they were not 'affecting' port 80 in any way, nor were they using anything similar to portsentry. It seems more likely to me that the culprit is DYNdns.org, since I have only been using them since about the 11th of this month, and *also* they have just completed a major task - moving their datacenter. http://www.dyndns.org/news/status/ Check out all that they did within the last 5 days. I have corresponded with them once and here is the gist of it: (Me) [snip] > > Can you think of *anything* on your end that may be contributing to > > this problem? (Them) > No, nothing on our end would be contributing to this. Since the host > name is resolving the DNS is working correctly. Connections on port > 80 are being refused so this would seem to be a problem with your > router or with the web server itself. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
On Sat, Oct 25, 2003 at 10:58:53AM -0500, Charles Howse wrote: > I did change the listen address to 8080 in httpd.conf and in the port > forward on the router, and rebooted. > NOW IT IS WORKING! As of 10:42 CDT, which is 16:42 UTC. > http:/howse.homeunix.net:8080 > Is there anything else to look at, or any files to peruse? > Running on port 8080 is _*not really acceptable for the long run*_. That's good in one way: it means that your system is actually working perfectly well. Unfortunately it also implies that the problem is actually somewhere in the network downstream of you. Since it seems to affect all external users equally, the problem must be within your service provider's network. The only thing you can do is open a ticket with your support and pray that it gets looked at by someone with a clue. The on/off behaviour often means that you're interacting with a dual server system, which is possibly meant to provide redundancy, but one of the servers isn't working correctly and the load balance isn't cutting out the duff machine. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Website up, then down, then up, etc.
How often do you reboot your router? My router flakes out every few months and I need to reboot it. On Oct 24, 2003, at 8:14 PM, Charles Howse wrote: Hi, For the past week or so I've been pulling my hair out trying to diagnose what's going on with my website. Prior to that, everything was working perfectly. I've made no changes that I was aware of. There is no pattern to this...sometimes I can connect to the web server over the Internet, sometimes not. I can always connect to the FTP server over the Internet, so DNS services appear to be working. I have just written my Dynamic DNS service, DYNdns.org, no reply yet. I called my ISP, they're not blocking inbound connections on port 80. "lynx localhost" always works on the web server. "host howse.homeunix.net" always resolves correctly. "apachectl restart" doesn't help. Rebooting the web server doesn't help. I can force an IP update successfully with ddclient. On my WinXP box, http://curly always works. Try it yourself: http://howse.homeunix.net Not working as of 19:05 this date, CDT (UTC -6:00). What in the world could be happening? The software setup: Apache2 vsftpd FreeBSD 4.8-RELEASE-p13 The network setup: Dynamic DNS service: DYNdns.org ISP: Charter Communications Cable Modem: Motorola Surfboard 4-port Cable/DSL Router: SpeedStream SS2604 (port forwarding enabled) Thanks, Charles Got a computer with idle CPU time? Join [EMAIL PROTECTED] and help make history! http://setiathome.ssl.berkeley.edu/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Lucas Holt [EMAIL PROTECTED] FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein (1879-1955) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
On Friday 24 October 2003 08:36 pm, Charles Howse wrote: > > Hi Charles, > > > > --On Friday, October 24, 2003 08:40:09 PM -0500 Charles Howse > > > > <[EMAIL PROTECTED]> wrote: > > > Strange > > > Looking at the header from your email, you came from: > > > > mygirlfriday.info > > > > > That resolves to 65.64.145.209 > > > > The above is the address of my remote mail/DNS server. My > > static IP that I > > connected to your port 80 is reflected at 65.41.216.204 > > > > > I see no record of that in /var/log/httpd-access.log. > > > Could you please confirm the IP address, and convert the time you > > > connected to UTC? > > > > I do not remember what time it was, but it will be in your > > logs. If not, I > > will log on again. > > > > Both of your questions were available in the email headers > > from the email > > originally sent to you. Both of my IP addresses were in the > > headers, as > > well as the time. > > Thanks for that clarification. > I do indeed see you in the logfile at 19:31. > Now I'm getting spooked! Could I be blocked from my own site? > I've been portscanning it a few times, moving it inside and outside the > firewall. > I don't have anything installed that would block an IP from using port > 80. > It's down now at 10:34 CDT, moving it outside the firewall didn't help. > Sheshwhat's going on? Are you using nat? Could you be losing your dhcp lease and then renew it and get access to apache back. I have 2 NICs in crystal and http://crystal always works on the internal network. I don't do that very often because I have a router after the DSL modem and use the external address for even my internal accesses. Crystal's firewall does the nat translation for the 6 machines connected through it. Topaz (this machine) has its own IP and doesn't do nat. The firewall is also much tighter and anyone using the IP address is trying to break in. I log everything on this system. It cost me more for 2 static IPs but that was a lot less trouble. You don't always have that choice. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
Hi Charles, On Fri, 24 Oct 2003 22:36:17 -0500 GMT (10/24/2003, 10:36 PM +0500 GMT my time), Charles Howse wrote: C> Thanks for that clarification. You are welcome. C> I do indeed see you in the logfile at 19:31. Good, at least WAN wise, you are fine. C> Now I'm getting spooked! Could I be blocked from my own site? Maybe a tcpdump with focus on port 80 will yield some answers. C> I've been portscanning it a few times, moving it inside and outside the C> firewall. I take it no problems there. That is to say, it shows up. C> I don't have anything installed that would block an IP from using port C> 80. It's down now at 10:34 CDT, moving it outside the firewall didn't C> help. Sheshwhat's going on? What comes to mind is DNS. Is your www address resolvable from inside your LAN to your IP address? What do your logs say? -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Website up, then down, then up, etc.
> Hi Charles, > > --On Friday, October 24, 2003 08:40:09 PM -0500 Charles Howse > <[EMAIL PROTECTED]> wrote: > > > Strange > > Looking at the header from your email, you came from: > mygirlfriday.info > > That resolves to 65.64.145.209 > > The above is the address of my remote mail/DNS server. My > static IP that I > connected to your port 80 is reflected at 65.41.216.204 > > > I see no record of that in /var/log/httpd-access.log. > > Could you please confirm the IP address, and convert the time you > > connected to UTC? > > I do not remember what time it was, but it will be in your > logs. If not, I > will log on again. > > Both of your questions were available in the email headers > from the email > originally sent to you. Both of my IP addresses were in the > headers, as > well as the time. Thanks for that clarification. I do indeed see you in the logfile at 19:31. Now I'm getting spooked! Could I be blocked from my own site? I've been portscanning it a few times, moving it inside and outside the firewall. I don't have anything installed that would block an IP from using port 80. It's down now at 10:34 CDT, moving it outside the firewall didn't help. Sheshwhat's going on? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Website up, then down, then up, etc.
Hi Charles, --On Friday, October 24, 2003 08:40:09 PM -0500 Charles Howse <[EMAIL PROTECTED]> wrote: Strange Looking at the header from your email, you came from: mygirlfriday.info That resolves to 65.64.145.209 The above is the address of my remote mail/DNS server. My static IP that I connected to your port 80 is reflected at 65.41.216.204 I see no record of that in /var/log/httpd-access.log. Could you please confirm the IP address, and convert the time you connected to UTC? I do not remember what time it was, but it will be in your logs. If not, I will log on again. Both of your questions were available in the email headers from the email originally sent to you. Both of my IP addresses were in the headers, as well as the time. -- Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Website up, then down, then up, etc.
> > Try it yourself: http://howse.homeunix.net > > I connected without any problem at 20:58 24 Oct (UTC -4:00). I am > running the same 4.8 version you are. > > > Not working as of 19:05 this date, CDT (UTC -6:00). Check my math here... You connected at 20:58 + 4:00 = 00:58 UTC I was down at 19:05 + 6:00 = 01:05 UTC So you connected before I noticed I was down...? I'm not positive it was down then. Currently down at 20:20 CDT = 02:20 UTC > > > > What in the world could be happening? > > > > The software setup: > > Apache2 > > vsftpd > > FreeBSD 4.8-RELEASE-p13 > > > > The network setup: > > Dynamic DNS service: DYNdns.org > > ISP: Charter Communications > > Cable Modem: Motorola Surfboard > > 4-port Cable/DSL Router: SpeedStream SS2604 (port > forwarding enabled) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Website up, then down, then up, etc.
> Hi Charles, > > --On Friday, October 24, 2003 07:14:21 PM -0500 Charles Howse > <[EMAIL PROTECTED]> wrote: > > > Try it yourself: http://howse.homeunix.net > > Not working as of 19:05 this date, CDT (UTC -6:00). > > > > What in the world could be happening? > > I just logged on without a problem, and very quickly. Looks good.. Strange Looking at the header from your email, you came from: mygirlfriday.info That resolves to 65.64.145.209 I see no record of that in /var/log/httpd-access.log. Could you please confirm the IP address, and convert the time you connected to UTC? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Website up, then down, then up, etc.
> > Try it yourself: http://howse.homeunix.net I connected without any problem at 20:58 24 Oct (UTC -4:00). I am running the same 4.8 version you are. > Not working as of 19:05 this date, CDT (UTC -6:00). > > What in the world could be happening? > > The software setup: > Apache2 > vsftpd > FreeBSD 4.8-RELEASE-p13 > > The network setup: > Dynamic DNS service: DYNdns.org > ISP: Charter Communications > Cable Modem: Motorola Surfboard > 4-port Cable/DSL Router: SpeedStream SS2604 (port forwarding enabled) > > > > Thanks, > Charles > > Got a computer with idle CPU time? > Join [EMAIL PROTECTED] and help make history! > http://setiathome.ssl.berkeley.edu/ > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Website up, then down, then up, etc.
Hi, For the past week or so I've been pulling my hair out trying to diagnose what's going on with my website. Prior to that, everything was working perfectly. I've made no changes that I was aware of. There is no pattern to this...sometimes I can connect to the web server over the Internet, sometimes not. I can always connect to the FTP server over the Internet, so DNS services appear to be working. I have just written my Dynamic DNS service, DYNdns.org, no reply yet. I called my ISP, they're not blocking inbound connections on port 80. "lynx localhost" always works on the web server. "host howse.homeunix.net" always resolves correctly. "apachectl restart" doesn't help. Rebooting the web server doesn't help. I can force an IP update successfully with ddclient. On my WinXP box, http://curly always works. Try it yourself: http://howse.homeunix.net Not working as of 19:05 this date, CDT (UTC -6:00). What in the world could be happening? The software setup: Apache2 vsftpd FreeBSD 4.8-RELEASE-p13 The network setup: Dynamic DNS service: DYNdns.org ISP: Charter Communications Cable Modem: Motorola Surfboard 4-port Cable/DSL Router: SpeedStream SS2604 (port forwarding enabled) Thanks, Charles Got a computer with idle CPU time? Join [EMAIL PROTECTED] and help make history! http://setiathome.ssl.berkeley.edu/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
