Where is it ? rootshell.be is going down. Thought I'll make yours my primary mirror. But...
yea this sucks. What am I gonna do at work now?
I just got into contact with Asemi, via text message. He is switching providers right now, which explains the downtime. Give it a while. Your site is not lost. :)
Yeah I know its not lost. He had some outages before, so I know he'll be back up. Anyone got an account at SDF ? Just want to know how it is. I need some place to host my little site. :)
i have a pretty reliable server and am willing to host things for people
That would be great. :) Didn't we have an IM sharing thread ? Whats your gmail/jabber id lucas ? You guys don't hang out at #bsd nowadays so I don't get to chat to you much.
lucasreddinger is at gmail
i can show up at #bsd, though.
i can show up at #bsd, though.
Ok. I'm on gmail after 9.00PM IST (+5.30) and on #bsd almost always. :)
yeah i'm not too happy that rootshell is going down..it really is one of the last large, great shell hosts.. :(
asemi what's up with thehomerow!?
asemi what's up with thehomerow!?
Yeah, will miss it.
just got the new Verizon DSL working a couple of hours ago. getting thehomerow back online now!
so I'm having quite a bit of trouble with this! the DSL modem Verizon provides acts as a router too so it's giving my OpenBSD router 192.168.1.2 for an IP address. kind of annoying, but whatever.
anyways, I guess Verizon is blocking port 80 somewhere. I'm attempting to use zoneedit.com to redirect thehomerow.net to thehomerow.net:8080 so it doesn't cause any problems.
I also need to set up a zoneedit client that will update stuff when/if my IP address changes. this is difficult since PPPoE is done on the modem and the zoneedit client would be running on the router. I do have the option of switching the modem into bridging mode and using OpenBSD's PPPoE software instead. this is probably what I'll do eventually, but right now I just want to eat dinner :).
this is making me contemplate not having a web server since it would be a hell of a lot easier and less confusing! I think I'd miss hosting my own stuff though.
anyways, I guess Verizon is blocking port 80 somewhere. I'm attempting to use zoneedit.com to redirect thehomerow.net to thehomerow.net:8080 so it doesn't cause any problems.
I also need to set up a zoneedit client that will update stuff when/if my IP address changes. this is difficult since PPPoE is done on the modem and the zoneedit client would be running on the router. I do have the option of switching the modem into bridging mode and using OpenBSD's PPPoE software instead. this is probably what I'll do eventually, but right now I just want to eat dinner :).
this is making me contemplate not having a web server since it would be a hell of a lot easier and less confusing! I think I'd miss hosting my own stuff though.
update!
I've got my OpenBSD router doing PPPoE now instead of the modem. so now the modem is in bridge mode instead of router mode and my LAN is about half as confusing as it was before. this is also nice because I can update my DNS records every time PPP starts up.
so here's how DNS is set up. thehomerow.net resolves to my actual IP, so things like logging in via SSH work. www.thehomerow.net, however, redirects to thehomerow.net:8080. this is done via what's called a WebForward on zoneedit.com (I love ZoneEdit :)). this kind of sucks because thehomerow.net without the www won't go to the website unless you specify port 8080.
the problem I'm having now is that users' directories won't work without the trailing slash.
http://www.thehomerow.net/~arun/ works, but http://www.thehomerow.net/~arun doesn't. for some reason the latter attempts to go to http://www2.thehomerow.net :8080/~arun/. I had the www2 set up as part of a WebForward before, but it's not there anymore, so I'm not sure why it's doing that or why the lack of a trailing slash would prompt it. I thought it might be ServerName in httpd.conf, but I changed that to thehomerow.net and that doesn't seem to have fixed anything :/.
I've got my OpenBSD router doing PPPoE now instead of the modem. so now the modem is in bridge mode instead of router mode and my LAN is about half as confusing as it was before. this is also nice because I can update my DNS records every time PPP starts up.
so here's how DNS is set up. thehomerow.net resolves to my actual IP, so things like logging in via SSH work. www.thehomerow.net, however, redirects to thehomerow.net:8080. this is done via what's called a WebForward on zoneedit.com (I love ZoneEdit :)). this kind of sucks because thehomerow.net without the www won't go to the website unless you specify port 8080.
the problem I'm having now is that users' directories won't work without the trailing slash.
http://www.thehomerow.net/~arun/ works, but http://www.thehomerow.net/~arun doesn't. for some reason the latter attempts to go to http://www2.thehomerow.net :8080/~arun/. I had the www2 set up as part of a WebForward before, but it's not there anymore, so I'm not sure why it's doing that or why the lack of a trailing slash would prompt it. I thought it might be ServerName in httpd.conf, but I changed that to thehomerow.net and that doesn't seem to have fixed anything :/.
:( ttf doesn't like those URLs with the port specifications.
Did you try changing the ServerName to thehomerow.net:8080
yay it works! I cleared my cache in Camino (web browser) and that fixed it. I guess it had cached some of the DNS stuff or something. thanks Gatzby for letting me know it was working from your end without the trailing slash.