An unfinished story about SE/30, DNS and WebStar.

[moosefuel]

I always wanted an SE/30, and I always wanted to try getting it online as a web server. I succeeded, for the most part. You can have a look at the landing page here: 76.67.165.247:8888 (note that this is a dynamic IP so it will change in a month or two on its own).

However, what I want to do is access it from my FQDN, with a port number. I've done this many times, in fact you can view my Newton-powered web server here: http://moosefuel.media:8080 (on a good day it won't have crashed too often). It's just a matter of opening the right ports and forwarding :8080 to the Newt.

So I opened the ports in my router for the SE/30, and accessing it via IP works fine, but if I try to use http://moosefuel.media:8888 as I set up, I get no response.

Does anyone know how to set up my DNS so that I can let the SE/30 loose on the web?

I'm running OS 7.5.3 with 64MB RAM, 100MB hard disk, Asante ethernet card, Open Transport networking.

Thanks for the help.

 

[cheesestraws]

You can have a look at the landing page here: 76.67.165.247:8888

This gives me a 'permission denied' error.

So I opened the ports in my router for the SE/30, and accessing it via IP works fine, but if I try to use http://moosefuel.media:8888 as I set up, I get no response.

moosefuel.media has no A record for 76.67.165.247 but does have two other A records, both pointing to cloudflare. Have you checked that your cloudflare setup isn't eating the traffic?

 

[cheesestraws]

Yes, going through your cloudflare setup, I don't even get an ACK back from the SE/30:


Whereas I do get an ACK back immediately when short-circuiting it via the direct IP:


This almost certainly isn't a DNS problem (at least not straightforwardly) - definitely look at your cloudflare setup.

 

[moosefuel]

definitely look at your cloudflare setup.

That's definitely progress, thank you @cheesestraws.

The "Access Denied" is a new problem, caused by me tinkering. I think it should work OK now http://76.67.165.247:8888/. I was experimenting with the "Allow/Deny" page in the WebStar admin.

I used another one of my domain names, http://newtfilm.com:8888 and in cloudflare I put it in development mode (supposed to bypass cloudflare's servers). Here's a photo of my DNS settings:



Not too much there. I wonder if I am not completely understanding how to set up hostnames in the WebStar setup:

Here is the default page:




And here is the virtual hosts page (which, when it works, serves a "Hello!" page that I made quickly in HTML):




The local port on the SE/30 is 80 but the router forwards the external :888 traffic to it.

I'm sure there is something about setting up DNS I've either forgotten or never understood, and I suspect it's on the virtual hosts page, unless you can see something wrong with Cloudflare's setup.

noah

 

[moosefuel]

Well scratch that, the page is working for me now at http://newtfilm.com:8888 so long as I have "Proxy" turned off. Your intuition about it being Cloudflare's problem was correct.

Welcome to the internet, my SE/30 server!

Thanks @cheesestraws.

 

[cheesestraws]

Hooray! Glad it's working now

 

[Andy]

Hey cool. I was able to get connect to your SE and to your Newton!

 

[moosefuel]

Hey cool. I was able to get connect to your SE and to your Newton!

Woohoo! You're lucky, the Newton seems to restart itself every few minutes so it's about a 60% chance you'll get it while it's up.

 

[beachycove]

I had a web server running on an eMate a few years ago, using (simple) custom css rather than the built in page. It too was unstable.

I’m interested to see what you put on the SE/30 in due course.

 

[shadedream]

So if this is something you intend to try and keep up all the time, the best bet is to either dedicate a domain to it, or use a subdomain to point to it since it seems like you're using the main domain with another modern website (presumably hosted on a VPS or something somewhere and not your home network?). Then you would set up a dynamic DNS service to update the dedicated domain/subdomain to point to your home IP address with a low TTL (though there will likely still be a bit of delay while it propagates before everyone can hit it again). The dynamic DNS service would require something else modern locally to handle that.

The ideal setup for something like this would be to run a more modern server locally on your network to act as a proxy (and possibly cache) for it so you could do something like point newton.moosefuel.media and se30.moosefuel.media at your home network IP and the proxy would act to point those to the individual servers without having to utilize non-standard web ports externally. You could probably set up an nginx reverse proxy with something like Nginx Proxy Manager and a script for the dynamic DNS on a raspberry pi or something if you have one laying around.

I've heard cloudflare has some sort of service that can handle the proxy/pass-through as well without publishing your public home IP address on the internet via DNS etc, but I've not looked into or messed with it.

 

[dcr]

I just tried and wasn't able to reach either site.

Back in the day, I used an SE/30 as my DNS server with WebStar on a PM 8600.